On Feb 20, 2018, at 08:34, Joshua Kordani wrote: > Not the OP, but regarding DYLD_LIBRARY_PATH, I don't understand how to make > use of dylib's provided by macports in my own programs without setting this > flag. I've read in several places that, esp with macports, this should not > be necessary, but I don't know what the *right way* is.
What problem or error message are you encountering when you do not set DYLD_LIBRARY_PATH?