On Tue, 2006-05-23 at 20:54 -0500, Jason L Tibbitts III wrote: > >>>>> "p" == paul <paul@xxxxxxxxxxxxxxxxxxxxxx> writes: > > p> ERROR 0001: file > p> '/usr/lib64/gnome-build-1.0/backends/libgbf-mkfile.so.0.0.1' > p> contains a standard rpath '/usr/lib64' in [/usr/lib64] > > Some references: > > http://fedoraproject.org/wiki/ToshioKuratomi > Rather than my personal page (which is a bit of a rat's nest :-) you can find more official information here:: http://fedoraproject.org/wiki/Extras/Schedule/RpathCheckBuildsys That page has a more detailed explanation of the rpath problem in general. It includes several workarounds for it when the rpath is being dragged in by libtool, including the workaround listed on my wiki page. It doesn't seem to mention the less intrusive measure of %configure --disable-rpath but that mostly works with applications, not with libtool-munged library builds. -Toshio
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-extras-list mailing list fedora-extras-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-extras-list
