Update Blueback compilers.yaml: add missing path to llvm-ar etc.
#1622
Conversation
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
areinecke
approved these changes
Apr 30, 2025
github-project-automation
bot
moved this from In Progress
to Done
in spack-stack-2.0.0 (2025 Q2-Q3)
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.
Summary
The Intel oneAPI compiler module on Blueback does not include the path to
llvm-aretc. This and other utilities in subdirectorycompilerare required for linking when using interprocedural optimization (-flto, formerly known as-ipo).Testing
Tested on Blueback (manually). No CI testing required.
Applications affected
None
Systems affected
Blueback
Dependencies
None
Issue(s) addressed
Link the issues addressed or resolved by this PR (use
Fixes #???for fully resolved issues)Checklist
All dependency PRs/issues have been resolved and this PR can be merged.