Branch: refs/heads/main
Revision: b9be834
Author: DanilaFe
Link: Use intel-classic in module builds by DanilaFe · Pull Request #20435 · chapel-lang/chapel · GitHub
Log Message:
Merge pull request #20435 from DanilaFe/use-intel-classic
Use intel-classic in module builds
The intel compiler has apparently switched from the "usual"
flavor to the Clang-based flavor. The two flavors have
incompatible build flags. Furthermore, some builds use
intel-classic(old version) as the target compiler, while
module builds are currently done with intel (new version)
as the gen compiler. This leads to an incompatibility, and
has been causing some builds to fail for a while. What's
more, we've not yet put any effort into migrating to the new
intel compiler; for the time being, it makes sense to build
with the same tool we've been using up until now.
See #20422 for some information about what exactly was
failing (intel-classic doesn't recognize a flag, while
intel does).
This PR switches the compiler used for module builds
to the "classic" version, which should resolve the
issues with incompatible flags. This should make
#20422 obsolete.
Reviewed by @ronawho - thank you!
TESTING
I've tested this by manually executing steps from
load_prgenv_intel and performing a complete build
afterwards. This worked as intended, but I don't know
how to exercise the setenv script in the way it's
normally used in CI.
Modified Files:
M util/build_configs/cray-internal/setenv-xc-x86_64.bash
Compare: https://github.com/chapel-lang/chapel/compare/4c48d6191fa2...b9be8341e69b