Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)
On Mon, Mar 06, 2006 at 04:59:42PM -0500, Kris Kennaway wrote: > On Sun, Mar 05, 2006 at 04:01:19AM -0500, Kris Kennaway wrote: > > On Sun, Mar 05, 2006 at 09:57:54AM +0100, Nicolas Rachinsky wrote: > > > * Kris Kennaway <[EMAIL PROTECTED]> [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? > > I have committed the patch, so this should go away next time you > portupgrade. Kris, thanks for taking care of this. I've been Net-dead for 3 weeks. -- -- David ([EMAIL PROTECTED]) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)
On Sun, Mar 05, 2006 at 04:01:19AM -0500, Kris Kennaway wrote: > On Sun, Mar 05, 2006 at 09:57:54AM +0100, Nicolas Rachinsky wrote: > > * Kris Kennaway <[EMAIL PROTECTED]> [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? I have committed the patch, so this should go away next time you portupgrade. Kris pgp2rzAmJZ8b1.pgp Description: PGP signature
Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)
On 03/05/06 04:12, Rainer Alves wrote: > Kris Kennaway wrote: >> On Sun, Mar 05, 2006 at 09:57:54AM +0100, Nicolas Rachinsky wrote: >>> * Kris Kennaway <[EMAIL PROTECTED]> [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? > > 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. I had yacc/bison problems when attempting to build the csup port. I've previously had issues with install-info/texinfo: http://lists.freebsd.org/pipermail/freebsd-questions/2006-February/114123.html The real issue was that I had changed my path to put /usr/local/(s)bin before /usr/(s)bin. I've since changed my path back and everything works as expected. I don't even recall why I changed it in the first place, but it caused some interesting problems... -Jonathan -- Jonathan Noack | [EMAIL PROTECTED] | OpenPGP: 0x991D8195 signature.asc Description: OpenPGP digital signature
Re: [Fwd: Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)]
Mike Jakubik wrote: > FYI. This has been a known issue with bison-1.75 for over three years: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=167635;archive=yes http://lists.gnu.org/archive/html/bug-bash/2003-01/msg00061.html http://lists.gnu.org/archive/html/bug-bash/2004-09/msg00118.html Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet ) Live Strong. No day but today. Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://cnswww.cns.cwru.edu/~chet/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)
Rainer Alves wrote: 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. Ditto. Works here. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)
Kris Kennaway wrote: On Sun, Mar 05, 2006 at 09:57:54AM +0100, Nicolas Rachinsky wrote: * Kris Kennaway <[EMAIL PROTECTED]> [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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)
On Sun, Mar 05, 2006 at 09:57:54AM +0100, Nicolas Rachinsky wrote: > * Kris Kennaway <[EMAIL PROTECTED]> [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 pgpBxdkANoizi.pgp Description: PGP signature
Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)
* Kris Kennaway <[EMAIL PROTECTED]> [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. Nicolas -- http://www.rachinsky.de/nicolas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)
On Sun, Mar 05, 2006 at 09:36:25AM +0100, Nicolas Rachinsky wrote: > * Nicolas Rachinsky <[EMAIL PROTECTED]> [2006-03-03 18:56 +0100]: > > Version 3.1.10 (which is the latest AFAIK) of the port contains the > > problem, at least here using FreeBSD 4.11. > > 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)? Kris pgpmC0W90sI7B.pgp Description: PGP signature
Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)
* Nicolas Rachinsky <[EMAIL PROTECTED]> [2006-03-03 18:56 +0100]: > Version 3.1.10 (which is the latest AFAIK) of the port contains the > problem, at least here using FreeBSD 4.11. 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. Nicolas -- http://www.rachinsky.de/nicolas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)
Kris Kennaway wrote: On Sat, Mar 04, 2006 at 07:33:00PM -0500, Mike Jakubik wrote: Shouldn't the port be marked broken or reverted to a working copy in that case? The preference is to fix it, of course, but if that can't happen in the next day or two we'll do one or the other for the releases. Kris Agreed. I've emailed bug-bash@gnu.org about this. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)
On Sat, Mar 04, 2006 at 07:33:00PM -0500, Mike Jakubik wrote: > Sam Sirlin wrote: > >FYI, in case there was any doubt, this annoying bug is also present in > >a recent 6.0-STABLE (Sat Jan 14) on amd 64. > > > >CONFIG_SHELL=/bin/sh is a fix. > > > > > > Shouldn't the port be marked broken or reverted to a working copy in > that case? The preference is to fix it, of course, but if that can't happen in the next day or two we'll do one or the other for the releases. Kris pgpcGIsuncHwL.pgp Description: PGP signature
Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)
Sam Sirlin wrote: FYI, in case there was any doubt, this annoying bug is also present in a recent 6.0-STABLE (Sat Jan 14) on amd 64. CONFIG_SHELL=/bin/sh is a fix. Shouldn't the port be marked broken or reverted to a working copy in that case? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)
FYI, in case there was any doubt, this annoying bug is also present in a recent 6.0-STABLE (Sat Jan 14) on amd 64. CONFIG_SHELL=/bin/sh is a fix. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
bash 3.1.10 breaks configure scripts (was Re: configure scripts ignores parameters)
* Kris Kennaway <[EMAIL PROTECTED]> [2006-03-03 12:39 -0500]: > On Fri, Mar 03, 2006 at 09:33:55AM -0800, Kevin Oberman wrote: > > > > I hope someone has reported this error to the bash developers. > > > > If te latest bash version fixes the problem, it's a bit too late to > > report it. > > Well, how about testing the latest version to see if it's fixed? :-) Version 3.1.10 (which is the latest AFAIK) of the port contains the problem, at least here using FreeBSD 4.11. > Bottom line is: unless people take swift action about this it'll > probably stay broken in the release. I sent a report with bashbug and CCd the port maintainer. I can't test with other FreeBSD releases. Nicolas -- http://www.rachinsky.de/nicolas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
