Awesome, thanks!

On Tue, May 12, 2020 at 11:15 PM Gilles Gouaillardet <
gilles.gouaillar...@gmail.com> wrote:

> Hi,
>
> no you do not.
>
> FWIW, MPI C++ bindings were removed from the standard a decade ago.
> mpicc is the wrapper for the C compiler, and the wrappers for the C++
> compilers are mpicxx,mpiCC and mpicxx.
> If your C++ application is only using the MPI C bindings, then you do
> not need --enable-mpi-cxx for the C++ wrappers to work.
> But if your C++ application is using the MPI C++ bindings, you should
> consider modernizing it
> (plain C bindings, or other C++ abstractions such as Boost.MPI or
> Elementals for example)
>
> Cheers,
>
> Gilles
>
> On Wed, May 13, 2020 at 1:00 PM Konstantinos Konstantinidis via users
> <users@lists.open-mpi.org> wrote:
> >
> > Hi,
> > I have a naive question. I have built Open MPI 3.1.6 on my system after
> configuring as follows:
> > ./configure --prefix=/usr/local
> >
> > I am planning to use Python so I want to build MPI4py 3.0.3 which will
> be using the Open MPI implementation. The MPI4py requirements here state
> that
> > "If you use a MPI implementation providing a mpicc compiler wrapper
> (e.g., MPICH, Open MPI), it will be used for compilation and linking. This
> is the preferred and easiest way of building MPI for Python."
> >
> > So I am wondering whether I need the C++ bindings (if still supported in
> Open MPI), i.e., does mpicc needs Open MPI to be configured with
> "--enable-mpi-cxx" for MPI4py to work?
> >
> > I won't be coding in C++ at all.
> >
> > Thanks,
> > Konstantinos Konstantinidis
> >
> >
>

Reply via email to