Updates towards compiling full unified environment with Intel oneAPI compilers (icx, icpx, ifort) #450
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.
Description
Several unrelated updates and a rather important bug fix that bring us one step closer to compiling the entire unified environment with the mixed Intel oneAPI compilers (icx, icpx, ifort):
fckit
: Straightforward, Upstream PR for spack develop: Update fckit to build with Intel oneAPI compilers (icx, icpx) and nvhpc compilers spack/spack#45196 (includes an earlier update we made in spack-stack-dev for compiling withnvhpc
).qt
: First, pulled in updates (two mostrecent commits) for the package from spack develop, then added the workaround for oneAPI. Tested successfully on Blackpearl (compiledqt
andecflow
with oneAPI, then start ecflow server and ecflow GUI). Upstream PR for spack develop: Add support for compiling [email protected] with Intel oneAPI compilers (icx, icpx) spack/spack#45195lib/spack/env/cc
: I mistakenly copied the C++logic into the Fortran block and nobody noticed it. This fixes it. Note that the entirevcheck_flags
logic inlib/spack/env/cc
will eventually be replaced by a better solution. But since I am currently iterating with the spack developers on how that solution should look like (see Fix lib/spack/env/cc: pass Intel oneAPI flags to suppress deprecation… spack/spack#44588), let's merge this important bug fix now.Corresponding spack-stack PR: JCSDA/spack-stack#1195