Re: [OMPI users] OpenMPI 5.0.0 & Intel OneAPI 2023.2.0 on MacOS 14.0:
We develop and build with clang on macOS frequently; it would be surprising if it didn't work. That being said, I was able to replicate both errors report here. One macOS Sonoma with XCode 15.x and the OneAPI compilers: * configure fails in the PMIx libevent section, complaining about how it can't find a suitable libevent * Filed github issue https://github.com/open-mpi/ompi/issues/12051 to track * build fails complaining that it can't find * Filed github issue https://github.com/open-mpi/ompi/issues/12052 to track Thanks for reporting these issues! From: users on behalf of Matt Thompson via users Sent: Monday, November 6, 2023 1:38 PM To: Open MPI Users Cc: Matt Thompson ; Christophe Peyret Subject: Re: [OMPI users] OpenMPI 5.0.0 & Intel OneAPI 2023.2.0 on MacOS 14.0: I have built Open MPI 5 (well, 5.0.0rc12) with Intel oneAPI under Rosetta2 with: $ lt_cv_ld_force_load=no ../configure --disable-wrapper-rpath --disable-wrapper-runpath \ CC=clang CXX=clang++ FC=ifort \ --with-hwloc=internal --with-libevent=internal --with-pmix=internal I'm fairly sure the two wrapper flags are not needed, I just have them for historical reasons (long ago I needed them and until they cause an issue, I just keep all my flags around). Maybe it works for me because I'm using clang instead of icc? I can "get away" with that because the code I work on is nearly all Fortran so the C compiler is not as important to us. And all the libraries we care about seem happy with mixed ifort-clang as well. If you don't have a driving need for icc, maybe this will let things work? On Mon, Nov 6, 2023 at 8:55 AM Volker Blum via users mailto:users@lists.open-mpi.org>> wrote: I don’t have a solution to this but am interested in finding one. There is an issue with some include statements between OneAPI and XCode on MacOS 14.x , at least for C++ (the example below seems to be C?). It appears that many standard headers are not being found. I did not encounter this problem with OpenMPI, though, since I got stuck at an earlier point. My workaround, OpenMPI 4.1.6, compiled fine. While compiling a different C++ code, these missing headers struck me, too. Many of the include related error messages went away after installing XCode 15.1 beta 2 - however, not all of them. That’s as far as I got … sorry about the experience. Best wishes Volker Volker Blum Vinik Associate Professor, Duke MEMS & Chemistry https://aims.pratt.duke.edu https://bsky.app/profile/aimsduke.bsky.social > On Nov 6, 2023, at 4:25 AM, Christophe Peyret via users > mailto:users@lists.open-mpi.org>> wrote: > > Hello, > > I am tring to compile openmpi 5.0.0 on MacOS 14.1 with Intel oneapi Version > 2021.9.0 Build 20230302_00. > > I enter commande : > > lt_cv_ld_force_load=no ../openmpi-5.0.0/configure > --prefix=$APP_DIR/openmpi-5.0.0 F77=ifort FC=ifort CC=icc CXX=icpc > --with-pmix=internal --with-libevent=internal --with-hwloc=internal > > Then > > make > > And compilation stops with error message : > > /Users/christophe/Developer/openmpi-5.0.0/3rd-party/openpmix/src/util/pmix_path.c(55): > catastrophic error: cannot open source file > "/Users/christophe/Developer/openmpi-5.0.0/3rd-party/openpmix/src/util/pmix_path.c" > #include > ^ > > compilation aborted for > /Users/christophe/Developer/openmpi-5.0.0/3rd-party/openpmix/src/util/pmix_path.c > (code 4) > make[4]: *** [pmix_path.lo] Error 1 > make[3]: *** [all-recursive] Error 1 > make[2]: *** [all-recursive] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all-recursive] Error 1 > -- Matt Thompson “The fact is, this is about us identifying what we do best and finding more ways of doing less of it better” -- Director of Better Anna Rampton
Re: [OMPI users] OpenMPI 5.0.0 & Intel OneAPI 2023.2.0 on MacOS 14.0:
I have built Open MPI 5 (well, 5.0.0rc12) with Intel oneAPI under Rosetta2 with: $ lt_cv_ld_force_load=no ../configure --disable-wrapper-rpath --disable-wrapper-runpath \ CC=clang CXX=clang++ FC=ifort \ --with-hwloc=internal --with-libevent=internal --with-pmix=internal I'm fairly sure the two wrapper flags are not needed, I just have them for historical reasons (long ago I needed them and until they cause an issue, I just keep all my flags around). Maybe it works for me because I'm using clang instead of icc? I can "get away" with that because the code I work on is nearly all Fortran so the C compiler is not as important to us. And all the libraries we care about seem happy with mixed ifort-clang as well. If you don't have a driving need for icc, maybe this will let things work? On Mon, Nov 6, 2023 at 8:55 AM Volker Blum via users < users@lists.open-mpi.org> wrote: > I don’t have a solution to this but am interested in finding one. > > There is an issue with some include statements between OneAPI and XCode on > MacOS 14.x , at least for C++ (the example below seems to be C?). It > appears that many standard headers are not being found. > > I did not encounter this problem with OpenMPI, though, since I got stuck > at an earlier point. My workaround, OpenMPI 4.1.6, compiled fine. > > While compiling a different C++ code, these missing headers struck me, too. > > Many of the include related error messages went away after installing > XCode 15.1 beta 2 - however, not all of them. That’s as far as I got … > sorry about the experience. > > Best wishes > Volker > > > Volker Blum > Vinik Associate Professor, Duke MEMS & Chemistry > https://aims.pratt.duke.edu > https://bsky.app/profile/aimsduke.bsky.social > > > On Nov 6, 2023, at 4:25 AM, Christophe Peyret via users < > users@lists.open-mpi.org> wrote: > > > > Hello, > > > > I am tring to compile openmpi 5.0.0 on MacOS 14.1 with Intel oneapi > Version 2021.9.0 Build 20230302_00. > > > > I enter commande : > > > > lt_cv_ld_force_load=no ../openmpi-5.0.0/configure > --prefix=$APP_DIR/openmpi-5.0.0 F77=ifort FC=ifort CC=icc CXX=icpc > --with-pmix=internal --with-libevent=internal --with-hwloc=internal > > > > Then > > > > make > > > > And compilation stops with error message : > > > > > /Users/christophe/Developer/openmpi-5.0.0/3rd-party/openpmix/src/util/pmix_path.c(55): > catastrophic error: cannot open source file > "/Users/christophe/Developer/openmpi-5.0.0/3rd-party/openpmix/src/util/pmix_path.c" > > #include > > ^ > > > > compilation aborted for > /Users/christophe/Developer/openmpi-5.0.0/3rd-party/openpmix/src/util/pmix_path.c > (code 4) > > make[4]: *** [pmix_path.lo] Error 1 > > make[3]: *** [all-recursive] Error 1 > > make[2]: *** [all-recursive] Error 1 > > make[1]: *** [all-recursive] Error 1 > > make: *** [all-recursive] Error 1 > > > > -- Matt Thompson “The fact is, this is about us identifying what we do best and finding more ways of doing less of it better” -- Director of Better Anna Rampton
Re: [OMPI users] OpenMPI 5.0.0 & Intel OneAPI 2023.2.0 on MacOS 14.0:
Hello everyone, I find your contribution very interesting, because I also use Apple and have been thinking about how I could best install OpenMPI on this device. For example, I have already installed the GNU C-compiler 14 and am very happy with it in conjunction with R - Project. My macOS version is already 14.2. Now, how can we build a community here so that we can network together for this topic? Best regards Z. Matthias > On Montag, Nov. 06, 2023 at 3:05 PM, Volker Blum via users > mailto:users@lists.open-mpi.org)> wrote: > I don’t have a solution to this but am interested in finding one. > > There is an issue with some include statements between OneAPI and XCode on > MacOS 14.x , at least for C++ (the example below seems to be C?). It appears > that many standard headers are not being found. > > I did not encounter this problem with OpenMPI, though, since I got stuck at > an earlier point. My workaround, OpenMPI 4.1.6, compiled fine. > > While compiling a different C++ code, these missing headers struck me, too. > > Many of the include related error messages went away after installing XCode > 15.1 beta 2 - however, not all of them. That’s as far as I got … sorry about > the experience. > > Best wishes > Volker > > > Volker Blum > Vinik Associate Professor, Duke MEMS & Chemistry > https://aims.pratt.duke.edu > https://bsky.app/profile/aimsduke.bsky.social > > > On Nov 6, 2023, at 4:25 AM, Christophe Peyret via users > > wrote: > > > > Hello, > > > > I am tring to compile openmpi 5.0.0 on MacOS 14.1 with Intel oneapi Version > > 2021.9.0 Build 20230302_00. > > > > I enter commande : > > > > lt_cv_ld_force_load=no ../openmpi-5.0.0/configure > > --prefix=$APP_DIR/openmpi-5.0.0 F77=ifort FC=ifort CC=icc CXX=icpc > > --with-pmix=internal --with-libevent=internal --with-hwloc=internal > > > > Then > > > > make > > > > And compilation stops with error message : > > > > /Users/christophe/Developer/openmpi-5.0.0/3rd-party/openpmix/src/util/pmix_path.c(55): > > catastrophic error: cannot open source file > > "/Users/christophe/Developer/openmpi-5.0.0/3rd-party/openpmix/src/util/pmix_path.c" > > # include > > ^ > > > > compilation aborted for > > /Users/christophe/Developer/openmpi-5.0.0/3rd-party/openpmix/src/util/pmix_path.c > > (code 4) > > make[4]: *** [pmix_path.lo] Error 1 > > make[3]: *** [all-recursive] Error 1 > > make[2]: *** [all-recursive] Error 1 > > make[1]: *** [all-recursive] Error 1 > > make: *** [all-recursive] Error 1 > > >
Re: [OMPI users] OpenMPI 5.0.0 & Intel OneAPI 2023.2.0 on MacOS 14.0:
I don’t have a solution to this but am interested in finding one. There is an issue with some include statements between OneAPI and XCode on MacOS 14.x , at least for C++ (the example below seems to be C?). It appears that many standard headers are not being found. I did not encounter this problem with OpenMPI, though, since I got stuck at an earlier point. My workaround, OpenMPI 4.1.6, compiled fine. While compiling a different C++ code, these missing headers struck me, too. Many of the include related error messages went away after installing XCode 15.1 beta 2 - however, not all of them. That’s as far as I got … sorry about the experience. Best wishes Volker Volker Blum Vinik Associate Professor, Duke MEMS & Chemistry https://aims.pratt.duke.edu https://bsky.app/profile/aimsduke.bsky.social > On Nov 6, 2023, at 4:25 AM, Christophe Peyret via users > wrote: > > Hello, > > I am tring to compile openmpi 5.0.0 on MacOS 14.1 with Intel oneapi Version > 2021.9.0 Build 20230302_00. > > I enter commande : > > lt_cv_ld_force_load=no ../openmpi-5.0.0/configure > --prefix=$APP_DIR/openmpi-5.0.0 F77=ifort FC=ifort CC=icc CXX=icpc > --with-pmix=internal --with-libevent=internal --with-hwloc=internal > > Then > > make > > And compilation stops with error message : > > /Users/christophe/Developer/openmpi-5.0.0/3rd-party/openpmix/src/util/pmix_path.c(55): > catastrophic error: cannot open source file > "/Users/christophe/Developer/openmpi-5.0.0/3rd-party/openpmix/src/util/pmix_path.c" > #include > ^ > > compilation aborted for > /Users/christophe/Developer/openmpi-5.0.0/3rd-party/openpmix/src/util/pmix_path.c > (code 4) > make[4]: *** [pmix_path.lo] Error 1 > make[3]: *** [all-recursive] Error 1 > make[2]: *** [all-recursive] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all-recursive] Error 1 >
Re: [OMPI users] OpenMPI 5.0.0 & Intel OneAPI 2023.2.0 on MacOS 14.0:
Hello, I am tring to compile openmpi 5.0.0 on MacOS 14.1 with Intel oneapi Version 2021.9.0 Build 20230302_00. I enter commande : lt_cv_ld_force_load=no ../openmpi-5.0.0/configure --prefix=$APP_DIR/openmpi-5.0.0 F77=ifort FC=ifort CC=icc CXX=icpc --with-pmix=internal --with-libevent=internal --with-hwloc=internal Then make And compilation stops with error message : /Users/christophe/Developer/openmpi-5.0.0/3rd-party/openpmix/src/util/pmix_path.c(55): catastrophic error: cannot open source file "/Users/christophe/Developer/openmpi-5.0.0/3rd-party/openpmix/src/util/pmix_path.c" # include ^ compilation aborted for /Users/christophe/Developer/openmpi-5.0.0/3rd-party/openpmix/src/util/pmix_path.c (code 4) make[4]: *** [pmix_path.lo] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all-recursive] Error 1
Re: [OMPI users] OpenMPI 5.0.0 & Intel OneAPI 2023.2.0 on MacOS 14.0:
Volker -- If that doesn't work, send all the information requested here: https://docs.open-mpi.org/en/v5.0.x/getting-help.html From: users on behalf of Volker Blum via users Sent: Saturday, October 28, 2023 8:47 PM To: Matt Thompson Cc: Volker Blum ; Open MPI Users Subject: Re: [OMPI users] OpenMPI 5.0.0 & Intel OneAPI 2023.2.0 on MacOS 14.0: Thank you very much, Matt! That sounds like it. Will try when I next get to work on this. (and I would really like to make 5.0.0 work …) (I lost a few extra hours afterwards, with the OneAPI based OpenMPI 4.1.6 mpic++ not being able to find various C++ headers - and I think this is due to Apple XCode. mpif90 and mpicc work and the situation for mpic++ did improve with XCode 5.1 beta 2, which is why I am suspecting this is an XCode related problem. However, I now need to find more time …) Thanks again & best wishes Volker Volker Blum Associate Professor, Duke MEMS & Chemistry https://aims.pratt.duke.edu https://bsky.app/profile/aimsduke.bsky.social > On Oct 28, 2023, at 1:32 PM, Matt Thompson wrote: > > On my Mac I build Open MPI 5 with (among other flags): > > --with-hwloc=internal --with-libevent=internal --with-pmix=internal > > In my case, I should have had libevent through brew, but it didn't seem to > see it. But then I figured I might as well let Open MPI build its own for > convenience. > > Matt > > On Fri, Oct 27, 2023 at 7:51 PM Volker Blum via users > wrote: > OpenMPI 5.0.0 & Intel OneAPI 2023.2.0 on MacOS 14.0: > > In an ostensibly clean system, the following configure on MacOS ends without > a viable pmix build: > > configure: WARNING: Either libevent or libev support is required, but neither > configure: WARNING: was found. Please use the configure options to point us > configure: WARNING: to where we can find one or the other library > configure: error: Cannot continue > configure: = done with 3rd-party/openpmix configure = > checking for pmix pkg-config name... pmix > checking if pmix pkg-config module exists... yes > checking for pmix pkg-config cflags... > -I/usr/local/Cellar/open-mpi/4.1.5/include > checking for pmix pkg-config ldflags... -L/usr/local/Cellar/open-mpi/4.1.5/lib > checking for pmix pkg-config static ldflags... > -L/usr/local/Cellar/open-mpi/4.1.5/lib > checking for pmix pkg-config libs... -lpmix -lz > checking for pmix pkg-config static libs... -lpmix -lz > checking for pmix.h... no > configure: error: Could not find viable pmix build. > > configure command used was: > > lt_cv_ld_force_load=no ./configure --prefix=/usr/local/openmpi/5.0.0 FC=ifort > F77=ifort CC=icc CXX=icpc > > *** > > The same command works (up to the end of the configure stage) with OpenMPI > 4.1.6. > > My guess is that this is related to some earlier pmix related issues that can > be found by google but wanted to report. > > Thank you! > Best wishes > Volker > > > Volker Blum > Associate Professor, Duke MEMS & Chemistry > https://aims.pratt.duke.edu > https://bsky.app/profile/aimsduke.bsky.social > > > > > > -- > Matt Thompson >“The fact is, this is about us identifying what we do best and >finding more ways of doing less of it better” -- Director of Better Anna > Rampton
Re: [OMPI users] OpenMPI 5.0.0 & Intel OneAPI 2023.2.0 on MacOS 14.0:
Thank you very much, Matt! That sounds like it. Will try when I next get to work on this. (and I would really like to make 5.0.0 work …) (I lost a few extra hours afterwards, with the OneAPI based OpenMPI 4.1.6 mpic++ not being able to find various C++ headers - and I think this is due to Apple XCode. mpif90 and mpicc work and the situation for mpic++ did improve with XCode 5.1 beta 2, which is why I am suspecting this is an XCode related problem. However, I now need to find more time …) Thanks again & best wishes Volker Volker Blum Associate Professor, Duke MEMS & Chemistry https://aims.pratt.duke.edu https://bsky.app/profile/aimsduke.bsky.social > On Oct 28, 2023, at 1:32 PM, Matt Thompson wrote: > > On my Mac I build Open MPI 5 with (among other flags): > > --with-hwloc=internal --with-libevent=internal --with-pmix=internal > > In my case, I should have had libevent through brew, but it didn't seem to > see it. But then I figured I might as well let Open MPI build its own for > convenience. > > Matt > > On Fri, Oct 27, 2023 at 7:51 PM Volker Blum via users > wrote: > OpenMPI 5.0.0 & Intel OneAPI 2023.2.0 on MacOS 14.0: > > In an ostensibly clean system, the following configure on MacOS ends without > a viable pmix build: > > configure: WARNING: Either libevent or libev support is required, but neither > configure: WARNING: was found. Please use the configure options to point us > configure: WARNING: to where we can find one or the other library > configure: error: Cannot continue > configure: = done with 3rd-party/openpmix configure = > checking for pmix pkg-config name... pmix > checking if pmix pkg-config module exists... yes > checking for pmix pkg-config cflags... > -I/usr/local/Cellar/open-mpi/4.1.5/include > checking for pmix pkg-config ldflags... -L/usr/local/Cellar/open-mpi/4.1.5/lib > checking for pmix pkg-config static ldflags... > -L/usr/local/Cellar/open-mpi/4.1.5/lib > checking for pmix pkg-config libs... -lpmix -lz > checking for pmix pkg-config static libs... -lpmix -lz > checking for pmix.h... no > configure: error: Could not find viable pmix build. > > configure command used was: > > lt_cv_ld_force_load=no ./configure --prefix=/usr/local/openmpi/5.0.0 FC=ifort > F77=ifort CC=icc CXX=icpc > > *** > > The same command works (up to the end of the configure stage) with OpenMPI > 4.1.6. > > My guess is that this is related to some earlier pmix related issues that can > be found by google but wanted to report. > > Thank you! > Best wishes > Volker > > > Volker Blum > Associate Professor, Duke MEMS & Chemistry > https://aims.pratt.duke.edu > https://bsky.app/profile/aimsduke.bsky.social > > > > > > -- > Matt Thompson >“The fact is, this is about us identifying what we do best and >finding more ways of doing less of it better” -- Director of Better Anna > Rampton
Re: [OMPI users] OpenMPI 5.0.0 & Intel OneAPI 2023.2.0 on MacOS 14.0:
On my Mac I build Open MPI 5 with (among other flags): --with-hwloc=internal --with-libevent=internal --with-pmix=internal In my case, I should have had libevent through brew, but it didn't seem to see it. But then I figured I might as well let Open MPI build its own for convenience. Matt On Fri, Oct 27, 2023 at 7:51 PM Volker Blum via users < users@lists.open-mpi.org> wrote: > OpenMPI 5.0.0 & Intel OneAPI 2023.2.0 on MacOS 14.0: > > In an ostensibly clean system, the following configure on MacOS ends > without a viable pmix build: > > configure: WARNING: Either libevent or libev support is required, but > neither > configure: WARNING: was found. Please use the configure options to point us > configure: WARNING: to where we can find one or the other library > configure: error: Cannot continue > configure: = done with 3rd-party/openpmix configure = > checking for pmix pkg-config name... pmix > checking if pmix pkg-config module exists... yes > checking for pmix pkg-config cflags... > -I/usr/local/Cellar/open-mpi/4.1.5/include > checking for pmix pkg-config ldflags... > -L/usr/local/Cellar/open-mpi/4.1.5/lib > checking for pmix pkg-config static ldflags... > -L/usr/local/Cellar/open-mpi/4.1.5/lib > checking for pmix pkg-config libs... -lpmix -lz > checking for pmix pkg-config static libs... -lpmix -lz > checking for pmix.h... no > configure: error: Could not find viable pmix build. > > configure command used was: > > lt_cv_ld_force_load=no ./configure --prefix=/usr/local/openmpi/5.0.0 > FC=ifort F77=ifort CC=icc CXX=icpc > > *** > > The same command works (up to the end of the configure stage) with OpenMPI > 4.1.6. > > My guess is that this is related to some earlier pmix related issues that > can be found by google but wanted to report. > > Thank you! > Best wishes > Volker > > > Volker Blum > Associate Professor, Duke MEMS & Chemistry > https://aims.pratt.duke.edu > https://bsky.app/profile/aimsduke.bsky.social > > > > -- Matt Thompson “The fact is, this is about us identifying what we do best and finding more ways of doing less of it better” -- Director of Better Anna Rampton
