Red Hat Bugzilla – Bug 139199
"freetype-config --libs" output is evil on amd64
Last modified: 2008-02-14 12:23:05 EST
danw@blorple:vte> rpm -q freetype-devel
danw@blorple:vte> freetype-config --libs
-L/usr/lib64 -Wl,--rpath -Wl,/usr/lib64 -lfreetype -lz
The "don't output libdir if it's -L/usr/lib" hack needs to be
updated to know about lib64
Assuming nobody objects, I'll commit upstream and put in our package
in a few days.
2004-11-16 Owen Taylor <firstname.lastname@example.org>
* builds/unix/freetype-config.in: Supress -L$libdir for
/usr/lib64 as well as /usr/lib. (Reported by Dan Winship -
I assume this also removes the horrible -Wl,--rpath -Wl,/usr/lib64 ?
That is just so wrong!
I was trying to test an alternative build of Mesa, using LD_LIBRARY_PATH to make
ppracer use the alternative build, but it got ignored by ld.so because of rpath,
which took me 2 hours to find out and workaround!
AFAIK, Rawhide already contains fixed to that effect (comment #3) -- can we get
them into FC4 as well?
Bumping product version.
(In reply to comment #4)
> AFAIK, Rawhide already contains fixed to that effect (comment #3) -- can we get
> them into FC4 as well?
The actual rawhide fix for the rpath problems was in Bug 160247
And Carl, just fyi: 173818 and 173819 bugs depend on this or need ugly
workarounds to avoid rpath problems.
What is the RPM version that contains this fix? I can't seem to find it, FC5 has
this bug, and it's going to start biting Mozilla packages before too long.
Benjamin, are you seeing the rpath output with the FC5 version of
The FC5 package definitively has the changes mentioned by Owen.
Sorry, got confused: FC4 is broken and FC5 is fixed.
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
This bug seems to have been fixed in Fedora Core 5.
Fedora Core 4 is not maintained anymore.
Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.