openmpi v5.0.1

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

• Dependencies have been updated if changed: see upstream
• Tests have passed
• Updated license if changed and license_file is packaged

Information about this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. 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.

Closes: #128

Pending Dependency Version Updates

Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.

Name	Upstream Version	Current Version
openmpi	5.0.1

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: false to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis by source code inspection shows a discrepancy between it and the the package's stated requirements in the meta.yaml.

Packages found by source code inspection but not in the meta.yaml:

• cython

_{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 https://github.com/regro/cf-scripts/actions/runs/7283816198, 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.

[leofang]

(Let's wait until #128 is in.)

[regro-cf-autotick-bot]

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

[dalcinl]

@leofang Now I see a lot of warnings in some of my GHA workflows: https://github.com/mpi4py/mpi4py/actions/runs/7294886629/job/19880465619#step:6:21

[fv-az1456-243:03807] pmix_mca_base_component_repository_open: unable to open /home/runner/micromamba/envs/cover/lib/prte/prte_mca_prtereachable_netlink: 
    dlopen error: libnl-route-3.so.200: cannot open shared object file: No such file or directory
    Perhaps a missing symbol, or compiled for a different version of prte? (ignored)

[dalcinl]

@leofang I think we have to add an explicit dependency on the libnl package (Linux only). Should we make a new build for this version?

[leofang]

@dalcinl I am not sure I fully understand -- Didn't we build fine without libnl? Is this because in our (limited) tests we could not capture this issue, as Open MPI dynamically links to it? But if we didn't add it to build/host, how would Open MPI know to build support for it?

If we are to fix it, I feel it's better we fix v5.0.0 (rebuild it with build number bumped) before the update to v5.0.1. WDYT?

[dalcinl]

Didn't we build fine without libnl?

My guess is that libnl is installed as a system package in the (RHEL-compatible) docker image used for building. However, once these packages are installed in a GHA runner, they do not work out of the box because libnl is not installed by default.

If we are to fix it, I feel it's better we fix v5.0.0 (rebuild it with build number bumped) before the update to v5.0.1. WDYT?

Definitely. I'll try to submit a PR.