DYLD_LIBRARY_PATH messes up applications
Imported from the Apple Support Forums via the Wayback Machine 🔗
Hi all,
i've got a strange problem with some libs i installed from MacPorts and the environment variable DYLD
LIBRARYPATH ...
First of all, i'm not sure whether this is the right forum to ask this, so if there is any better forum / newsgroup, please let me know.
The problem is the following.
I installed the TIFF library via MacPorts, because it is needed by some other software that i want to compile. (FYI: that other software uses the good old 'configure; make; make install' - triad.)
In order for that other software to find the libs when i run it, i need to set the environment variable DYLD
LIBRARYPATH to something like "/opt/local/lib:..." (I think)
However, when i put that in my .cshrc, and then run, for instance, 'opendiff' i get the strange error message:
dyld: lazy symbol binding failed: Symbol not found:
_cgTIFFSetErrorHandler
Referenced from: /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
Expected in: /opt/local/lib/libTIFF.dylib
The strange thing is that there is no libTIFF.dylib in /opt/local/lib!
There are just these:
% ls libtiff*
libtiff.3.dylib* libtiff.dylib@ libtiffxx.3.dylib* libtiffxx.dylib@
libtiff.a libtiff.la* libtiffxx.a libtiffxx.la*
I also don't get why it
expects libTIFF to be in /opt/local/lib ?
Now, i
could manually set and unset DYLD
LIBRARYPATH whenever i run that other software or a built-in app, resp., but that is, of course, very cumbersome.
Does anyone have an idea?
Could some kind soul please shed some light on this strange behavior?
Should i be using DYLD
FALLBACK_LIBRARYPATH??
I've reviewed the man page of dyld, but it is not quite clear to me.
(I'm coming from a unix world, so this DYLD
LIBRARYPATH business is not quite familiar yet.)
Thanks a lot in advance.
Best regards,
Gabriel.
5 replies
Sign in or join Beachball Help to reply.
- 0
- 0
- 0
- 0
- 0