From owner-freebsd-ports@FreeBSD.ORG Thu Dec 22 09:32:24 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54D21106566C for ; Thu, 22 Dec 2011 09:32:24 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from mail.vx.sk (mail.vx.sk [IPv6:2a01:4f8:150:6101::4]) by mx1.freebsd.org (Postfix) with ESMTP id E3BBD8FC0C for ; Thu, 22 Dec 2011 09:32:23 +0000 (UTC) Received: from core.vx.sk (localhost [127.0.0.2]) by mail.vx.sk (Postfix) with ESMTP id 214BD1625E; Thu, 22 Dec 2011 10:32:23 +0100 (CET) X-Virus-Scanned: amavisd-new at mail.vx.sk Received: from mail.vx.sk by core.vx.sk (amavisd-new, unix socket) with LMTP id 2POktJTM1iaT; Thu, 22 Dec 2011 10:32:17 +0100 (CET) Received: from [10.9.8.1] (188-167-78-15.dynamic.chello.sk [188.167.78.15]) by mail.vx.sk (Postfix) with ESMTPSA id AC70F16247; Thu, 22 Dec 2011 10:32:17 +0100 (CET) Message-ID: <4EF2F920.8060007@FreeBSD.org> Date: Thu, 22 Dec 2011 10:32:16 +0100 From: Martin Matuska User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: perryh@pluto.rain.com References: <4EF1E3EF.9000405@eskk.nu> <4ef30e7b.gG6UGw+kkNWpdv07%perryh@pluto.rain.com> In-Reply-To: <4ef30e7b.gG6UGw+kkNWpdv07%perryh@pluto.rain.com> X-Enigmail-Version: 1.3.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org, kob6558@gmail.com, leslie@eskk.nu Subject: Re: Stop in /usr/ports/multimedia/x264 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2011 09:32:24 -0000 Say, did you look at the port recently? :-) I have added bash as a build dependency and use it for the configure script. There are two ways I can solve this in general: 1.) add bash as a build dependency and use it for configure (I have chosen this for now, already committed) 2.) patch configure and remove/replace constructs unsupported by /bin/sh (e.g. "==" or [[ ]]) Cheers, mm On 22.12.2011 12:03, perryh@pluto.rain.com wrote: > Kevin Oberman wrote: > >> I see the following errors during the configure stage: >> ===> Configuring for x264-0.119.2113 >> [[: not found > That sure looks as if the configure script needs to be run with bash. > > files/patch-configure does this: > > -#!/bin/bash > +#!/bin/sh > > which presumes that the script does not actually need bash extensions. > However, since it does seem to need those extensions, that part of the > patch should be > > -#!/bin/bash > +#!/usr/local/bin/bash > > and bash needs to be added as a build dependency. (Alternatively, the > configure script could be patched to not use the [[ bash builtin.) > > Maintainer already in Cc: list. -- Martin Matuska FreeBSD committer http://blog.vx.sk