Skip to content
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

Update spack.yaml and/or build instructions to work with recent oneapi versions #260

Open
oparry-ukaea opened this issue Oct 31, 2024 · 3 comments · May be fixed by #262
Open

Update spack.yaml and/or build instructions to work with recent oneapi versions #260

oparry-ukaea opened this issue Oct 31, 2024 · 3 comments · May be fixed by #262

Comments

@oparry-ukaea
Copy link
Contributor

oparry-ukaea commented Oct 31, 2024

Since version 2024.0, the intel-oneapi-compilers spack package no longer contains the "classic" intel compilers (see e.g. here)

so

spack load intel-oneapi-compilers@2024
spack compiler find

Won't generate an intel@x.y spec in compilers.yaml.

We could either

  1. Change the build instructions to install icc etc., separately and register them with spack or
  2. Remove the %intel tags from spack.yaml

The tags were apparently added to avoid excessive memory consumption when building numpy with earlier versions of the oneapi compilers, but that no longer seems to be an issue with 2024.1.0, as far as I can tell.

I also found I needed to drop the Scotch version requirement; version 6 failed to build with [email protected].

@JamesEdgeley
Copy link
Contributor

To add to this - you have to use at least spack 0.22 to have [email protected] included in the package.py

@cmacmackin
Copy link
Contributor

I think someone said the more recent versions of oneapi are able to build Numpy (which I believe is what we were using the legacy compilers for). So hopefully we can remove the %intel tags.

@oparry-ukaea
Copy link
Contributor Author

Yep, just removing them worked fine for me (and @JamesEdgeley I believe)

@JamesEdgeley JamesEdgeley linked a pull request Oct 31, 2024 that will close this issue
15 tasks
@JamesEdgeley JamesEdgeley linked a pull request Oct 31, 2024 that will close this issue
15 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants