(re)set environment variables used by cargo in prepare step of Cargo easyblock#3774
Merged
Micket merged 1 commit intoeasybuilders:developfrom Jun 13, 2025
Merged
Conversation
Member
Author
|
Test report by @boegel Overview of tested easyconfigs (in order)
Build succeeded for 1 out of 1 (1 easyconfigs in total) |
cargo in prepare step of Cargo easyblock
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.
(created using
eb --new-pr)This fixes a failure in the RPATH sanity check for easyconfigs using
CargoPythonPackagewhen Rust was built withstablechannel (see also #3691), for example (withmaturin-1.6.0-GCCcore-13.3.0.ebbeing installed on top of EESSI):The underlying reason is that the path to
gccwas being resolved too early, before the build environment that includes setting up the RPATH wrappers was set up (inpreparestep), leading to the path to the non-wrappedgccbeing picked up:The fix in #3698 is insufficient to deal with the fallout caused by #3691, because the
load_modulemethod in which theset_cargo_varsmethod is called is only used when extensions are being installed, so it only helps with installations done withCargoPythonBundle...