Is your feature request related to a problem?
For spack-stack-2.1, a few site configs need to be updated to address issues or complete work that didn't make it into spack-stack-2.0.
Describe the solution you'd like
Additional context
See discussion (comments) in #1835 for some of the site config build errors encountered during the spack-stack-2.0 release.
Is your feature request related to a problem?
For spack-stack-2.1, a few site configs need to be updated to address issues or complete work that didn't make it into spack-stack-2.0.
Describe the solution you'd like
py-scipybuild errors (inmesonstep) with Intel oneAPI compilers - @rickgrubin-noaa and@AlexanderRichert-NOAA@climbfujipy-scipybuild errors (inmesonstep) with Intel oneAPI compilers - @rickgrubin-noaa and@AlexanderRichert-NOAA@climbfujimodules.yamlfiles; bug fix in util/nrl/batch_install.sh #1911modules.yamlfiles; bug fix in util/nrl/batch_install.sh #1911ectransbuild errors (incmakestep) with GNU compilers), update oneapi to 2025.3.0 - @climbfuji and @rickgrubin-noaaspack ctrbuilds with a tier 1 site config for a container build that is more similar to how we install on bare-metal systems. @eap with input from EPIC; Clean up as part of this work:Revert spack-stack modifications of container builds in Spack engine code - @climbfujiwill be done on develop after the releaseRemovewill be done on develop after the releasespack stack ctrextension and associated unit tests - @climbfujiAdditional context
See discussion (comments) in #1835 for some of the site config build errors encountered during the spack-stack-2.0 release.