Testing issue: openmpi@4.1.6 halting on initialization on m1 mac, apple-clang@14.0.0
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.1k
- Forks
- 2.5k
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 82
Description
Steps to reproduce the failure(s) or link(s) to test output(s)
$ spack spec -I openmpi@4.1.6%apple-clang@14.0.0~atomics~cuda~cxx~cxx_exceptions~gpfs~internal-hwloc~internal-pmix~java~legacylaunchers~lustre~memchecker~openshmem~orterunprefix+romio+rsh~singularity+static+vt+wrapper-rpath build_system=autotools fabrics=none schedulers=none arch=darwin-monterey-m1
Error message
Any program calling MPI_INIT halts and must be closed with CTRL+C.
Here is a very simple .cpp file to test the openmpi installation.
test.cpp
#include <mpi.h>
int main (int argc, char* args[]) {
MPI_Init(&argc, &args);
MPI_Finalize();
}
to run
>> spack load openmpi@4.1.6
>> mpic++ test.cpp
>> ./a.out
Information on your system or the test runner
Running on an M1 mac, OS Monterey 12.7.1, with apple-clang 14.0.0.
This issue does not exist with openmpi versions 4.1.5 and below.
Additional information
No response
General information
- I have reported the version of Spack/Python/Platform/Runner
- I have run
spack maintainers <name-of-the-package>and @mentioned any maintainers - I have uploaded any available logs
- I have searched the issues of this repo and believe this is not a duplicate
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the exact Spack spec on the stated M1 macOS and run the minimal test.cpp through spack load, mpic++, and ./a.out. Compare the behavior with openmpi 4.1.5 and earlier, then determine whether the issue is in Spack's package configuration or the 4.1.6 build; done means the initialization hang is explained and a verified resolution is recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- build-system, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100