autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: autoconf 2.53 doesn't find autom4te


From: Alexandre Duret-Lutz
Subject: Re: autoconf 2.53 doesn't find autom4te
Date: Wed, 12 Jun 2002 20:15:49 +0200
User-agent: Mutt/1.4i

On Wed, Jun 12, 2002 at 10:33:58AM -0700, Paul Eggert wrote:
> 
> 2002-06-12  Paul Eggert  <address@hidden>
> 
>       * bin/autoconf.as (AUTOM4TE): Default to a fully qualified path
>       name, so that symlinks to 'autoconf' work properly.  Bug reported
>       by Bruno Haible.
>       * bin/autoheader.in (AUTOM4TE): Likewise.
>       * bin/autoreconf.in (autoconf, autoheader): Likewise.
>       * bin/autoscan.in (autom4te): Likewise.
>       * bin/autoupdate.in (autom4te): Likewise.
> 

This will break the test suite for the same reason my patch of
February did.
http://mail.gnu.org/pipermail/autoconf-patches/2002-February/008222.html

The test suite relies on PATH.  With your patch, calling `autoconf' from
the test suite will run tests/autoconf which runs bin/autoconf, which
finally runs $bindir/autom4te (i.e. any version previously installed here)
instead of the tests/autom4te wrapper.

Also I recall there was many dicussions about whether full PATH
should be used or not, back in February.  My impression was that
there was an agreement that absolute pathnames were worse than relative
pathnames. (Of course the ideal is to not use filenames at all :))
-- 
Alexandre Duret-Lutz



reply via email to

[Prev in Thread] Current Thread [Next in Thread]