Skip to content

openmpi 4.1.7 #192

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 262 commits into
base: 4.x
Choose a base branch
from
Open

openmpi 4.1.7 #192

wants to merge 262 commits into from

Conversation

@dalcinl
Copy link
Contributor

@dalcinl dalcinl commented Mar 6, 2025 •
edited
Loading

Checklist

  • Used a personal fork of the feedstock to propose changes
  • Bumped the build number (if the version is unchanged)
  • Reset the build number to 0 (if the version changed)
  • Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
  • Ensured the license file is being packaged.

jakirkham and others added 30 commits March 28, 2023 04:02
@jakirkham
Drop extra <space>
1566c0b
@jakirkham
Bump build/number to 2
0092d50
@jakirkham
Align on GCC 9 (w/CUDA 11.0) on Linux
a1663f3 
GCC 7 (used with CUDA 10.2) has configuration errors due to missing
features. Plus all other architectures use GCC 9 (with CUDA 11.0). So go
ahead and align on GCC 9 (with CUDA 11.0).
MNT: Re-rendered with conda-build 3.24.0, conda-smithy 3.23.1, and co…
eac1137 
…nda-forge-pinning 2023.03.28.09.32.54
@jakirkham
Drop cos7 from Linux x86_64 image name
5d52d97 
The CUDA 11.0 image on Linux `x86_64` is already on CentOS 7 (as opposed
to CentOS 6 with older CUDA images). So drop the `cos7` portion from the
name.
MNT: Re-rendered with conda-build 3.24.0, conda-smithy 3.23.1, and co…
b1c2e7f 
…nda-forge-pinning 2023.03.28.09.32.54
@jakirkham
Update to GCC 10
6005eb0 
Switch to CUDA 11.1 to allow updating to GCC 10.
MNT: Re-rendered with conda-build 3.24.0, conda-smithy 3.23.1, and co…
a0bc3d3 
…nda-forge-pinning 2023.03.28.22.53.26
@regro-cf-autotick-bot
updated v5.0.0
42a61ad
@regro-cf-autotick-bot
MNT: Re-rendered with conda-build 3.27.0, conda-smithy 3.27.1, and co…
af96fa9 
…nda-forge-pinning 2023.10.26.11.34.06
@dalcinl
recipe: Update build and test scripts
8540c16
@dalcinl
recipe: Upgrade linux64 to CUDA 11.2
cfadcd3
@dalcinl
MNT: Re-rendered with conda-build 3.26.1, conda-smithy 3.30.2, and co…
5b6c074 
…nda-forge-pinning 2023.12.21.09.51.46
@leofang
Merge pull request conda-forge#128 from regro-cf-autotick-bot/5.0.0_h…
cfad5e8 
…822a68

openmpi v5.0.0
@dalcinl
recipe: Add libnl dependency on Linux
6a4279d
@dalcinl
recipe: bump build number
bfc9e21
@dalcinl @leofang
recipe: Remove run_export packages from run section
0612218 
Co-authored-by: Leo Fang <[email protected]>
@leofang
Merge pull request conda-forge#133 from dalcinl/fix-recipe-libnl
1e7008b 
recipe: Add libnl dependency on Linux
@dalcinl
recipe: Set mca_base_component_show_load_errors=0
5398207
@dalcinl
recipe: bump build number
d22a8f0
@dalcinl
Merge pull request conda-forge#134 from dalcinl/fix-missing-libcuda-w…
b3da828 
…arning

Fix missing libcuda warning
@regro-cf-autotick-bot
updated v5.0.1
f2b86eb
@dalcinl
recipe: Fix configure with CUDA
7e1efee
@leofang
Merge pull request conda-forge#135 from regro-cf-autotick-bot/5.0.1_h…
c577e78 
…da4da5

