Config for Mac Sonoma 14.6.1 with Command Line Tools 15.3

[srherbener]

This PR adds in the necessary configuration to get the latest MacOS and Command Line Tools versions working (14.6.1 and 15.3 respectively).

This PR includes a patch for FMS 2024.02 and a variant spec that builds shared (dylib) libraries. This makes it unnecessary to do the manual FMS build workaround that was recently published. The FMS patch is only needed for version 2024.02 in that the next version (2024.03) contains the update to the CMakeLists.txt file that adds in the shared library option.

Resolves JCSDA/spack-stack/issues/1211

[climbfuji]

Thanks for these updates. Any plans to send those upstream to spack develop?

[climbfuji]

Might be better to apply the patch in the same way as the spack developers suggested it for the bufr-query library.

[climbfuji]

spack develop PR for py-netcdf4 and py-ruamel-yaml-clib is here: spack#46184

Unfortunately, I couldn't cherry-pick the changes from this PR since everything was submitted in one commit. We should split this into one commit per package (as I did in spack#46184). We can cherry-pick those commits later and fix the conflicts in our branch.

[climbfuji]

Might be better to apply the patch in the same way as the spack developers suggested it for the bufr-query library.

Done as well.

[climbfuji]

I will create the upstream PR for fms tomorrow, but I am happy with the changes as they are now.

[climbfuji]

spack develop PR for py-netcdf4 and py-ruamel-yaml-clib is here: spack#46184

Unfortunately, I couldn't cherry-pick the changes from this PR since everything was submitted in one commit. We should split this into one commit per package (as I did in spack#46184). We can cherry-pick those commits later and fix the conflicts in our branch.

Pull request for fms in spack develop: spack#46238

[climbfuji]

spack develop PR for py-netcdf4 and py-ruamel-yaml-clib was merged into spack develop (spack#46184)

[srherbener]

Spack stack built successfully on my Mac, but when running ecbuild on jedi-bundle, the FMS::fms_r8 component was not found. Upon inspection, only the FMS::fms_r4 component was built. I think before both the r4 and r8 components were built. Is this an intended change?

[climbfuji]

Spack stack built successfully on my Mac, but when running ecbuild on jedi-bundle, the FMS::fms_r8 component was not found. Upon inspection, only the FMS::fms_r4 component was built. I think before both the r4 and r8 components were built. Is this an intended change?

None of my changes should have an effect on which version(s) get(s) built

[srherbener]

Spack stack built successfully on my Mac, but when running ecbuild on jedi-bundle, the FMS::fms_r8 component was not found. Upon inspection, only the FMS::fms_r4 component was built. I think before both the r4 and r8 components were built. Is this an intended change?

I think the changes here are okay. I think I found the issue in the spack-stack configuration. See this comment: JCSDA/spack-stack#1281 (comment)