Re: libtool in binutils question

["Maciej W. Rozycki" <macro at ds2 dot pg dot gda dot pl>]

On 11 Jan 2002, Alexandre Oliva wrote:

> I'm not sure we're ready to switch over to autoconf 2.5x, but I don't
> see a problem in using automake 1.5.  The autoconf 2.5x issues are the
> most relevant ones that have been causing me to postpone this task.
> I'd rather make the upgrade independently, so that we spread the
> breakage along a longer period (instead of breaking everything at once
> and then not knowing where to start trying to fix it :-) but if a
> newer libtool requires autoconf 2.5x (*) , we should start by officially
> adopting autoconf 2.5x, and only then upgrading libtool.  If you can
> show that both the src and the gcc repositories keep working after all
> their autoconf-generated configure scripts are rebuilt, I'm game, but
> I've heard reports that said we were not ready for that yet.

 As of 1.4.2 libtool doesn't require anything over autoconf 2.13, AFAIK. 
Actually the AC_PROG_LIBTOOL macro has not been updated to autoconf 2.5x
yet and running `autoconf -W all' on it produces a number of problem
reports.  It seems to run fine nevertheless. 

 One of the issues I know of with updating to autoconf 2.5x is as follows. 
The Cygnus top-level configure script passes target_alias (via
"--target=") down to sub-configures as this is needed for setting tooldir
properly.  Unfortunately, autoconf 2.5x considers cross-tools are to be
build unconditionally whenever target_alias is set and it sets
program_prefix then.  As a result all programs get installed under
"${target_alias}-<program>" names.  Apparently this is a desired property
of autoconf now. 

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@ds2.pg.gda.pl, PGP key available        +