> > On the machines where this apparently works, AC_PROG_LIBTOOL is in
> > aclocal.m4, but on subdirs where it does not work, AC_PROG_LIBTOOL is
> > *not* in aclocal.m4
> How do you invoke the subdir configure scripts from inside of your
> toplevel configure script?
The bootstrap script runs 'aut
On Mon, 2006-06-26 at 19:39 +, Harlan Stenn wrote:
> 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
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
> 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
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:
Here's a small configure.ac that demonstrates the problem:
AC_INIT(foo, 1.0, [EMAIL PROTECTED])
AC_PROG_LIBTOOL
AC_OUTPUT
H
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
With a bit of digging I can see that the configure.ac file that
(on a machine that demonstrates this problem) autom4te sees:
% cd autom4te.cache/
% grep AC_PROG_LIBT *
output.0:AC_PROG_LIBTOOL
output.1:AC_PROG_LIBTOOL
output.3:AC_PROG_LIBTOOL
requests:'AC_PROG_LIBTOOL' => 1
Hi Ralf,
> > autoconf 2.59 and libtool 1.5.6.
> >
> > I'm seeing this on a bunch of different systems
>
> > autoreconf259: configure.ac: not using Libtool
> > configure.ac:10: error: possibly undefined macro: AC_PROG_LIBTOOL
> > If this token and others are legitimate, please use m4_patt
