On Fri, 8 Jun 2007, Jeff Squyres wrote:
> Would it be helpful if we provided some way to link in all the MPI
> language bindings?
>
> Examples off the top of my head (haven't thought any of these through):
>
> - mpicxx_all ...
> - setenv OMPI_WRAPPER_WANT_ALL_LANGUAGE_BINDINGS
>mpicxx ...
>
Would it be helpful if we provided some way to link in all the MPI
language bindings?
Examples off the top of my head (haven't thought any of these through):
- mpicxx_all ...
- setenv OMPI_WRAPPER_WANT_ALL_LANGUAGE_BINDINGS
mpicxx ...
- mpicxx -ompi:all_languages ...
On Jun 6, 2007, at 12:
Hi Jeff,
Thanks for willing to put more thought on it. Here is my simplified
story. I have an accelerator physics code, Omega3P that is to perform
complex eigenmode analysis. The algorithm for solving eigensystems
makes use of a 3rd-party sparse direct solver called MUMPS (http://
graal.e
On Jun 5, 2007, at 11:17 PM, Lie-Quan Lee wrote:
it is a quite of headache for each compiler/platform to deal with
mixed language
issues. I have to compile my application on IBM visual age compiler,
Pathscale, Cray X1E compiler,
intel/openmpi, intel/mpich, PGI compiler ...
And of course, openmp
On Jun 5, 2007, at 6:46 PM, Jeff Squyres wrote:
On Jun 5, 2007, at 4:51 PM, Lie-Quan Lee wrote:
Using the OPEN_MPI #define is probably the safest bet to identify the
MPI as Open MPI, which then opens the door to using mpi --
showme to find the proper linker flags. I would *NOT* recommend
h
On Jun 5, 2007, at 4:51 PM, Lie-Quan Lee wrote:
Using the OPEN_MPI #define is probably the safest bet to identify the
MPI as Open MPI, which then opens the door to using mpi --
showme to find the proper linker flags. I would *NOT* recommend hard-
coding specific flags just because you know that
Jeff is right-- if you've already confirmed ompi,
just use the ompi specific arguments to get the
MPI LDFLAGS out. I withdraw the comment about adding
a feature to ompi_info.
It is unfortunate, but true, that the mpi compiler wrappers
give no hint of the existence of -show, --showme:link, etc
befo
Using the OPEN_MPI #define is probably the safest bet to identify the
MPI as Open MPI, which then opens the door to using mpi --
showme to find the proper linker flags. I would *NOT* recommend hard-
coding specific flags just because you know that you're linking
against Open MPI (because we can/h
On Jun 5, 2007, at 4:22 PM, Ben Allan wrote:
What you really want, after configure has confirmed openmpi with the
macro check, is to extract the libraries listed in the output of
mpif90 -v test.f
that are needed.
Ideally someone could update ompi_config to output the link flags
for 3 cases:
C
What you really want, after configure has confirmed openmpi with the
macro check, is to extract the libraries listed in the output of
mpif90 -v test.f
that are needed.
Ideally someone could update ompi_config to output the link flags for 3 cases:
C++ linking without using mpicxx
F90 linking with
Hi Rich -
All the releases back to the 0.9 pre-release included a #define of
OPEN_MPI to 1 in mpi.h, so that would be a good way to find out if
you are using Open MPI or not.
Hope this helps,
Brian
On Jun 5, 2007, at 1:36 PM, Lie-Quan Lee wrote:
I was thinking of this way. Is macro OPEN
I was thinking of this way. Is macro OPEN_MPI always defined in the openmpi
release? I search through FAQ and other docs and cannot confirm it. Or there
is another macro which is unique to openmpi?
--Rich
On 6/5/07, Anthony Chan wrote:
Never tried this myself, but this test could work
AC_CO
this is neat but it will need to identify whether the MPI implementation is
openmpi. -- Not all the implementations accept --showme flag.
--Rich
On 6/5/07, Nuno Sucena Almeida wrote:
Hi,
there's an autoconf macro you can find at
http://autoconf-archive.cryp.to/acx_mpi.html
Never tried this myself, but this test could work
AC_COMPILE_IFELSE( [
AC_LANG_PROGRAM( [
#include "mpi.h"
], [
#if defined( OPEN_MPI )
return 0;
#else
#error
#endif
] )
], [
mpi_is_openmpi=yes
], [
mpi_is_openmpi=no
] )
A.Chan
On Tue, 5 Jun 2007, Lie-Quan Lee wrote:
Hi,
there's an autoconf macro you can find at
http://autoconf-archive.cryp.to/acx_mpi.html
it might be useful to you. I prefer to use it just to test the
existence of
MPI and then inside configure.ac something like (ugly):
(...)
MPI_CXXLIBS=`mpicxx --showme:link
15 matches
Mail list logo
