Skip to content

add gsi-ncdiag@1.1.3#62

Closed
AlexanderRichert-NOAA wants to merge 46 commits into
JCSDA:release/2.1from
AlexanderRichert-NOAA:gsi-ncdiag-for-2.1
Closed

add gsi-ncdiag@1.1.3#62
AlexanderRichert-NOAA wants to merge 46 commits into
JCSDA:release/2.1from
AlexanderRichert-NOAA:gsi-ncdiag-for-2.1

Conversation

@AlexanderRichert-NOAA
Copy link
Copy Markdown
Collaborator

Add gsi-ncdiag@1.1.3 for release/2.1

climbfuji and others added 30 commits January 28, 2026 13:58
…rsions (spack#45)

* Add py-setuptools@73.0.1; add conflict for py-numpy@2.4 with py-setuptools newer than @73 if depending on python@3.11.11
…iles (create symbolic links for backward compatibility) (spack#43)

* Remove crtm-fix@2.3.0_emc and crtm@2.3.0_emc; update crtm-fix for all remaining versions: retain original directory structure, link requested files to top-level 'fix' dir
* Enable all CRTM tests
* perl-clone: add compiler dependency (spack#719)
* perl-xml-parser: add compiler dependency (spack#718)

---------

Co-authored-by: Alex Richert <alexander.richert@noaa.gov>
Co-authored-by: Krishna Chilleri <krishnachilleri@gmail.com>
…pack#2926)

Some example targets (e.g. v4l2) use math functions such as sin(), but libm
was not listed explicitly on the link line. Older toolchains linked this
transitively, but newer GCC/binutils reject this with “DSO missing from
command line”. Add -lm explicitly to make the link robust and portable.
…pack#2926) (spack#51)

Some example targets (e.g. v4l2) use math functions such as sin(), but libm
was not listed explicitly on the link line. Older toolchains linked this
transitively, but newer GCC/binutils reject this with “DSO missing from
command line”. Add -lm explicitly to make the link robust and portable.

Co-authored-by: Mathias Anselmann <mathias.anselmann@posteo.de>
Bug fix to compile py-protobuf@4.24.4 with gcc@14. Newer versions of py-protobuf don't need the bug fix, and older versions already have a conflict with gcc@14. But we need exactly this version for py-cylc-flow, which is nitpicky about its dependencies.
…g symbols in libimf.so/libirc.so (spack#4092)

* Add variant fix_rt_linkage to intel-oneapi-compilers, run patchelf on libimf.so and libirc.so during the installation of intel-oneapi-runtime to add the missing symbols from libm.so.6 and libc.so.6

* [@spackbot] updating style on behalf of climbfuji

---------

Co-authored-by: climbfuji <climbfuji@users.noreply.github.com>
New variant `fix_rt_linkage` for intel-oneapi-compilers to fix missing symbols in libimf.so/libirc.so (spack-packages spack#4092)
…_spack_stack

codee: add v2026.1.1& v2026.1.2 (spack-packages spack#4526)
mathomp4 and others added 16 commits April 29, 2026 12:52
Bug fix in repos/spack_repo/builtin/packages/py_pyhdf/package.py for Intel oneAPI 2026.0.0
…ck_stack_dev

Bug fixes for scalasca, scorep, py-pyhdf for Intel oneAPI, including oneapi@2026.0.0
Copy link
Copy Markdown
Collaborator

@climbfuji climbfuji left a comment

Choose a reason for hiding this comment

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

Unfortunately, the merge from spack-stack-dev brings in many more updates than just the bufr and gsi-ncdiag updates. Can we cherry-pick those updates instead, please?

@AlexanderRichert-NOAA
Copy link
Copy Markdown
Collaborator Author

That's weird, I must have done this from the wrong branch...

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.

5 participants