GCOM fails to build with GCC

[Whyborn]

The GCOM package (or at least the most up to date version) fails with GCC. This causes CI failures for UM/UM7 builds (and probably those with UM dependencies), which shouldn't necessarily block merging as all of our release builds use Intel.

[manodeep]

Does this apply for both gcom and gcom4?

[aidanheerdegen]

UM CI builds fail anyway as the source code is currently inaccessible.

What is the context for these failures? If you're happy to not test against gcc you can modify the default tests by specify what manifests to test with. e.g. the cice4 disables gcc testing by only specifying an intel manifest

https://github.com/ACCESS-NRI/access-spack-packages/blob/main/.github/build-ci/manifests/cice4/

Same for cice5, which also specifies 3 different model contexts to test against

https://github.com/ACCESS-NRI/access-spack-packages/tree/main/.github/build-ci/manifests/cice5