All,
On 21/02/2005, at 6:36 PM, Nigel Stanger wrote:
On 21/2/2005 1:49 AM, Peter O'Gorman at [EMAIL PROTECTED] spake thus:
If I recall correctly, the problems come when you have an app that needs
fontconfig and also needs a lib that uses the new fontconfig, both the older
fontconfig in /usr/X11R6/lib and the new one will be loaded by the dynamic
linker and it becomes anyone's guess as to which symbols will be used. But I
may not be recalling correctly, so I hope that someone will correct me if
I'm wrong.
This sounds like what happened to me with libfreetype in my ploticus2
package. I have it depending on the fink-installed version, but couldn't
ensure that it didn't use the X11-installed one. My solution was to add
-dylib_file /usr/X11R6/lib/libfreetype.6.dylib:/sw/lib/libfreetype.6.dylib
(with /sw appropriately abstracted, of course) to the link flags. It's
intended (I think) for situations where you have a single copy of the
library installed in a non-default location, but it seems to work just as
well when the library exists in both the default and a non-default location.
Check in the ld man page.
I've been using a combination of SetLDFLAGS: -L%p/lib/freetype2/lib -Wl,-search_paths_first, and carefully crafted Makefiles - it's working (albeit with a small amount of set-up), but at least I'm not clobbering the packages that work fine with the X11 installed freetype2.
-t
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
