{chem}[foss/2026.1] eOn v2.16.0#26435
Open
HaoZeke wants to merge 7 commits into
Open
Conversation
…-13.3.0.eb, Meson-1.8.2-GCCcore-13.3.0.eb, Rust-1.88.0-GCCcore-13.3.0.eb, quill-11.1.0-GCCcore-13.3.0.eb, metatensor-0.2.2-GCCcore-13.3.0.eb, metatensor-torch-0.10.0-foss-2024a.eb, metatomic-torch-0.1.15-foss-2024a.eb and patches: Meson-1.8.2_reenable-binutils-workaround.patch, Rust-1.70_sysroot-fix-interpreter.patch
Retarget upstream contribution from foss-2024a/GCCcore-13.3.0 to the current common toolchain foss-2026.1 (GCCcore 15.2.0). Drop Rust/cargo-c/Meson GCCcore-13.3.0 backports already present on develop for GCCcore-15.2.0. Keep only true gaps: eOn, quill, metatensor stack, CapnProto-1.4.0 on 15.2.0. Site validation of recipe mechanics (readcon cargo-c stage, CWD subshell, feedstock surface) was on EESSI foss-2024a; PyTorch 2.9.1 and xtb 6.7.1 remain explicit 2024a pins until those land on 2026.1.
HaoZeke
changed the title
Transitional PyTorch 2.9.1 is foss-2024a (Python 3.12.3). Recipes on foss-2026.1 use Python 3.14.2, so %(pyshortver)s expands to 3.14 and breaks EBROOTPYTORCH site-packages / Torch_DIR / libtorch / torch_path. Use python3.12 for all paths under EBROOTPYTORCH in eOn, metatensor-torch, and metatomic-torch. eOn own-install still uses %(pyshortver)s.
Keep technical notes only (PyTorch/xtb generation pins, python3.12 layout under EBROOTPYTORCH, Meson CWD subshell). No site/host/PR meta.
HaoZeke
changed the title
Contributor
|
Please check https://docs.easybuild.io/policies/ai/ |
…cdylib Build-verified on a from-scratch foss-2026.1 stack: - Eigen 5.0.0 guards Eigen/Core with EIGEN_CORE_MODULE_H instead of EIGEN_CORE_H, so the Eigen-aware safemath helpers (safe_normalized) silently compile away and every consumer TU fails. Patch accepts either guard (same fix applied upstream). - The cargo-c-built readcon-core cdylib is copied in via postinstallcmds, bypassing RPATH compiler wrappers and failing rpath-mode sanity checks: patchelf --force-rpath --set-rpath $ORIGIN, with patchelf as builddep. eonclient 2.16.0 then runs with an empty environment, linking torch/xtb/capnp/metatomic/readcon.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
New easyconfigs for eOn 2.16.0 on foss-2026.1 (GCCcore 15.2.0), plus companions not already on develop for this generation.
Files
e/eOn/eOn-2.16.0-foss-2026.1.eb-- MesonNinja; metatomic + xTB + Cap'n Proto serve + rgpot; stages rgpot/readcon-core; cargo-c install of readcon into a builddir prefix (subshell so Meson CWD stays clean)q/quill/quill-11.1.0-GCCcore-15.2.0.eb-- logging dep (not on develop)m/metatensor/metatensor-0.2.2-GCCcore-15.2.0.eb-- core C lib from CXX release tarballm/metatensor-torch/metatensor-torch-0.10.0-foss-2026.1.eb-- TorchScript bindings (CMakeNinja)m/metatomic-torch/metatomic-torch-0.1.15-foss-2026.1.eb-- metatomic Torch C++ (CMakeNinja)c/CapnProto/CapnProto-1.4.0-GCCcore-15.2.0.eb-- GCCcore recipe; develop only has 1.4.0 on GCCcore-14.3.0Already on develop (not re-added)
Rust-1.94.1-GCCcore-15.2.0, cargo-c-0.10.23-GCCcore-15.2.0, Meson-1.10.2-GCCcore-15.2.0, and other foss-2026.1 stack pieces (Python 3.14.2, SciPy-bundle 2026.05, ...).
Why some GCCcore recipes
In EasyBuild, pure compiler-toolchain libraries use GCCcore, not foss. That is normal for CapnProto / quill / metatensor-core. Pins are GCCcore-15.2.0 to match foss-2026.1 -- not a GCCcore-13.3.0 backport dump.
Cross-generation deps (temporary)
develop has no PyTorch--foss-2026.1 and no xtb--gfbf-2026.1 yet, so eOn (and the torch C++ companions) pin:
foss-2024a PyTorch installs under Python 3.12, while this recipe set uses Python 3.14.2. Paths under
$EBROOTPYTORCHtherefore usepython3.12explicitly (not%(pyshortver)s).Testing
Full eOn + metatomic stack was built and sanity-checked on foss-2024a (same recipe mechanics: readcon cargo-c stage, CMakeNinja torch libs, CXX metatensor tarballs). This PR is a foss-2026.1 retarget of those recipes; a full robot install of the 2026.1 set has not been run as part of this contribution.