-
Notifications
You must be signed in to change notification settings - Fork 217
allow specifying location for RPATH wrapper scripts via rpath_wrappers_dir + also pass rpath_include_dirs when preparing build environment for extensions
#4596
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
5487954
Squash and rebase for 5.0.x branch
ocaisa 67b5a38
Add missing import
ocaisa 4c02482
No need to create the wrapper directory or modify permissions
ocaisa 6684446
Fix updated test
ocaisa 79495df
Add rpath_wrappers_dir build option
ocaisa f1482cd
Unused import
ocaisa f88ab4f
Fix tests
ocaisa 8cc4dc3
Merge branch 'easybuilders:develop' into export_rpath_wrappers
ocaisa 224e83a
Merge branch 'easybuilders:develop' into export_rpath_wrappers
ocaisa dd4d4db
Add warning if wrappers are being overwritten
ocaisa 539bb56
Merge branch 'export_rpath_wrappers' of github.com:ocaisa/easybuild-f…
ocaisa ef951d9
Add warning if wrappers are being overwritten
ocaisa 64a4b19
remove --rpath-wrappers-dir configuration option
boegel 841b82b
copy rpath_args.py script alongside RPATH wrapper scripts, and use it
boegel e9e7870
avoid that test_toolchain_prepare_rpath_external produces output
boegel c863497
make sure that parent directory for RPATH wrappers exists before copy…
boegel 4606da6
use relative path to rpath_args.py script when creating RPATH wrapper…
boegel 62e0a28
only copy rpath_args.py script and use relative path to it when custo…
boegel f6f5e93
fix excessively long comments
boegel 71cc6eb
Merge pull request #47 from boegel/export_rpath_wrappers
ocaisa File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The omission of this in the original call looks like a bug to me, so I have added it back...but I can't be 100%
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It likely doesn't actually matter as the wrappers will probably already have been prepared by the time this is called by an extension.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Definitely a bug, I don't see a reason not to pass through
rpath_include_dirshere.See also call to
self.toolchain.prepareinEasyBlock.prepare_step, where we do pass this down.This is a genuine bug, and since this call to
toolchain.prepareinstalls additional wrappers, the compiler wrapper from the parent is shadowed. Although I guess the RPATH wrapper script for the extension will use the RPATH wrapper script that was generated for the parent? Not sure about that (I'll check).I'm a bit puzzled why this hasn't caused a whole bunch of problems, so it seems that somehow this hasn't actually been an issue in practice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm pretty sure it has no impact, the wrappers have a protective clause to ensure that they do not wrap themselves.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(see https://github.com/easybuilders/easybuild-framework/pull/4596/files#diff-c1bad9950fee9f74b59e255119ea04ce41e9d9ce8cfa9fa94e831c8d314d106dR1041)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It has no impact for 2nd extension, where we'll pick up on wrapper created for first extension.
But the RPATH wrapper that was created for the "parent" will no longer be found (because the build environment is reset before build environment for first extension is set up), and so the installation of extensions will be done with an incorrect RPATH wrapper script in which
rpath_include_dirsis not picked up.That's bad since
$ORIGIN/../lib& co are specified that way (see howself.rpath_wrappers_diris defined inEasyBlock.prepare_step).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hold on, the resetting of build environment before starting installation of extensions is not correct I think, I'm going through things in detail now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
rpath_include_dirsmechanism was implemented in #2358, which shows that it's only picked up by the "parent"toolchain.prepare, the call totoolchain.preparefor extensions was overlooked. That confirms to me this is a genuine bug.I'm still a bit puzzled why this doesn't cause real trouble though, or how it has flown under the radar...