> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Nicolas Rachinsky > Sent: Friday, March 03, 2006 5:20 AM > To: freebsd-stable@FreeBSD.ORG > Subject: Re: configure scripts ignores parameters > > * "Elisey O. Savateev" <[EMAIL PROTECTED]> [2006-03-03 16:10 +0500]: > > Fri, 3 Mar 2006 11:56:09 +0100 > > Nicolas Rachinsky <[EMAIL PROTECTED]> wrote: > > > > > > > > Do you have shells/bash (bash-3.1.10) installed? > > > > > > > Yes. I have. > > > I had one problem here, but unfortunately not the time to really look > at it (and I don't have time to try it again). > > My bash3 here did not correctly process > | for foo > | do echo "$foo" > | done > A similar contruct seems to be in some (most, all?) configure scripts, > which automatically use bash to be executed (if it's available). > > I installed shells/bash2 (bash-2.05b.007_4) and my problem > disappeared. > > HTH, > Nicolas > > -- > http://www.rachinsky.de/nicolas [Bill Milford] I am having the some problem. My temporary fix is to either install bash-3.0.16_1 which is the latest bash package available or you can set CONFIG_SHELL=/bin/sh in your environment. The configure scripts will use bash if available and when it re-executes itself, somehow the command line options do not get passed correctly. Even the most simple option: ./configure --help fails. It was causing the previously reported issues with the apr-db4 port. It causes problems for me in the OpenCA configure script. I suspect that it will affect many ports that use ./configure scripts to pass parameters. I am going to re build all of my ports when this is finally resolved.
_______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
