Clear out environment vars like PKG_CONFIG_PATH, LD_LIBRARY_PATH etc. #108
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These can break builds attempted within the chroot.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
These variables can break builds attempted within the chroot.
Example where this problem arises:
On my system I have various libraries the sysadmin has installed into
/usr/pkg/libthat programs I have compiled outside of JuNest link against. So I have those in PKG_CONFIG_PATH. But then I found things I build inside JuNest got linked to libraries like libselinux.so which should never happen with Arch! My solution was to manually unset all these variables before firing up JuNest.