From owner-freebsd-ports@FreeBSD.ORG Fri Mar 13 09:59:51 2009 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 CD8FC106566B for ; Fri, 13 Mar 2009 09:59:51 +0000 (UTC) (envelope-from gesbbb@yahoo.com) Received: from web32105.mail.mud.yahoo.com (web32105.mail.mud.yahoo.com [68.142.207.119]) by mx1.freebsd.org (Postfix) with SMTP id 8C2888FC18 for ; Fri, 13 Mar 2009 09:59:51 +0000 (UTC) (envelope-from gesbbb@yahoo.com) Received: (qmail 71965 invoked by uid 60001); 13 Mar 2009 09:59:50 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1236938390; bh=QsdszLWAVFxeIIkPLX3LJSOHm2JpgD5lKv2+X1rq66M=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=RM0cgeM6qT2pRzdKdF+ybiPh0eCT7yfrVgHrjTMo7HazLn3e+uXexGCX7cDdmVVNSwtEYdsiJWUeU7ENMwEjFy1cGUc2FRoBTUO9KSUU8oo3PzWXrGvXVOcq/XGjjK7BQqKPH/8B2XNRnnsB9Aph7TtWJ/X5eY145ytWK4l+Nww= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=UD/qG9Oz6XmOXKkZ7PuiK+UQCrI1KOqiQWhQ7ucUVlFOIeG9vWDuXtbPj/knPNsqT6SQu1bWPKhewwk2lE2B7b7goyp71dkHnaRdWtendtvxQDyJj2meHJbGv+5GMuQjePN3EHS8f8aoTEx5t4NbUWxM3MEhQipbuQG/bp1hqLk=; Message-ID: <887176.71382.qm@web32105.mail.mud.yahoo.com> X-YMail-OSG: C6nhsy8VM1l6xuHNyT13D.sx3CpGU22uVmZ5iIxwXCBKAsSX7YZTtTmt5A_cmBkk_jDghjSK6.yaq_44GViyyvSwPtnG3owAhOgHwhOr20NUFJYK_lpGoNygWZIgmSAaEmNKWytW3.E8yNbe7evnj17jT2fwjtjhND3n6yI8OKupynQoUn6B40XHByG4Go.9IueYwcE6M.jHF.6gop4Ea0wGom0- Received: from [76.23.177.172] by web32105.mail.mud.yahoo.com via HTTP; Fri, 13 Mar 2009 02:59:50 PDT X-Mailer: YahooMailRC/1277.29 YahooMailWebService/0.7.289.1 References: <721111.30542.qm@web39104.mail.mud.yahoo.com> Date: Fri, 13 Mar 2009 02:59:50 -0700 (PDT) From: GESBBB To: freebsd-ports@freebsd.org In-Reply-To: <721111.30542.qm@web39104.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: Problem with Bash-4 and $(command) syntax 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: Fri, 13 Mar 2009 09:59:52 -0000 > From: bf =0A=A0=0A> > > {Problem with Bash-4 and $(com= mand) ...}:=0A> > [...]=0A> > > I found the same problem, and have reverted= to=0A> > >=A0 bash3.2 until it's sorted out. =0A> >=0A> > See if the follo= wing helps.=0A> >=0A> > http://tiswww.case.edu/php/chet/bash/COMPAT=0A> >= =0A> > Especially:=0A> >=0A> > 38. Since bash-4.0 now follows Posix rules f= or finding the =0A> > closing=0A> > delimiter of a $() command substitution= , it will not behave as > previous=0A> > versions did, but will catch more = syntax and parsing errors =0A> > before=0A> > spawning a subshell to evalua= te the command substitution.=0A> >=0A> >Eray=0A> =0A> Yes, the above is tru= e.=A0 But many of the examples cited=0A> by people noticing this problem ar= e perfectly valid and=0A> _should_ work.=A0 The problem is that the port's = parser is =0A> broken, owing in part to incompatibilities between the =0A> = system yacc currently used to build the parser and GNU=0A> bison, which is = used by the people who write bash.=A0 This=0A> is true of both shells/bash = and shells/bash3, but is more=0A> noticeable in shells/bash.=A0 A fix has b= een proposed, and patches=0A> are available, in the follow-up to:=0A> =0A> = http://www.FreeBSD.org/cgi/query-pr.cgi?pr=3Dports/101230=0A> =0A> The port= 's maintainer has been reluctant to switch to bison,=0A> so this may not be= the solution that is ultimately used to=0A> fix the port, but you can use = these in the meantime.=0A=0AUntil a fix has been put in place, I would sugg= est that a notice be placed in UPDATING that Bash-4 is not completely funct= ional and its use is not recommended. Better yet, maybe the port should jus= t be marked "BROKEN", since it clearly is. I personally would never have in= stalled it had I been aware of the problems it is causing.=A0 IMHO, it shou= ld have been tested more completely before being released into the ports sy= stem.=0A=0A-- =0AJerry