Peter Scheibel

## Compiler flag combination semantics The following attempts to describe cases where two sets of compiler flags are *complementary* based on my reading of [GCC](https://gcc.gnu.org/onlinedocs/gcc-13.2.0/gcc/Invoking-GCC.html). Loosely speaking, something like `-O3...

Broad approach based on discussion of above between @tgamblin @alalazo @psakievich @becker33 (each step here can be a separate PR): - first: relax .satisfies to be subset - next phase:...

Thanks, I likewise have not yet delivered on my promise: > (I'll check internally and get back to you on whether we'd want that sort of change, since we try...

@becker33 @alalazo FYI (you each appear in the `git blame` for the relevant function)

Apologies: I swapped up the order. There is an essentially identical problem though (if you edit packages.yaml, it is ignored). I've updated the description accordingly (swapping the order of compilers/packages...

> Do you see the warning? Yes (so again, apologies for being misleading in the the issue description): that message seems to come up even if for example the compilers.yaml...

The "silent" part of this is addressed by https://github.com/spack/spack/pull/42655 so I'll close this. Feel free to reopen if you think https://github.com/spack/spack/issues/38664 does not capture the rest of this.

Spack makes an effort not to use paths like `/usr/lib64` as RPATHs, and it looks like the `Library rpath:` entry in https://github.com/spack/spack/issues/42695#issuecomment-1961340394 includes that as well as `$ORIGIN/../lib64` - this...

(EDIT Feb. 28: still working on build) (EDIT Feb. 27: I thought I'd get to this by Monday, but will not have a chance until tomorrow to try a build...

@adityakavalur I've built one instance of paraview using an external (located in `/usr`) - the generated `pserver` executable does not contain a `/usr/lib64` RPATH. I'm trying to update the installation...