Commit a1bd79e
spack-environment: use %gcc for py-tensorflow, revert all:require to '%gcc'
The previous fix (any_of: ['%gcc', '%clang'] in all:require) allowed
py-tensorflow to concretize with %clang but caused ~24 packages to be
duplicated (once compiled with %gcc, once with %clang).
Root cause analysis: py-tensorflow@2.20's own compiler constraints only
require gcc@12+ and clang@16+; both gcc@13.3.0 and clang@17.0.6 are
valid. The '%clang' requirement in packages.yaml was a preference, not
a technical necessity.
In Spack v1.1+, 'all: require: %gcc' applies to ALL packages without
exception and cannot be overridden by package-specific require entries
(both constraints apply simultaneously). Removing the '%clang' preference
from py-tensorflow:require eliminates the compiler conflict entirely,
and the all:require:'%gcc' preference guides py-tensorflow to use %gcc
consistently with all other packages.
Also update the misleading comment that claimed 'require for all is
overwritten by package-specific entries' — this was incorrect for
Spack v1.1+.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>1 parent 97b39b5 commit a1bd79e
1 file changed
Lines changed: 4 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
11 | 11 | | |
12 | 12 | | |
13 | 13 | | |
14 | | - | |
15 | | - | |
16 | | - | |
| 14 | + | |
| 15 | + | |
| 16 | + | |
17 | 17 | | |
18 | 18 | | |
19 | 19 | | |
20 | 20 | | |
21 | 21 | | |
22 | 22 | | |
23 | 23 | | |
24 | | - | |
| 24 | + | |
25 | 25 | | |
26 | 26 | | |
27 | 27 | | |
| |||
0 commit comments