Re: automake 1.8d: "Libtool library used but `LIBTOOL' is undefined"

[Stephan A Suerken]

Alexandre Duret-Lutz <address@hidden> writes:

(...)
>  Stephan> src/Makefile.am:22: The usual way to define `LIBTOOL' is to add 
> `AC_PROG_LIBTOOL'
>  Stephan> src/Makefile.am:22: to `configure.ac' and run `aclocal' and 
> `autoconf' again.
> 
>  Stephan> although AC_PROG_LIBTOOL _is_ present in configure.ac.
> 
> Therefore it means AC_PROG_LIBTOOL is not evaluated.
> This is certainly because AC_PROG_LIBTOOL is not defined in aclocal.m4.
> This is probably because aclocal does not see libtool.m4 in its search path.
> This is might be because Automake and Libtool are installed with different
> --prefix; for instance Libtool in /usr and Automake in /usr/local.
> 
> If that is your case, you can add /usr/share/aclocal to the search
> path of the new aclocal using
> 
>   echo /usr/share/aclocal > /usr/local/share/aclocal/dirlist
> 
> See the Automake manual's "Macro search path" section for more
> discussion about dirlist.

I actually had tried "-I /usr/share/aclocal" (aclocal and autoheader),
which did not work either. Extending /usr/local/share/aclocal/dirlist
as suggested didn't succeed as well.

The bottom line seems to be that it was naive to assume that simply by
installing automake to /usr/local, it will cleanly supersede the
installation's automake, and work fine with the installed
libtool/autoconf. I.e., at least for Debian sarge, I needed to purge
all automake* packages. After that, it worked as expected.

So maybe the error message is misleading, but this would hold true for
all automake's, not only 1.8d...

Thanks,

Stephan
-- 
Stephan A Suerken <suerken|address@hidden>

Schlund + Partner AG, Karlsruhe