Steps to reproduce

If you have a build cache with multiple GCCs at the same version, but built with a different glibc, Spack ultimately always errors during concretization with

Cannot satisfy 'glibc@=X.Y'

The reason is likely that the compiler is identified by name@version somewhere, and that this translates into multiple requirements on glibc for the node that depends on this compiler.

Error message

No response

Information on your system

• Spack: 1.2.0.dev0 (e61534c)
• Builtin repo: spack/spack-packages@298ae09
• Python: 3.11.4
• Platform: darwin-sequoia-m4

General information

• I have run spack debug report and reported the version of Spack/Python/Platform
• I have searched the issues of this repo and believe this is not a duplicate
• I have run the failing commands in debug mode and reported the output