Recipes using deprecated versions of GCC

[albestro]

From a quick grep, this should be the list of recipes using a deprecated version of GCC.

./recipes/cp2k/2025.1/mc/compilers.yaml
./recipes/cp2k/2025.1/gh200/compilers.yaml
./recipes/cp2k/2024.1/mc/compilers.yaml
./recipes/cp2k/2024.1/gh200/compilers.yaml
./recipes/cp2k/2024.2/mc/compilers.yaml
./recipes/cp2k/2024.2/gh200/compilers.yaml
./recipes/cp2k/2024.3/mc/compilers.yaml
./recipes/cp2k/2024.3/gh200/compilers.yaml
./recipes/arbor/v0.9/mc/compilers.yaml
./recipes/arbor/v0.9/gh200/compilers.yaml
./recipes/prgenv-nvfortran/24.11/gh200/compilers.yaml
./recipes/vasp/v6.4.2/gh200/compilers.yaml
./recipes/vasp/v6.4.3/gh200/compilers.yaml
./recipes/vasp/v6.5.0/gh200/compilers.yaml
./recipes/sirius/v7.5/a100/compilers.yaml
./recipes/julia/24.9/gh200/compilers.yaml
./recipes/paraview/13/mc/compilers.yaml
./recipes/mch/v5/compilers.yaml
./recipes/mch/v7/compilers.yaml
./recipes/mch/climana/24.7/compilers.yaml
./recipes/mch/climana/24.10/compilers.yaml
./recipes/mch/v6/compilers.yaml
./recipes/mch/v8/compilers.yaml
./recipes/visit/3.4.1/mc/compilers.yaml
./recipes/editors/24.7/compilers.yaml
./recipes/linalg/24.11/gh200/compilers.yaml
./recipes/lammps/2024/gh200/compilers.yaml
./recipes/wcp/icon/v1/gh200/compilers.yaml
./recipes/wcp/icon/v1/a100/compilers.yaml
./recipes/netcdf-tools/2024/x86/compilers.yaml
./recipes/netcdf-tools/2024/arm64/compilers.yaml
./recipes/linalg-complex/24.11/gh200/compilers.yaml
./recipes/prgenv-gnu/24.2/gh200/compilers.yaml
./recipes/prgenv-gnu/24.7/gh200/compilers.yaml
./recipes/prgenv-gnu/24.11/gh200/compilers.yaml
./recipes/prgenv-gnu/24.11/a100/compilers.yaml
./recipes/gromacs/2024/gh200-mpi/compilers.yaml
./recipes/gromacs/2023/gh200-mpi/compilers.yaml
./recipes/namd/3.0/gh200/compilers.yaml

AFAIK these recipes will not build as they are and spack concretization phase might fail with cryptic messages like the following.

==> Error: failed to concretize `squashfs default_compression=zstd`, `[email protected] languages='c,c++'` for the following reasons:
     1. Cannot satisfy '[email protected]'
     2. Cannot satisfy '[email protected]'
        required because [email protected] languages='c,c++' requested explicitly 
     3. Cannot satisfy '[email protected],12.2,13.1:' and '[email protected]
        required because [email protected] languages='c,c++' requested explicitly 
        required because @11.3,12.2,13.1: is a requirement for package gcc 
          required because [email protected] languages='c,c++' requested explicitly . You could consider setting `concretizer:unify` to `when_possible` or `false` to allow multiple versions of some packages.

Moreover in general it might be a good idea not to stick to a specific minor version of a compiler.