OpenMPI @1.10.3 builds but always hangs or segfaults on High Sierra

[mkuron (Michael Kuron)]

OpenMPI builds and installs fine on High Sierra, but even the simplest MPI programs hang after launching or segfault:

[mac:03395] *** Process received signal ***
[mac:03395] Signal: Segmentation fault: 11 (11)
[mac:03395] Signal code:  (0)
[mac:03395] Failing at address: 0x0
[mac:03395] [ 0] 0   libsystem_platform.dylib            0x00007fff552ebf5a _sigtramp + 26
[mac:03395] [ 1] 0   ???                                 0x0000000000000000 0x0 + 0
[mac:03395] [ 2] 0   libopen-pal.13.dylib                0x000000010439a270 event_process_active_single_queue + 464
[mac:03395] [ 3] 0   libopen-pal.13.dylib                0x0000000104396ac9 event_process_active + 137
[mac:03395] [ 4] 0   libopen-pal.13.dylib                0x0000000104395c5c opal_libevent2021_event_base_loop + 796
[mac:03395] [ 5] 0   libopen-rte.12.dylib                0x000000010430041f orte_progress_thread_engine + 47
[mac:03395] [ 6] 0   libsystem_pthread.dylib             0x00007fff552f56c1 _pthread_body + 340
[mac:03395] [ 7] 0   libsystem_pthread.dylib             0x00007fff552f556d _pthread_body + 0
[mac:03395] [ 8] 0   libsystem_pthread.dylib             0x00007fff552f4c5d thread_start + 13
[mac:03395] *** End of error message ***
Segmentation fault: 11

To reproduce, put the following into a file mpitest.c and run mpicc-openmpi-mp -o mpitest mpitest.c && ./mpitest:

#include <mpi.h>

int main (int argc, char *argv[])
{
	MPI_Init(&argc, &argv);
    MPI_Finalize();
	return 0;
}

To fix the issue, simply adapt the Portfile to install OpenMPI 3.0.0 instead of 1.10.3. I also tried 1.10.7, which exhibits the same problem. The 1.10 line is out of support anyway; 2.0 and 2.1 are still in support and 3.0 is the most recent one.

[mkuron (Michael Kuron)]

Note that this is with Apple's Clang compiler (openmpi-default port). With GCC (openmpi-gcc7 port), there is another unrelated issue #54993 where OpenMPI doesn't even build.

[seanfarley (Sean Farley)]

This should have been fixed with the update to 3.0.0. Please let me know if that's not correct.