Provide a workaround of macos SIP in the build system #16
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mac SIP (System Integrity Protection) was introduced in El Capitan (10.11) in 2015 and it disabled
DYLD_*LIBRARY_PATHfor some protected binaries (theDYLD_LIBRARY_PATHandDYLD_FALLBACK_LIBRARY_PATHare purged when launching the processes).makeis among the binaries influenced by SIP. Assume that we have aMakefile:and run it by supplying the environment variables. The
dyldenvironment variables are not gone, surprisingly:Consequently, we no longer can set the
dyldvariables outsidemakeand send them to processes spawned inmake. A workaround is to use an include file inMakefile. Assume we have a file namesetup.mk:RUNENV ?= DYLD_LIBRARY_PATH=. DYLD_FALLBACK_LIBRARY_PATH=.The
Makefileis modified to:python3is a custom installed Python binary. (If you use the systempython, which is a protected binary, this trick won't work.) Running make and the value stored in the include file can be passed to thepython3sub-processes: