Re: possibly undefined macro: AC_PROG_LIBTOOL (was: (no subject))

2006-06-26 Thread Stepan Kasal
Hi, first, run aclocal, it should install the AC_PROG_LIBTOOL macro to aclocal.m4. Then run autoconf. The info from your preceding mail does not pbring anything new: % cd autom4te.cache/ % grep AC_PROG_LIBT * output.0:AC_PROG_LIBTOOL output.1:AC_PROG_LIBTOOL output.2:AC_PROG_LIBTOOL output.3:

Re: possibly undefined macro: AC_PROG_LIBTOOL (was: (no subject))

2006-06-26 Thread Harlan Stenn
> Hi, > first, run aclocal, it should install the AC_PROG_LIBTOOL macro to > aclocal.m4. > Then run autoconf. autoreconf does this. The fragment I posted works on many machines and does not work on some machines. In particular, I have a "nested" repo, where topdir/configure.ac uses AC_PROG_L

Re: possibly undefined macro: AC_PROG_LIBTOOL (was: (no subject))

2006-06-26 Thread Harlan Stenn
Clarification: > > first, run aclocal, it should install the AC_PROG_LIBTOOL macro to > > aclocal.m4. > > Then run autoconf. > > autoreconf does this. autoreconf runs aclocal is what I meant. On the machines where this apparently works, AC_PROG_LIBTOOL is in aclocal.m4, but on subdirs where

Autoconf 2.60 released

2006-06-26 Thread Paul Eggert
We're happy to announce the release of Autoconf 2.60. Please grab it from one of the gnu.org mirror sites. The important changes since 2.59 are listed below. Two of these changes require special attention: * Some directory variables have been added, and others adjusted to changes in the GNU Co