On Thu, 6 Jul 2000, Lars J. Aas wrote:
> On Thu, Jul 06, 2000 at 02:33:39PM +0200, Lars J. Aas wrote:
> : I'm trying to upgrade to CVS autoconf, and I'm wondering if I need
> : to upgrade automake, libtool, and m4 at the same time?
>
> I've upgraded autoconf and automake and m4 to release 1.4o (only
> vanilla tool is libtool 1.3.5), and things seems to go fine until I
> try to run configure:
>
> [...]
> | checking host system type... i586-pc-linux-gnu
> | checking for ranlib... ranlib
> | checking for ld used by GCC... /usr/bin/ld
> | checking if the linker (/usr/bin/ld) is GNU ld... yes
> | checking for BSD-compatible nm... /usr/bin/nm -B
> | checking whether ln -s works... yes
> | loading cache /dev/null within ltconfig
> | ltconfig: you must specify a host type if you use `--no-verify'
> | Try `ltconfig --help' for more information.
> | configure: error: libtool configure failed
> | $
>
> What's the deal with this? Am I missing some libtool macro in
> configure.in?
You need to upgrade to the CVS versions of autoconf, automake, and
libtool. You also need to install them in that order to get libtool
to bootstrap itself with the new autoconf. It is actually kind of
messy, but it does work if you install them in the right order
and set the PATH to include the install bin directory.
The error you are running into means you are using the
old version of libtool with the new version of autoconf
and automake, and that don't work. Another approach is to
uninstall the old versions of autoconf, automake, and libtool
before you begin.
Mo DeJong
Red Hat Inc
