Hi Jordi,
That's a bug in debian libtool package, apparently. On debian unstable
I see:
# dpkg -l libtool
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii libtool 2.5.4-3 all Generic library support script
So far so good. Now, the LT_PREREQ macro is defined as (file
/usr/share/aclocal/libtool.m4:41-46):
m4_defun([LT_PREREQ],
[m4_if(m4_version_compare(m4_defn([LT_PACKAGE_VERSION]), [$1]), -1,
[m4_default([$3],
[m4_fatal([Libtool version $1 or higher is required],
63)])],
[$2])])
In other words, it compares its argument with the value of m4 variable
LT_PACKAGE_VERSION. That variable, in turn, is defined in file
/usr/share/aclocal/ltversion.m4. Examining that file I see (in line
24):
m4_define([LT_PACKAGE_VERSION], [2.4.7])
Obviously, 2.4.7 < 2.5.4, hence abnormal termination.
Regards,
Sergey
