Check LD_LIBRARY_PATH on setup #580
Open
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
|
This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. |
|
I have to check this more carefully when I have more time. Thank you for your contribution! Sorry for taking so long to look at this. |
TimDettmers
added
medium priority
|
Related: #1041 (comment) |
Titus-von-Koeller
force-pushed
the
main
branch
2 times, most recently
from
9b72679 to
7800734
Compare
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.
Issue:
Instructions when compiling to source require setting the destination of binaries in env var LD_LIBRARY_PATH.
This env is not checked during library setup, so unshipped self-compiled binaries will remain undetected.
Soln:
Adds a check to LD_LIBRARY PATH.