Date: Thu, 22 Dec 2011 10:32:16 +0100 From: Martin Matuska <mm@FreeBSD.org> To: perryh@pluto.rain.com Cc: freebsd-ports@freebsd.org, kob6558@gmail.com, leslie@eskk.nu Subject: Re: Stop in /usr/ports/multimedia/x264 Message-ID: <4EF2F920.8060007@FreeBSD.org> In-Reply-To: <4ef30e7b.gG6UGw%2BkkNWpdv07%perryh@pluto.rain.com> References: <4EF1E3EF.9000405@eskk.nu> <CAN6yY1tOrhyng1o5%2Bo5ko3cEoT2MLqCUF=L47Gesv%2BNnDdrhFw@mail.gmail.com> <4ef30e7b.gG6UGw%2BkkNWpdv07%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <kob6558@gmail.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EF2F920.8060007>