|
From: | Peter Dyballa |
Subject: | Re: 23.0.60; How to make some libraries link statically via pkg-config files? |
Date: | Tue, 19 Feb 2008 22:25:05 +0100 |
Am 19.02.2008 um 21:31 schrieb Stephen J. Turnbull:
That's not what's happening. I don't understand the Mac OS X dylib architecture in any depth, but I'm pretty sure that an object can request an object from a specific location to be dynamically linked (similar to the -rpath flag in GNU ld).
This is my impression too.
FWIW, my guess is that the reason you're seeing multiple instances of libraries is not that Mac OS X "presents" them, but because/usr/X11R6/lib/libXft.2.dylib (compatibility version 2.1.0, current version 2.1.0)is specifically requesting a different version from the one you get from /sw. Try running otool on /usr/X11R6/lib/libXft.2.dylib and see if the output corresponds to the unwanted versions.
It does show:/usr/X11R6/lib/libfontconfig.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/X11R6/lib/libexpat.0.dylib (compatibility version 0.4.0, current version 0.4.0) /usr/X11R6/lib/libfreetype.6.dylib (compatibility version 6.3.0, current version 6.3.0)
I was (I still am?) hoping that a statically linked library would satisfy these dependencies too.
-- Greetings Pete I hope to die before I *have* to use Microsoft Word. - Donald E. Knuth, 2001-10-02 in Tübingen.
[Prev in Thread] | Current Thread | [Next in Thread] |