Re: Libtool library used but 'LIBTOOL' is undefined

[Dave Goodell]

On Nov 8, 2012, at 1:19 PM CST, Stefano Lattarini wrote:

> On 11/08/2012 07:56 PM, Bruce Korb wrote:
>> 
>>> autoreconf: configure.ac: not using Libtool
[…]
>>> lib/Makefile.am:31: error: Libtool library used but 'LIBTOOL' is undefined
>>> lib/Makefile.am:31:   The usual way to define 'LIBTOOL' is to add 'LT_INIT'
>>> lib/Makefile.am:31:   to 'configure.ac' and run 'aclocal' and 'autoconf' 
>>> again.
>>> lib/Makefile.am:31:   If 'LT_INIT' is in 'configure.ac', make sure
>>> lib/Makefile.am:31:   its definition is in aclocal's search path.
>>> lib/Makefile.am: installing './depcomp'
>>> autoreconf: automake failed with exit status: 1
>> 
>> Yes, I see the
>>  ``If 'LT_INIT' is in 'configure.ac', make sure its
>>    definition is in aclocal's search path.''
>> stuff, but if I google the string, I just get advice
>> to add LT_INIT to my configure.ac file.  Pretty useless.
>> 
> 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.

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