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

Here's a small configure.ac that demonstrates the problem: AC_INIT(foo, 1.0, [EMAIL PROTECTED]) AC_PROG_LIBTOOL AC_OUTPUT H ___ http://lists.gnu.org/mailman/listinfo/libtool

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

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

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

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

(no subject)

autoconf 2.59 and libtool 1.5.6. I'm seeing this on a bunch of different systems (the following is from FreeBSD, but I'm also seeing it on Solaris9 and 10, and some others): ... autoreconf259: configure.ac: not using Libtool configure.ac:10: error: possibly undefined macro: AC_PROG_LIBTOOL

cross compiles and DESTDIR

Please leave me in the Cc: line; even if I was subscribed the gnu.org lists manage to auto-unsubscribe me way too frequently. I have inherited a project that originally used libtool-1.4.2. 3 patches were made to that version of libtool to "make it work" in the target environment (cross compile, w

Re: 1,000 year backward compatability of tools

I guess it's time for me to chime in. Dave Mills expect NTP to compile on anything he can get his hands on. I've been lucky so far in that some of the older gear he has is breaking. I do, however, still support SunOS4.1 and Ultrix. And NTP will still use ansi2knr where needed. I am also workin

Re: libfoo.la is already going to be installed in lib.

> Harlan> This appears to be aproblem with libtool+automake; if I > Harlan> use a static library (no libtool) I don't see this > Harlan> problem. > > Unless I'm mistaken, you already submitted this one as PR automake/350. Could well be - things are hectic here. > Harlan> Is there a workarou

libfoo.la is already going to be installed in lib.

This appears to be aproblem with libtool+automake; if I use a static library (no libtool) I don't see this problem. Is there a workaround/bugfix? This problem means that autoreconf bails with an error... (Yes, I've tried a couple of other choices, like using a variable in the conditionals and s