* David Paleino wrote on Tue, Feb 05, 2008 at 08:32:21PM CET: > > $ libtool --version > ltmain.sh (GNU libtool 1.2525 2007/10/16 22:45:48) 2.1a
This is irrelevant. > $ ./libtool --version > ltmain.sh (GNU libtool) 1.5.24 Debian 1.5.24-1ubuntu1 (1.1220.2.456 2007/06/24 > 02:25:32) This is the bug. The ltmain.sh file used came from 1.5.24 not from 2.1a. > ./libtool --config: <http://pastebin.com/f47ec56a> This is from 2.1a. > libtool --config: <http://pastebin.com/f4ffad97b> Again, this is irrelevant. > > > libtoolize comes with the package libtool itself, and I > > > just had installed the experimental version. Thus, libtoolize must have > > > been > > > updated as well, together with libtool. Right? > > > > Yes. And you reran libtoolize, and aclocal with the right flags to find > > and reran autoconf and configure? > > Erm... no. I feared to change upstream's source code, which would result in > different md5sums at the end. And yes, I know upstream shouldn't include any > generated code, but many do. :( The point is, whether you re-bootstrap or not, you must use matching versions of the macro files (*.m4) and the script file (ltmain.sh). Your breakage comes from not doing that. I don't recall how to mark a Debian bug as invalid/fixed. Cheers, Ralf -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
