Date: Wed, 01 Mar 2006 12:53:41 +1300 From: Mark Kirkwood <markir@paradise.net.nz> To: Kris Kennaway <kris@obsecurity.org> Cc: Dag-Erling Sm?rgrav <des@des.no>, freebsd-current@freebsd.org, Kash Pande <kash@kashzone.info> Subject: Re: /bin/sh doesn't run autoconf'ied configure scripts correctly Message-ID: <4404E285.8080305@paradise.net.nz> In-Reply-To: <20060228233402.GA88717@xor.obsecurity.org> References: <44013740.6000609@kashzone.info> <86r75qednn.fsf@xps.des.no> <440248FD.6080806@paradise.net.nz> <86veuz7c9u.fsf@xps.des.no> <4404CB8E.1020300@paradise.net.nz> <20060228233402.GA88717@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > On Wed, Mar 01, 2006 at 11:15:42AM +1300, Mark Kirkwood wrote: > >>Dag-Erling Sm?rgrav wrote: >> >>>Mark Kirkwood <markir@paradise.net.nz> writes: >>> >>> >>>>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 >>> >>> >>>this should not be necessary if autoconf was installed from ports >>>(devel/gnu-autoconf). >>> >>>DES >> >>I'm using the autoconf259 and automake19 ports, this doctoring seems to >>be needed in some cases anyway - audacious and enlightenment CVS HEAD >>are the two examples I can recall. > > > You don't want to use the numbered auto* ports for non-port > development, but gnu-autoconf instead as ade said. > > Kris Ah - right, always wondered about when to use which, thanks for clearing that up! Cheers Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4404E285.8080305>