From owner-freebsd-ports@FreeBSD.ORG Thu Dec 22 16:38:19 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 9218B106564A; Thu, 22 Dec 2011 16:38:19 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 048A28FC0A; Thu, 22 Dec 2011 16:38:18 +0000 (UTC) Received: by wgbdr11 with SMTP id dr11so16269034wgb.31 for ; Thu, 22 Dec 2011 08:38:18 -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; bh=ggbTQwN10+uYIlV4yiVGckLcV58sTmn+g5rpU0eVigM=; b=jyOh+QLDSfleTQTbeGyXCdxnLm9BbIBcgkHh+GTTI5M0y4R8RhKvrMcJR313MSfetT q/r0MrdNQe1i/aMGMdgHavmkG0EKsUS61VVemxm9wXMNIHgXMTPoYgr5mbUFycOQljFy uACpFmthauxlRwhH3FPSqxVGYxPirgJo4vlOw= MIME-Version: 1.0 Received: by 10.227.206.66 with SMTP id ft2mr11199878wbb.8.1324571897859; Thu, 22 Dec 2011 08:38:17 -0800 (PST) Received: by 10.223.158.129 with HTTP; Thu, 22 Dec 2011 08:38:17 -0800 (PST) In-Reply-To: <4EF2F920.8060007@FreeBSD.org> References: <4EF1E3EF.9000405@eskk.nu> <4ef30e7b.gG6UGw+kkNWpdv07%perryh@pluto.rain.com> <4EF2F920.8060007@FreeBSD.org> Date: Thu, 22 Dec 2011 08:38:17 -0800 Message-ID: From: Kevin Oberman To: Martin Matuska Content-Type: text/plain; charset=ISO-8859-1 Cc: perryh@pluto.rain.com, 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 16:38:19 -0000 On Thu, Dec 22, 2011 at 1:32 AM, Martin Matuska wrote: > 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 [[ ]]) Thanks for the quick fix, but I am still baffled as to why it built correctly on two of my three systems where it's installed. All three complained about the '[[' type constructs, but only one spit out the "x264_CSP|all" error and al of the other completed the build. It is possible that the build was not quite right as a result of the errors, but why did only one fail completely? The only thing I can think of is that the failing system is the oldest, running 8.2 while the others were running 9.0-RC2 and 9.0-Beta3. Again, thanks again for the quick fix. I tend to prefer #2 if there is no real reason for bash, but almost all systems used for multimedia work already have bash installed, so it's not a big deal. -- R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com