[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: how to break out of the libtool rathole ?
From: |
Gary V. Vaughan |
Subject: |
Re: how to break out of the libtool rathole ? |
Date: |
Thu, 18 Jul 2013 18:29:59 +0700 |
On Jul 18, 2013, at 10:17 AM, Dennis Clarke <address@hidden> wrote:
> libtool: Version mismatch error. This is libtool 2.4.2, revision 1.3337,
> libtool: but the definition of this LT_INIT comes from revision 1.3201.
> libtool: You should recreate aclocal.m4 with macros from revision 1.3337
> libtool: of libtool 2.4.2 and run autoconf again.
> gmake[2]: *** [libltdl/loaders/libltdl_libltdl_la-preopen.lo] Error 63
> gmake[2]: Leaving directory
> `/usr/local/build/libtool-2.4.2_SunOS5.8_sparcv9.003'
> gmake[1]: *** [all-recursive] Error 1
> gmake[1]: Leaving directory
> `/usr/local/build/libtool-2.4.2_SunOS5.8_sparcv9.003'
> gmake: *** [all] Error 2
> mimas$
This happens when you partially regenerate libtool m4 files (specifically
ltversion.m4)
using a different version of libtool to the one you are building with, and
prevents
a lot of problems later on if you had continued with a mix-and-match of
ltmain.sh and
libtool.m4 from different libtool revisions.
Assuming you clear up the problem with your file timestamps, you'll be able to
use
the generated files as is from the release tarball which do have matching
version
numbers.
If you prefer to build from git, then the bootstrap script will generate the
missing
files correctly before you call ./configure.
Cheers,
--
Gary V. Vaughan (gary AT gnu DOT org)
Re: how to break out of the libtool rathole ?, Gary V. Vaughan, 2013/07/18