VT guys --
I just committed https://svn.open-mpi.org/trac/ompi/changeset/29280 so that the
OMPI trunk can build. Feel free to replace it with a different/better fix.
Sorry for the rush on this! This particular problem came in with some
inadequate testing of a different/new feature on the OMPI
I looked into this. There's two issues:
1. In vt_mpiwrap.c, there's this code:
-
#if defined(MPI_VERSION) && MPI_VERSION >= 3
# define CONST const
#else /* MPI_VERSION */
# define CONST
#endif /* MPI_VERSION */
-
Open MPI doesn't yet identify itself as MPI_VERSION>=3, so this test didn'
VT guys -
We just updated all the OMPI c bindings to have the MPI 3 const and []
declarations on the trunk.
Can you update VT to match?
Sent from my phone. No type good.
Begin forwarded message:
From: MPI Team mailto:mpit...@crest.iu.edu>>
List-Post: devel@lists.open-mpi.org
Date: September 2
I'll look on it asap. Thanks for the hint, George!
Matthias
On Monday 14 November 2011 23:39:08 George Bosilca wrote:
> This is supposed to be an intrinsic, automatically replaced by GCC during
> the compilation process. If I do the same configure as you (on the same
> machine) I have in my opal_
This is supposed to be an intrinsic, automatically replaced by GCC during the
compilation process. If I do the same configure as you (on the same machine) I
have in my opal_config.h:
/* Whether C compiler supports __builtin_expect */
#define OPAL_C_HAVE_BUILTIN_EXPECT 1
/* Whether C++ compiler s
Hi VT-folks
I'm building the devel trunk on a Mac, using a vanilla configure line:
./configure --prefix=foo. When I try to compile, I get this error:
undefined symbols for architecture x86_64:
"___builtin_expect", referenced from:
_main.omp_fn.0 in otfprofile-otfprofile.o
ld: symbol(s) n
