Cameron Rutherford

@jeremylt ah - sorry for the confusion. I was generating these spack specs after having issues with a bigger environment. ```console ==> Concretized 3 specs: - vs7nw4o libceed@develop~cuda~debug+libxsmm~magma~occa~rocm build_system=makefile arch=darwin-sequoia-armv8.4a...

I filed spack issue https://github.com/spack/spack/issues/50167 to capture the stuff I presented at the beginning of the issue.

For CMake packages, you can override the compiler spec (and effectively discard the spack compiler wrapper) by specifying `CMAKE_{C/CCX}_COMPILER`. Since libCEED package is controlling its own compiler flags, I wonder...

To clarify, I think there are three distinct options to resolve this issue: 1. Don't use the Spack compiler wrapper at the `package.py` level in libCEED, avoiding this issue, but...

The difference between your CI job working and the Spack build failing is the Spack compiler wrapper. The compiler wrapper injects it's own plethora of flags, and then your specification...

@jedbrown yes. Here is a simple reproducer of the issue (simplified to not use the Spack compiler wrapper, but reproduces the same issue): `Makefile`: ```Makefile # Compiler and flags CC...

I think this suggests that this is a gcc bug that we should upstream a bug report for, and then work around locally. I don't quite understand Spack's philosophy here,...

I suppose one final option is to not have libCEED specify any compiler flags at the `package.py` level, but that's a touch more extreme of a suggestion. EDIT: This would...

Would a diff like this be what you are intending for the libCEED `package.py` then? ```diff diff --git a/var/spack/repos/builtin/packages/libceed/package.py b/var/spack/repos/builtin/packages/libceed/package.py index 948a35c8..07bea1ef 100644 --- a/var/spack/repos/builtin/packages/libceed/package.py +++ b/var/spack/repos/builtin/packages/libceed/package.py @@ -80,33 +80,7...

> @cameronrutherford seems to me gcc 7.5 is not supported anymore [see here](https://github.com/LLNL/hiop/actions/runs/10605563003/job/29394599640?pr=693#step:4:175) You find a new spack bug every day... https://github.com/spack/spack/issues/43919#issuecomment-2318321043 I think this is an issue in using...