Repository navigation
Conversation
Contributor
Author
|
Wrong repo |
This file contains hidden or 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
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.
This Pull request:
The cppjit tests set
LD_LIBRARY_PATHto only the test directory, replacing the one from the environment. When ROOT is built with a compiler whose C++ standard library is found throughLD_LIBRARY_PATH, as with the LCG views, every cppjit test fails before running:or
Changes or fixes:
Prepend the test directory to the
LD_LIBRARY_PATHof the environment instead of replacing it, the same wayPYTHONPATHis set a few lines above.Checklist:
Tested on AlmaLinux 9 with the dev3 view (gcc 16): before, all 26 cppjit tests fail through ctest; after, all of them pass.