Hi Dave, Stefano, On Thu, Nov 8, 2012 at 11:40 AM, Dave Goodell <good...@mcs.anl.gov> wrote: > On Nov 8, 2012, at 1:19 PM CST, Stefano Lattarini wrote: > >> On 11/08/2012 07:56 PM, Bruce Korb wrote: >> I'd expect its definition to be brought in by the 'libtoolize' call >> issued by autoreconf; but then I see, in the output you've reported: >> >>> autoreconf: configure.ac: not using Libtool >> >> which means that might still be something wrong with your configure.ac, >> or some bug in autoreconf. If you want more help, you should send us >> the content of your configure.ac, as well as the exact versions of the >> autotools you're using.
OK, attached, but it worked previously, and then there is Dave's followup: > FWIW, I think that I've encountered errors like this before when I've > installed libtool > in a different directory than I installed automake and/or autoconf. > This causes autom4te/aclocal to be unable to find the libtool m4 files, > causing tracing for LT_INIT to fail, so you get the "not using Libtool" > message > and subsequent failures. > > -Dave What it may be worth is a good bit of hassle saving :) I'll check out what happens when I install local versions of autoconf and libtool. Later, though. I have my day job... $ for f in autoconf automake libtool ; do printf "\n$f\n";which -a $f;done autoconf /usr/bin/autoconf automake /u/ROOT/usr/local/bin/automake /usr/bin/automake libtool /usr/bin/libtool
configure.ac
Description: Binary data
