On Tue, 22 Jun 2010 14:36:01 +0900, Mamoru Tasaka wrote: > So actually for most cases, the case that rpath /usr/lib64 is > added (only for 64 bits arch) can be avoided by > ------------------------------------------------------------------------ > sed -i.libdir_syssearch -e \ > '/sys_lib_dlsearch_path_spec/s|/usr/lib |/usr/lib /usr/lib64 /lib > /lib64 |' \ configure > ------------------------------------------------------------------------ > i.e. just add the needed paths to sys_lib_dlsearch_path_spec in > configure (note that libtool in the build directory is generated > by configure) before calling %configure. - You can alternatively > do "autoreconf -fi", however calling autotools > is not recommended unless unavoidable. > ---------- To continue an old thread: is there any plan to update the current packaging guidelines? http://fedoraproject.org/wiki/Packaging/Guidelines#Beware_of_Rpath I've been using the DIE_RPATH_DIE hack for one of my packages, vala, for a long time, but today when working on an update for it I decided to try and get its compiler test suite working; it turns out that the only reason it's been failing all along was that the DIE_RPATH_DIE solution made it impossible to run the tests against an uninstalled copy of libvala, because, as you can guess, it requires using rpath. Adding /usr/lib and /usr/lib64 to the bundled libtool solved the problem nicely. Regards, -- Michel Alexandre Salim Fedora Project Contributor: http://fedoraproject.org/ Email: salimma@xxxxxxxxxxxxxxxxx | GPG key ID: 78884778 Jabber: hircus@xxxxxxxxxxxxx | IRC: hircus@xxxxxxxxxxxxxxxx () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments -- packaging mailing list packaging@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/packaging
