Skip to content

Added NVHPC compiler (Ursa, nvhpc@26.9) recipe changes and patches for several packages - #107

Open
natalie-perlin wants to merge 2 commits into
JCSDA:spack-stack-devfrom
natalie-perlin:ursa-nvhpc-26.9
Open

natalie-perlin wants to merge 2 commits into
JCSDA:spack-stack-devfrom
natalie-perlin:ursa-nvhpc-26.9

Conversation

@natalie-perlin

@natalie-perlin natalie-perlin commented Nov 9, 2026 •

Copy link
Copy Markdown

DESCRIPTION

Added several recipe changes and patches to build packages to build ufs-weather-module-env/1.0.0 module:

crtm@3.1.5
fms@2025.03
g2@3.5.1
mapl@2.69.1
esmf@9.0.0.b17
py_numpy@1.25
pango@1.54.0,

Tested along with the changes in the https://github.com/JCSDA/spack-stack PR# 2201

Spack-stack environment that includes only ufs-weather-model-env defines as shown below in the spack.yaml, builds successfully. A template is made under ./configs/templates/ufswm-dev. Modules and meta-modules are created correctly.

spack-stack.yaml environment specs section:

spack:
  concretizer:
    unify: when_possible

  view: false
  include:
  - site/packages_nvhpc-26.9.yaml
  - site
  - common/packages_nvhpc.yaml
  - common/modules_lmod.yaml
  - common

  specs:
  - ufs-weather-model-env ^esmf@=9.0.0b17 ^crtm@=3.1.5

  # Mapl with specific esmf tags (list all to avoid duplicate packages)
  - mapl@2.69.1 ^esmf@=9.0.0b17

  # Various esmf tags (list all to avoid duplicate packages)
  - esmf@=9.0.0b17

  # Various fms builds
  - fms +gfs_phys constants=GFS

  packages:
    # Turn on python variant for esmf
    esmf:
      require:
      - +python
    # Avoid duplicate builds of parallelio +pnetcdf and ~pnetcdf
    parallelio:
      require:
      - +pnetcdf
  config:
    install_tree:
      padded_length: 200

… build packages for ufs-weather-module-env module: crtm@3.1.5, fms@2025.03, pango@1.54.0, g2@3.5.1, mapl@2.69.1, esmf@9.0.0.b17, py_numpy@1.25

@climbfuji climbfuji left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These patches are narrow - mostly apply to just one version. Can they be generalized? Or should we add conflicts for other versions? To be discussed.

Regardless, each of these updates should be merged upstream in spack/spack-packages. Ideally one PR per package, and ideally upstream first and then cherry-picked here.


# https://github.com/JCSDA/spack-stack/issues/1088
patch("v3.1.0-skylabv8.installprefix.patch", when="@v3.1.0-skylabv8")
patch("crtm-3.1-nvhpc-compiler-flags.patch", when="@3.1.5 %nvhpc")

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is the patch named crtm-3.1-nvhpc if it only applies to 3.1.5?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants