Description of problem: In Fedora 10 libtool wasn't using rpath for {/usr,}/lib64 directories, but now in rawhide with libtool 2.2, it does. In F10 using autoreconf -f -i -v prevented libtool from using /usr/lib64 as rpath, now it's not working. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. try to make x86_64 for some package (for example ecryptfs-utils) with other rpath workarounds removed 2. 3. Actual results: rpmbuild fails because of /usr/lib64 rpath Expected results: libtool stops using {/usr,}/lib64 as rpath Additional info:
Yes, this seems to be causing packages which did not have rpath issues in F10 to acquire them after a rawhide rebuild. Maintainers are reticent to fix these because the problem is, ostensibly, in libtool. It seems that some of the stuff patched by libtool-1.5.24-multilib.patch is still present in its unpatched form in the current libtool 2.2.6 tree, but honestly I don't know enough about libtool to tell what part of the source is the actual libtool and which is the libtool-generated configure bits used to build it.
please try again with libtool-2.2.6-10.fc11 and reopen this bug when the problem still exists.
(In reply to comment #2) > please try again with libtool-2.2.6-10.fc11 and reopen this bug when the > problem still exists. works for me
Yes, I can verify that this is fixed.