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_config.h: > > /* Whether C compiler supports __builtin_expect */ > #define OPAL_C_HAVE_BUILTIN_EXPECT 1 > /* Whether C++ compiler supports __builtin_expect */ > #define OMPI_CXX_HAVE_BUILTIN_EXPECT 0 > > This means that the C compiler supports __builtin_expect while the C++ > compiler doesn't. I guess the VT-folks should fix their usage of the > BUILTIN_EXPECT macro … > > george. > > On Nov 14, 2011, at 12:22 , Ralph Castain wrote: > > 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) not found for architecture x86_64 > > collect2: ld returned 1 exit status > > > > > > I believe this comes from your VT code. Can you take a look? > > > > Thanks > > Ralph > > > > > > _______________________________________________ > > devel mailing list > > de...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/devel > > _______________________________________________ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel
