> On Dec 10, 2015, at 5:19 PM, Hanspeter Niederstrasser 
> <f...@snaggledworks.com> wrote:
> 
> 
> On Thu, December 10, 2015 3:49 pm, Alexander Hansen wrote:
>> 
>>> On Dec 10, 2015, at 13:42, Jacques Bloch
>>> <jacques.bl...@physik.uni-regensburg.de> wrote:
>>> 
>>> Somehow i was able to use DYLD_LIBRARY_PATH with armadillo which i put
>>> in ~/opt/lib on my system.
>>> 
>>> Jacques
>>> 
>>> Sent from my iPhone
>> 
>> 
>> That may be implementation-dependent.  If armadillo just wants _a_
>> DYLD_LIBRARY_PATH and doesn’t rely on it being an environment variable,
>> that may still work.
>> 
>> Fionna:~ hansen$ DYLD_LIBRARY_PATH="/sw/lib"
>> Fionna:~ hansen$ export DYLD_LIBRARY_PATH
>> Fionna:~ hansen$ printenv DYLD_LIBRARY_PATH
>> Fionna:~ hansen$ echo $DYLD_LIBRARY_PATH
>> /sw/lib
> 
> From what I understand, DYLD_LIBRARY_PATH still works, but it just doesn't
> get passed to subshells.
> 
> So
> 
> DYLD_LIBRARY_PATH=/foo/lib /bin/sh BAR.sh
> 
> will use /foo/lib successfully, but
> 
> DYLD_LIBRARY_PATH=/foo/lib ./BAR.sh
> 
> (where BAR.sh starts with #!/bin/sh) will fail.
> 

Specifically, all DYLD_* environment variables get removed when running any 
binary that is considered “protected”. That includes anything in /bin, /sbin, 
/usr/bin and /usr/sbin. So the problem is that you can’t pass DYLD_* to /bin/sh 
since it’s protected. If you were to use fink’s bash it WILL work since it 
isn’t protected but that would mean a dependency on bash. That’s kind of an 
expensive work around.

DYLD_FALLBACK_LIBRARY_PATH is the one exception that does get passed but it’s 
useless for overriding an already installed library.

Daniel


Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

------------------------------------------------------------------------------
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to