Date: Mon, 27 Feb 2006 13:34:05 +1300 From: Mark Kirkwood <markir@paradise.net.nz> To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: freebsd-current@freebsd.org, Kash Pande <kash@kashzone.info> Subject: Re: /bin/sh doesn't run autoconf'ied configure scripts correctly Message-ID: <440248FD.6080806@paradise.net.nz> In-Reply-To: <86r75qednn.fsf@xps.des.no> References: <44013740.6000609@kashzone.info> <86r75qednn.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smørgrav wrote: > Kash Pande <kash@kashzone.info> writes: > >>I'm running 6.1-BETA1, and I guess this is a part of the 27,000 >>regressions that happened from 5.4 to 6.1, however, when using sh as >>the bourne code interpreter, configure scripts fail to execute. > > > The likelihood of this being a sh(1) bug is pretty much nil. The > ports cluster builds the entire ports collection about once a week. > There are currently 11,901 ports with a GNU configure script, so the > ports team should have encountered this by now. > > Judging from the error messages you quote, it's more likely that there > is something wrong with your installed version of m4, or that you have > installed a package with a buggy aclocal script which confuses m4. > > DES A related possibility is that you need to amend the include path for aclocal correctly/differently. On 6.0R I get a sensible result out of autogen.sh if I change the aclocal command to: run_or_die $ACLOCAL -I m4 -I /usr/local/share/aclocal cheers Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?440248FD.6080806>