On Mar 20, 2009, at 8:00 PM, Ryan Schmidt wrote:
On Mar 20, 2009, at 13:20, Yolande Serra wrote:
Not sure this will help, but if you defined a DYLD_LIBRARY_PATH in
your .bashrc or .profile get rid of it.
The libraries that macs point to are found assuming this variable
is not defined. Somewhere buried in the system it has a path to
its own libs. You mess this up when you define dynamic library
paths.
I agree with Yolande: it sounds like you have DYLD_LIBRARY_PATH set,
and you should not.
I'll note that there are cases requiring this environment variable. If
this is one of those, then you can probably use
DYLD_FALLBACK_LIBRARY_PATH instead. See http://developer.apple.com/documentation/DeveloperTools/Conceptual/DynamicLibraries/100-Articles/DynamicLibraryUsageGuidelines.html
for more information about load libraries.
Chris
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
