Rebuild for openmpi 5

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update openmpi5.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

---

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by - please use this URL for debugging.}

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[jan-janssen]

/home/conda/feedstock_root/build_artifacts/lammps_1718139432252/work/lib/lepton/asmjit/core/cpuinfo.cpp:18:12: fatal error: sys/auxv.h: No such file or directory
   18 |   #include <sys/auxv.h>
      |            ^~~~~~~~~~~~
compilation terminated.

[jan-janssen]

@conda-forge/core I struggle to find sys/auxv.h in sysroot=2.17. I have the same issue when I try to switch to the new stdlib format #194 . But when I explicitly specify sysroot_linux-64 2.17 # [linux] in the meta.yaml then it works fine.

[h-vetinari]

I believe you're running into the issues being discussed in conda-forge/openmpi-feedstock#143 / conda-forge/linux-sysroot-feedstock#63

[minrk]

I don't think this is quite the same as what's being discussed in ompi 5, but definitely related because this package itself requires 2.17.

I do think there's a problem in conda-smithy, because this PR specifies that c_stdlib_version is 2.17, but the rerender is still using 2.12 when it explodes the compiler variants. Fortunately, for this specific case, there's another way to force 2.17: set os_version: linux_64: cos7 in conda-forge.yml: conda-forge/conda-smithy#1950

But lammps will not be able to build against openmpi 5 until it supports plumed 2.9, because there are no openmpi 5 builds of plumed < 2.9. Looks like it has been submitted upstream: lammps/lammps#4177

The specific plumed patch suggests the version pinning was preemptive, assuming breakage would happen that didn't. So we could backport that patch here. Alternatively, wait for the next release, which I'm assuming is coming soon based on that PR.

[jan-janssen]

@conda-forge-admin, please rerun bot

[regro-cf-autotick-bot]

Due to the bot-rerun label I'm closing this PR. I will make another one as appropriate. This message was generated by https://github.com/regro/cf-scripts/actions/runs/10192340769 - please use this URL for debugging.