-
-
Notifications
You must be signed in to change notification settings - Fork 12
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.
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
Rebuild for openmpi 5 #34
Rebuild for openmpi 5 #34
Conversation
…nda-forge-pinning 2024.05.24.20.53.51
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 ( |
osx failure:
|
7eb99fe
to
31a41be
Compare
everything's passing except mac+arm+openmpi, which is failing at Find_MPI_Fortran. No info as to why that fails, of course. |
Could it just be the issue related to MPI constants in common blocks that the new Apple linker broke? Do you remember the related MUMPS issue? |
I think that was this one, which seemed to have been resolved by a mumps-specific This one is CMake failing to find MPI_Fortran at all, which I don't understand. Presumably setting the right variable will do it, but FindMPI is so elaborate and CMake's debug output is so unclear, I don't know where to start. |
Something fishy is going on. Notice the following output. I've installed the package locally, and the
|
I tried to reproduce locally (with the |
@dalcinl it's there, but |
But running |
@minrk What about passing |
You're right, I realize it's compile-time that's failing, not link, so LDFLAGS wouldn't be relevant. Added If that works, the real question is why mac + openmpi + cross-compile is the only combination where this isn't on the default search path. Probably related to the fact that openmpi compiler wrappers are in both the build and host env. |
|
Looks like this was a deliberate choice in the new v5 release. I also believe the issue is related to cross-compilation and a mismatch between the native vs cross prefixes. |
it's the same in 4.x as well. Something might have changed in the default wrapper arguments to prevent them being found (or it could be a change in cmake FindMPI), but the install location is the same. I opened open-mpi/ompi#12600 because every fortran package I can find puts .mod files in include, not lib, so it really seems like a mistake to me, just one that doesn't come up very often. |
It looks like the install directory hasn't changed in at least 8 years, so I don't think it's a recent choice. |
This PR has been triggered in an effort to update openmpi5.
Notes and instructions for merging this PR:
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 theconda-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 https://github.com/regro/cf-scripts/actions/runs/9231606986 - please use this URL for debugging.