Hi Kurt, * Kurt Roeckx wrote on Sun, Dec 25, 2005 at 01:14:43PM CET: > > I came accross a package that failed to build on Debian amd64 > where it tried to link the static library instead of the shared > one. This seems to have been caused by a change to libtool, > which seems to come from gentoo. The bug in the Debian bug > tracking system for this is: > http://bugs.debian.org/344662 > > The change in libtool.m4 seems to be: > + # Find out which ABI we are using (multilib Linux x86_64 hack). *snip* > I'm not really sure why this breaks anything though. My guess > would be that you're removing paths it needs.
I'm not convinced yet that this is the cause for the breakage. It may well be, though. In any case, it's a system-specific patch; it was not accepted into GNU libtool simply because it's not valid for all GNU/Linux distributions. Don't blame libtool for their non-uniformity. Since I don't have a Debian amd64 system for testing, please rerun the build, post the ./libtool --mode=link command, and all of its output, with --debug added. Please also post ./libtool --config I assume that I can get the source of the corresponding package (the exact one please!) from these URLs, right? http://ftp.debian.org/debian/pool/main/c/cpufrequtils/cpufrequtils_0.4.orig.tar.gz http://ftp.debian.org/debian/pool/main/c/cpufrequtils/cpufrequtils_0.4-1.diff.gz Cheers, Ralf _______________________________________________ Bug-libtool mailing list Bug-libtool@gnu.org http://lists.gnu.org/mailman/listinfo/bug-libtool