Date: Sun, 05 Mar 2006 06:12:49 -0300 From: Rainer Alves <rainer.alves@gmail.com> To: Kris Kennaway <kris@obsecurity.org> Cc: fbsd-stable-0@ml.turing-complete.org, freebsd-stable@FreeBSD.ORG, obrien@FreeBSD.org Subject: Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters) Message-ID: <440AAB91.8090901@gmail.com> In-Reply-To: <20060305090119.GA73809@xor.obsecurity.org> References: <20060303172231.GA8478@xor.obsecurity.org> <20060303173355.1F0FB45041@ptavv.es.net> <20060303173925.GA8832@xor.obsecurity.org> <20060303175644.GA77766@mid.pc5.i.0x5.de> <20060305083625.GB90680@mid.pc5.i.0x5.de> <20060305084123.GA73405@xor.obsecurity.org> <20060305085754.GA42388@mid.pc5.i.0x5.de> <20060305090119.GA73809@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > On Sun, Mar 05, 2006 at 09:57:54AM +0100, Nicolas Rachinsky wrote: >> * Kris Kennaway <kris@obsecurity.org> [2006-03-05 03:41 -0500]: >> > On Sun, Mar 05, 2006 at 09:36:25AM +0100, Nicolas Rachinsky wrote: >> > > The problem seems to depend on the installed bison version. With no >> > > bison or bison-2.1_1 installed it works fine, with bison-1.75_2,1 it >> > > doesn't. >> > >> > Installed at what point: the build time of the bash port, or runtime >> > (which would be very odd)? >> >> The build time. I submitted ports/94086, which contains a >> fix/workaround. > > Great, thanks for tracking this down! Can others confirm this > solution? > > Kris > Yes, this fixes the problem. Using devel/bison2 instead of 1.75 also works, but switching to the builtin YACC is indeed a better solution. -- Rainer Alves
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?440AAB91.8090901>