Describe the bug
I found a typo in configs/sites/tier1/atlantis/packages_oneapi.yaml: instead of the correct version 2025.0.3, the external intel-oneapi-runtime packages has version 2025.0.0, and more importantly, the compiler (%oneapi) also has 2025.0.0 instead of 2025.0.3.
This causes spack to build the packge intel-oneapi-runtime instead of using the external package. While this doesn't cause errors, it produces lots of warnings when running CMake, for example:
CMake Warning at drivers/CMakeLists.txt:41 (add_executable):
Cannot generate a safe runtime search path for target
diagnostic_unit_test.exe because files in some directories may conflict
with libraries in implicit directories:
runtime library [libiomp5.so] in /gpfs/neptune/spack-stack/oneapi-2025.0.3/compiler/2025.0/lib may be hidden by files in:
/gpfs/neptune/spack-stack/spack-stack-dev-20250221/envs/ne-oneifx-2025.0.3/install/oneapi/2025.0.3/intel-oneapi-runtime-2025.0.3-7xbummu/lib
Some of these libraries may not be found correctly.
To Reproduce
Look at output from CMake on Atlantis when building NEPTUNE
Expected behavior
spack should use the external package intel-oneapi-runtime
System:
Atlantis
Additional context
n/a
Describe the bug
I found a typo in
configs/sites/tier1/atlantis/packages_oneapi.yaml: instead of the correct version 2025.0.3, the external intel-oneapi-runtime packages has version 2025.0.0, and more importantly, the compiler (%oneapi) also has 2025.0.0 instead of 2025.0.3.This causes spack to build the packge
intel-oneapi-runtimeinstead of using the external package. While this doesn't cause errors, it produces lots of warnings when running CMake, for example:To Reproduce
Look at output from CMake on Atlantis when building NEPTUNE
Expected behavior
spack should use the external package
intel-oneapi-runtimeSystem:
Atlantis
Additional context
n/a