libtool-patches
[Top][All Lists]
Advanced

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

Re: FYI: 85-gary-fix-vcl.tmp-droppings.patch


From: Alexandre Duret-Lutz
Subject: Re: FYI: 85-gary-fix-vcl.tmp-droppings.patch
Date: Tue, 10 Feb 2004 20:41:02 +0100
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux)

>>> "Gary" == Gary V Vaughan <address@hidden> writes:

[...]

 Gary> It's going to take a little while longer, because both
 Gary> autoreconf and automake don't invoke libtool when there
 Gary> is no AC_PROG_LIBTOOL in configure.ac :-( We may have to
 Gary> ship libtool with patches for automake 1.8.2 and autoconf
 Gary> 2.59.

For the records, automake does not invoke libtoolize since
version 1.6, and does not trace AC_PROG_LIBTOOL since version
1.6b.  It should just require the $(LIBTOOL) Makefile variable to
be defined when libtool libraries are used.

When $(LIBTOOL) is not defined, automake will suggest adding
AC_PROG_LIBTOOL to configure.ac, but this is just a
suggestion and it can be improved after libtool 1.6 is
released.


As far as autoreconf is concerned, my understanding is that it
works as follows:
   1. run aclocal
   2. trace for AC_PROG_LIBTOOL
   3. run libtoolize if AC_PROG_LIBTOOL has been seen
   4. run aclocal again in case libtoolize modified the auxdir

Even if you do not rename AC_PROG_LIBTOOL, this procedure
already fails because the first aclocal cannot locate the
AC_PROG_LIBTOOL.

A possible solution would be to
  a) reinstall libtool.m4 back in /usr/share/aclocal/ so step #1 works
  b) arrange so that LT_INIT calls AC_PROG_LIBTOOL so step #2 works

this latter point is not really satisfactory because
AC_PROG_LIBTOOL can not longer be AU_DEFUNed, but at least it
makes the change seamless to autoreconf.
-- 
Alexandre Duret-Lutz





reply via email to

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