Red Hat Bugzilla – Bug 467367
Build breaks with libtool 2.2.x
Last modified: 2009-02-05 12:10:49 EST
apr's build is breaking with libtool 2.2.x because it is calling apr's "buildconf" script to regenerate apr's build scripts. Why is it doing this? I don't see any of the autotools input files getting patched (which would be the normal reason to do such a thing).
Unless I've missed something, the problem can be fixed simply by eliminating the call to buildconf.
1) because APR ships a copy of the generated libtool script, which should be in sync with the system copy
2) otherwise the generated (upstream vanilla) libtool script does correctly support multilib systems, and e.g. might start hard-coding RPATHS of /usr/lib64 everywhere, which is a Major Nightmare
^ does **not** correctly support! :)
1) Generally speaking, there is no need for such synchronization. (Actually, configure generates the libtool script from the included ltmain.sh.)
2) You could instead patch ltmain.sh to address this. That would be more resilient to changes in the autotools. Another alternative would be to build with "make LIBTOOL=/usr/bin/libtool". While that also exposes the package to changes in the system libtool (for better or for worse), it doesn't have the side-effects running libtoolize has.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Is this the same bug as 467270 ?
No. This isn't F10, either.
This is fixed in Raw Hide.