bug-autoconf
[Top][All Lists]
Advanced

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

Re: autoreconf vs. libtool


From: Akim Demaille
Subject: Re: autoreconf vs. libtool
Date: 07 Nov 2001 20:38:17 +0100
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Artificial Intelligence)

| Something weird (w/ autoconf/cvs, automake/cvs, libtool-1.4.2)
| Checking out a virgin copy of a simple source-tree from CVS:
| 
| # cvs co libmail
| ..
| # find ! -path '*CVS*'
| ./Makefile.am
| ./configure.ac
| ./libmail.pc.in
| ./libmail.spec.in
| ./mail
| ./mail/.cvsignore
| ./mail/Makefile.am
| ./mail/maillock.c
| ./mail/maillock.h
| 
| # 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
|                           ^^^^^^^^^^^^^^^^^
| autoreconf: running: aclocal  --output=aclocal.m4t
| autoreconf: `aclocal.m4' is created
| autoreconf: running: automake --add-missing --copy --force-missing
| configure.ac: installing `./install-sh'
| configure.ac: installing `./mkinstalldirs'
| configure.ac: installing `./missing'
| aclocal.m4:662: required file `./ltmain.sh' not found
| aclocal.m4:662: installing `./config.guess'
| aclocal.m4:662: installing `./config.sub'
| mail/Makefile.am: installing `./depcomp'
| autoreconf: running: autoconf --force
| autoreconf: configure.ac: not using Autoheader
| 
| 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?  I guess aclocal.m4
will have brought AC_PROG_LIBTOOL in the picture, so the second time
it should work.


Hm.  Bad news.   Hm...



reply via email to

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