Skip to content

Upstream Image: intel-oneapi-compilers explicitly use %gcc@13.2.0 - #325

Merged
CodeGat merged 2 commits into
v4from
upstream-intel-oneapi-compilers-depend-on-gcc13.2.0
Sep 9, 2026
Merged

CodeGat merged 2 commits into
v4from
upstream-intel-oneapi-compilers-depend-on-gcc13.2.0

Conversation

@CodeGat

@CodeGat CodeGat commented Sep 9, 2026

Copy link
Copy Markdown
Member

Background

Currently, the upstream image places no constraints on what compiler intel-oneapi-compilers builds with, so it opts for gcc@8.5.0 (the default external). When we place hard requirements on the version of gcc (eg. 13.2.0) used, as we propose in ACCESS-NRI/access-spack-packages#486 (currently prefer, will be require once we use this image), these conflict and concretization fails.

The PR

  • Make intel-oneapi-compilers explicitly need %gcc@13.2.0
    • NOTE: intel-oneapi-compilers-classic doesn't need this as it is not compiled
  • Update image version

@CodeGat CodeGat added type:bug Something isn't working priority:high A high priority issue - has an impact on core functionality for:v4 labels Sep 9, 2026
@CodeGat CodeGat self-assigned this Sep 9, 2026
@CodeGat
CodeGat requested a review from harshula September 9, 2026 05:31
Comment thread containers/.env Outdated
Comment thread containers/upstream/compilers.spack.yaml Outdated
@CodeGat
CodeGat force-pushed the upstream-intel-oneapi-compilers-depend-on-gcc13.2.0 branch from 256ec97 to f5c5d57 Compare September 9, 2026 05:42

@harshula harshula left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤞

@CodeGat
CodeGat merged commit 5538bba into v4 Sep 9, 2026
This was referenced Sep 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

for:v4 priority:high A high priority issue - has an impact on core functionality type:bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants