Upstream Image: intel-oneapi-compilers explicitly use %gcc@13.2.0 - #325
Merged
Merged
Conversation
harshula
reviewed
Sep 9, 2026
harshula
reviewed
Sep 9, 2026
CodeGat
force-pushed
the
upstream-intel-oneapi-compilers-depend-on-gcc13.2.0
branch
from
September 9, 2026 05:42
256ec97 to
f5c5d57
Compare
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.
Background
Currently, the upstream image places no constraints on what compiler
intel-oneapi-compilersbuilds with, so it opts forgcc@8.5.0(the default external). When we place hard requirements on the version ofgcc(eg.13.2.0) used, as we propose in ACCESS-NRI/access-spack-packages#486 (currentlyprefer, will berequireonce we use this image), these conflict and concretization fails.The PR
intel-oneapi-compilersexplicitly need%gcc@13.2.0intel-oneapi-compilers-classicdoesn't need this as it is not compiled