-
Notifications
You must be signed in to change notification settings - Fork 47
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
Name clashes error in "spack module lmod refresh", Spack Stack 1.9.0 on S4 #1543
Comments
Looks like you skipped the check for duplicate packages after concretizing? |
Spot on, I forgot the duplicate checking step. I restarted the whole process and after concretizing I checked and found duplicates. How do I eliminate those duplicates? |
This is where the fun begins. First, you need to identify which package is installed twice and why. The ones you listed above with module name clashes all seem to be consequences of some lower-level package being built twice. Can you post the output from the check for duplicates here? |
@climbfuji, More details about the problem. I got this problem trying to have intel classic in addition to oneapi. Initially I said that it was oneapi, but after double check, it is only intel classic (2023) that is causing duplicates. oneapi 2024 is installing without problem.
|
I see two different versions of py-numpy, this must be the problem.
I guess there are some conflicts/limitations on which versions of numpy work with all packages in the unified environment, in addition to conflicts of certain versions of numpy with Intel classic. Please try to figure this out with JCSDA. |
Almost certainly it's related to
in |
When I fully remove py-numpy from my package file, the concretization fails with the message Let me add the content of
|
I removed |
Please be careful. We added those settings for a reason. Please try what @rickgrubin-noaa suggested, namely adding
to the
I am still hopeful that NOAA one day will tell us that we can switch back to using Intel MKL with the Intel Classic and LLVM compilers. Then all of this wouldn't be necessary. |
Describe the bug
spack module lmod refresh
step fails on S4 withError: Name clashes detected in module files
error message;A couple of packages seem to be installed twice with the same version number
To Reproduce
Steps to reproduce the behavior:
source setup.sh
spack stack create env --site s4 --template unified-dev --name ue.s4.oneapi --compiler oneapi
cd envs/ue.s4.oneapi
spack concretize --force 2>&1 | tee concretize.log
spack install --source --verbose --fail-fast 2>&1 | tee install.log
spack module lmod refresh
Expected behavior
The module refresh step should run smoothly without error message
System:
What system(s) are you running the code on? S4
Additional context
Below is the whole error message
The text was updated successfully, but these errors were encountered: