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 <sys/statfs.h>
*
Filed github issue https://github.com/open-mpi/ompi/issues/12052 to track
Thanks for reporting these issues!
________________________________
From: users <users-boun...@lists.open-mpi.org> on behalf of Matt Thompson via
users <users@lists.open-mpi.org>
Sent: Monday, November 6, 2023 1:38 PM
To: Open MPI Users <users@lists.open-mpi.org>
Cc: Matt Thompson <fort...@gmail.com>; Christophe Peyret
<christophe.pey...@onera.fr>
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
<users@lists.open-mpi.org<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
> <users@lists.open-mpi.org<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_000000.
>
> 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 <sys/statfs.h>
> ^
>
> 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
