DYLD_LIBRARY_PATH and make

App & System Services Core OS
gtoronto
gtoronto OP
Created Jul ’15
Replies 9
Boosts 0
Views 19k
Participants

Recently upgraded to the latest El Cap beta 15A216g. I have several build steps (Qt/clang/make/etc) that rely on DYLD_LIBRARY_PATH being set so that the proper libraries can be found. If I do this:


$ DYLD_LIBRARY_PATH=/path/to/libicu make

uic /Users/gtoronto/build/test/test.ui

dyld: Library not loaded: libicui18n.46.dylib

Referenced from: /usr/local/Qt-5.2.1/lib/QtCore.framework/Versions/5/QtCore

Reason: image not found


However if I do this:


$ DYLD_LIBRARY_PATH=/path/to/libicu uic /Users/gtoronto/build/test/test.ui


Then the file gets generated correctly. This started happening only when upgrading El Cap.

Replies  9
Boosts  0
Views  19k
Participants  
aburgh
aburgh OP
Jul ’15

It may have been changed in the name of security. On Yosemite:


bash-3.2$ DYLD_PRINT_LIBRARIES=1 X=1 /usr/bin/printenv
dyld: loaded: /usr/bin/printenv
dyld: loaded: /usr/lib/libSystem.B.dylib
dyld: loaded: /usr/lib/system/libcache.dylib
...
dyld: loaded: /usr/lib/libc++.1.dylib
dyld: loaded: /usr/lib/libDiagnosticMessagesClient.dylib
X=1
DYLD_PRINT_LIBRARIES=1
TERM_PROGRAM=Apple_Terminal
...


But on El Capitan, all the `dyld: loaded:` messages are not printed and DYLD_PRINT_LIBRARIES is not in the list of variables, but X is. I have the same problem with makefiles that you do.

0
Fritzt
Fritzt OP
Aug ’15

Having exactly the same issue. Our cross-platform build system (written in Python and using Qt qmake + make) is broken on El Capitan, disabling system integrity protection doesn't prevent this. Is there any way to allow passing of the DYLD_ variables to shells and using them from there? At least I would expect this behavior to respect the system integrity protection settings!

0
Fritzt
Fritzt OP
Aug ’15

filed as bug report 22300976

0
khoyt
khoyt OP
Oct ’15

Since I ran into this too, from the System Integrity Protection Guide:



Spawning children processes of processes restricted by System Integrity Protection, such as by launching a helper process in a bundle with NSTask or calling the exec(2) command, resets the Mach special ports of that child process. Any dynamic linker (dyld) environment variables, such as DYLD_LIBRARY_PATH, are purged when launching protected processes.


0
ChrisMacGregor
ChrisMacGregor OP
Mar ’22

This entitlement appears to be the answer:

https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_security_cs_allow-dyld-environment-variables?language=objc

0
DYLD_LIBRARY_PATH and make
First post date Last post date
 
 
Q