Closed CodeGat closed 2 months ago
Probably it would be good to submit the changes to the FMS package upstream.
There's an upstream version of fms at https://github.com/spack/spack/blob/develop/var/spack/repos/builtin/packages/fms/package.py
Hi @micaeljtoliveira , Do you use large_file
and/or internal_file_nml
variants?
Hi @CodeGat , Probably drop the copying of fms
SPD. Spack v0.21 fms
is only missing two variants and shouldn't impact your CI.
Hi @micaeljtoliveira , Do you use large_file and/or internal_file_nml variants?
Yes. Otherwise I wouldn't have bothered adding them ;)
Edit: if you don't add them, the model won't work correctly.
Hi @micaeljtoliveira , Can you please submit the patch upstream? They are default false in the SPD. Can you please elaborate how you use them? Are they default true in FMS' build system?
Hi @micaeljtoliveira , Can you please submit the patch upstream? They are default false in the SPD. Can you please elaborate how you use them? Are they default true in FMS' build system?
Yes, sure, I can submit upstream. +large_file
is set explicitly in the environment definition. Looks like internal_file_nml
is not set, but I'm afraid I don't remember exactly why. The only thing I'm quite sure is that both are set by in CESM, which was used as a template for OM3.
In this PR:
COSIMA/spack_packages
packages required for the OM3spack.yaml
- ~fms
~,fortranxml
at https://github.com/COSIMA/spack_packages/commit/a65eaf418730f7f132be3061e64b5f8c05c475caReferences #91