MSU hosts hercules / orion: require a version of openssl consistent with the OS-supplied version

[rickgrubin-noaa]

Description

spack-stack@{2.1.0, 2.0.0} builds, by default openssl@3 as specified in

configs/common/packages.yaml

    openssl:
      require:
      - +shared
      - '@3'

and on MSU hosts hercules and orion, this concretizes to openssl@3.4.1

Specified stack environments successfully build / install, but applications built against said environments fail when referencing openssl, as seen in:

jedi-bundle compilation fails with GNU spack-stack 2.0.0 on MSU Hercules (undefined reference to SSL_get0_group_name@OPENSSL_3.2.0) #1892

To Reproduce

Create / concretize / install any env (e.g. unified-dev) that builds openssl, and compile / link any code the depends on openssl, e.g. UFS WM regression tests

results in:

/work/noaa/epic/role-epic/UFS-WM/ufswm-orion-2.1/UFSATM/ccpp/physics/physics/Radiation/RRTMGP/rte-rrtmgp/rrtmgp-frontend/mo_gas_optics_rrtmgp.F90(922): 
[...]
ld: /apps/contrib/spack-stack/spack-stack-2.1.0/envs/ue-oneapi-2025.3.1/install/intel-oneapi-compilers/2025.3.1/curl-8.11.1-ni2noub/lib/libcurl.so.4: undefined reference to `SSL_get0_group_name@OPENSSL_3.2.0'

Expected Behavior

Code / applications built against the installed stack run as expected.

System, compiler, code, ...

What system(s) are you running the code on? Which compiler? Which version of the code? Any other details you can provide?

• hercules
  • spack-stack@{2.1.0, 2.0.0}
    • oneapi@2025.3.1
• orion
  • spack-stack@{2.1.0, 2.0.0}
    • oneapi@2025.3.1

Additional context

This issue does not manifest on other RDHPCS hosts (derecho, gaea-c6, ursa) as the system-installed openssl on those hosts satisfied the required symbols.