Re: autoreconf vs. libtool

[Ralf Corsepius]

Am Mit, 2001-11-07 um 20.38 schrieb Akim Demaille:
> 
> | Something weird (w/ autoconf/cvs, automake/cvs, libtool-1.4.2)
> | Checking out a virgin copy of a simple source-tree from CVS:
> | 

> | # cat configure.ac
> | AC_PREREQ(2.52g)
> | AC_INIT
> | AC_CONFIG_SRCDIR([mail])
> | AC_CONFIG_AUX_DIR(.)
> | AM_INIT_AUTOMAKE(libmail,2.3.0)
> | AC_PROG_CC
> | AM_PROG_LIBTOOL
> | ^^^^^^^^^^^^^^^
> | Using libtool !
> | ..
> | 
> | Now trying to "bootstrap" w/ autoreconf
> | 
> | # autoreconf -i -f -v
> | autoreconf: working in `.'
> | autoreconf: configure.ac: not using Gettext
> | autoreconf: configure.ac: not using Libtool
> |                           ^^^^^^^^^^^^^^^^^
 
> | Apparently autoreconf fails to handle libtool correctly.
> 
> Thanks!  My guilt.  I don't know what is the macro to trace.  What is
> the official PROG_LIBTOOL macro?  The AM_ or AC_?  Autoreconf traces
> AC_PROG_LIBTOOL.
> 
> I don't understand, I just checked in 1.4.2, and there is:
> 
> # old names
> AC_DEFUN([AM_PROG_LIBTOOL],   [AC_PROG_LIBTOOL])
> 
> so tracing AC_PROG_LIBTOOL is enough...
> 
> Hm... I think I know...
> 
> Your aclocal was not built yet, hence AM_PROG_LIBTOOL was not defined,
> so tracing it gave nothing.  What if you rerun it?

# autoreconf -i -f -v
autoreconf: working in `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: libtoolize --copy --force
You should update your `aclocal.m4' by running aclocal.
autoreconf: running: aclocal  --output=aclocal.m4t
autoreconf: `aclocal.m4' is unchanged
autoreconf: running: automake --add-missing --copy --force-missing
autoreconf: running: autoconf --force
autoreconf: configure.ac: not using Autoheader

=> libtoolize has been run, subsequent ./configure and ./make work fine.

> I guess aclocal.m4
> will have brought AC_PROG_LIBTOOL in the picture, so the second time
> it should work.
When having a look into autoreconf, I had suspected something of this
kind, but ...
 
> 
> Hm.  Bad news.   Hm...
Logically, AM_GNU_GETTEXT also is also subject of this issue:

The more I think about it, I am inclined to think tracing can't work for
libtoolize and gettextize unless aclocal has been run once before them 

Ralf