openmpi v5.0.1
@jakirkham
Add cuda_compiler for zip_keys
4b9534b
MNT: Re-rendered with conda-build 3.28.2, conda-smithy 3.30.2, and co…
aa316f7 
…nda-forge-pinning 2024.01.05.22.51.09
@jakirkham
Merge conda-forge/main into conda-forge-admin/conda_forge_admin_120
f469c86
@jakirkham
Add CUDA 11.8 migrator
9a95fe2
@jakirkham
Bump to CUDA 11.8
7352c1d
MNT: Re-rendered with conda-build 3.28.2, conda-smithy 3.30.2, and co…
3e2b3dd 
…nda-forge-pinning 2024.01.05.22.51.09
minrk and others added 13 commits December 16, 2024 12:58
@minrk
don't unbundle prrte
f1d5e8d 
openmpi 6 forks prrte, so no point unbundling it now
@minrk
MNT: Re-rendered with conda-build 24.9.0, conda-smithy 3.45.0, and co…
3d075f9 
…nda-forge-pinning 2024.12.15.16.05.58
@minrk
use newly split libfabric-devel
5002689
@minrk
avoid duplicate keys caused by faulty bot/lint parsers
3f275a9
@minrk
build with libfabric-devel 1.19
ca39ccd 
for best abi compatibility
@minrk
MNT: Re-rendered with conda-build 24.9.0, conda-smithy 3.45.0, and co…
45a403e 
…nda-forge-pinning 2024.12.18.11.57.07
@j34ni
Merge pull request conda-forge#188 from minrk/prrte-pmix
84cf2c1 
use external libpmix
@regro-cf-autotick-bot
Rebuild for ucx 1.18
4a2f167
@regro-cf-autotick-bot
MNT: Re-rendered with conda-build 25.1.1, conda-smithy 3.45.4, and co…
e1937df 
…nda-forge-pinning 2025.01.24.17.08.54
@dalcinl
Merge pull request conda-forge#189 from regro-cf-autotick-bot/rebuild…
d1e5e82 
…-ucx118-0-1_h0a6fe3

Rebuild for ucx 1.18
@regro-cf-autotick-bot
updated v5.0.7
5ad85d6
@regro-cf-autotick-bot
MNT: Re-rendered with conda-build 25.1.2, conda-smithy 3.45.4, and co…
06b5883 
…nda-forge-pinning 2025.02.15.07.01.42
@dalcinl
Merge pull request conda-forge#190 from regro-cf-autotick-bot/5.0.7_h…
ce820d4 
…56db24

openmpi v5.0.7
@dalcinl
Copy link
Contributor Author

dalcinl commented Mar 6, 2025

@conda-forge-admin rerender

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Mar 6, 2025 •
edited
Loading

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/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/13707071556. Examine the logs at this URL for more detail.

@dalcinl
Copy link
Contributor Author

dalcinl commented Mar 6, 2025

@minrk What would be the correct approach for building an older release series? Should I merge main while adjusting the version number?

@minrk
Copy link
Member

minrk commented Mar 7, 2025

backporting changes main might be useful (e.g. the activation scripts), but you don't need to. Merge conflicts might be a pain, but just reviewing the changes that would occur from:

git checkout main recipe

and opting to keep what looks appropriate makes sense to me. If this built successfully, I'd probably leave it and move on.

If you want this branch to get dependency bump PRs, we should add

bot:
  abi_migration_branches:
    - 4.x

to conda-forge.yml on main, which will lead to this branch being included in the bot PRs for dependency version bumps.

@LourensVeen LourensVeen mentioned this pull request Apr 15, 2025
Merged
5 tasks
@astrofrog astrofrog removed their request for review April 25, 2025 13:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@beckermr beckermr Awaiting requested review from beckermr beckermr is a code owner

@bekozi bekozi Awaiting requested review from bekozi bekozi is a code owner

@leofang leofang Awaiting requested review from leofang leofang is a code owner

@minrk minrk Awaiting requested review from minrk minrk is a code owner

@msarahan msarahan Awaiting requested review from msarahan msarahan is a code owner

@ocefpaf ocefpaf Awaiting requested review from ocefpaf ocefpaf is a code owner

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

10 participants

@dalcinl @conda-forge-admin @minrk @jakirkham @regro-cf-autotick-bot @leofang @beckermr @ktlim @ChenYuHo @j34ni