From owner-freebsd-ports@FreeBSD.ORG Thu Dec 22 05:36:18 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 53B951065670; Thu, 22 Dec 2011 05:36:18 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id B338F8FC14; Thu, 22 Dec 2011 05:36:17 +0000 (UTC) Received: by werb13 with SMTP id b13so5703643wer.13 for ; Wed, 21 Dec 2011 21:36:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=+q2mK2rC/nLE3HtTG8LWU1EWLd+cyICOBSi3dRN1zm0=; b=U0wzMVh0b0JVmH4I5X+6ss1CK1SfZZdRZaywhRRLDyGkGA2y5YOq/wamWPBH9bjA/X sRqyGR2BzriYBV7uWTa6pcFzqMuP4PsHkvHuu0knQkzEvGOeQkPXy8lzbcE+7YmtjiXA RE7Xu0RR2pLEu/nG/8WKzpjBxfLv3VDNFwoVQ= MIME-Version: 1.0 Received: by 10.216.144.138 with SMTP id n10mr4977272wej.57.1324532176529; Wed, 21 Dec 2011 21:36:16 -0800 (PST) Received: by 10.223.158.129 with HTTP; Wed, 21 Dec 2011 21:36:16 -0800 (PST) In-Reply-To: <4ef30e7b.gG6UGw+kkNWpdv07%perryh@pluto.rain.com> References: <4EF1E3EF.9000405@eskk.nu> <4ef30e7b.gG6UGw+kkNWpdv07%perryh@pluto.rain.com> Date: Wed, 21 Dec 2011 21:36:16 -0800 Message-ID: From: Kevin Oberman To: perryh@pluto.rain.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: mm@freebsd.org, freebsd-ports@freebsd.org, 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 05:36:18 -0000 On Thu, Dec 22, 2011 at 3:03 AM, wrote: > Kevin Oberman wrote: > >> I see the following errors during the configure stage: >> =3D=3D=3D> =A0Configuring 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: > > =A0-#!/bin/bash > =A0+#!/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 > > =A0-#!/bin/bash > =A0+#!/usr/local/bin/bash > > and bash needs to be added as a build dependency. =A0(Alternatively, the > configure script could be patched to not use the [[ bash builtin.) > > Maintainer already in Cc: list. Hmm. I just noticed the mm@ removed patch-configure from the port as the upstream now uses sh. So there is a problem, but it is not with the port. Looks like the upstream switched to sh, but sis not remove all of the "bash"isms. I edited configure to change from sh to bash and that makes it configure and build correctly. Looks like the configure script needs a bit of love to work correctly with sh, though I still am baffled as to why if built on 2 systems and failed on one. --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com