Building ACCESS-OM2 on Archer2 (UK HPC)

[Aidan (Aidan Heerdegen, ACCESS-NRI Release Team Lead)]

@davemunday

This has allowed the remaining components to compile. I’ve uploaded the error and install logs, as they both have a lot of entries.

Hooray! Now at least it is possible to iterate from this point.

@davemunday

I have managed to compile oasis_mct after recalling that Archer2 uses different wrappers to mpif90, etc. I had to point to the correct ones in oasis_mct/package.py and then this package compiles without further issue

We have discussed compiler wrappers on Pawsey, which is also a Cray machine:

Spack and Cray HPC Architecture

@Scott mentioned some issues with the using spack on a Cray HPC system (setonix) because spack and the Cray uses it’s own compiler wrappers. The docs suggest this is a solved problem: Is there something else going on? See also this paper from 2017 on using spack on Cray HPCs

It shouldn’t be necessary to modify the spack package of an individual component for something like this. That is much better specified in the configuration for the HPC, or in the spack environment where the package is built.