Re: /bin/sh doesn't run autoconf'ied configure scripts correctly

On Wed, Mar 01, 2006 at 11:15:42AM +1300, Mark Kirkwood wrote:
> Dag-Erling Sm?rgrav wrote:
> >Mark Kirkwood <markir_at_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