Oracle uses an abysmally complicated configure line, but nearly all of it is irrelevant to the problem here. For this, I would suggest just doing a vanilla ./configure - if the component gets pulled into libmpi, then we know there is a problem.


Just FYI: here is there actual configure line, just in case you spot something problematic:

CC=cc CXX=CC F77=f77 FC=f90  --with-openib  --enable-openib-connectx-xrc  --without-udapl 
--disable-openib-ibcm  --enable-btl-openib-failover   --without-dtrace  --enable-heterogeneous
--enable-cxx-exceptions --enable-shared --enable-orterun-prefix-by-default --with-sge
--enable-mpi-f90 --with-mpi-f90-size=small  --disable-peruse --disable-state 
--disable-mpi-thread-multiple   --disable-debug  --disable-mem-debug  --disable-mem-profile 
CFLAGS="-xtarget=ultra3 -m32 -xarch=sparcvis2 -xprefetch -xprefetch_level=2 -xvector=lib -Qoption
cg -xregs=no%appl -xdepend=yes -xbuiltin=%all -xO5"  CXXFLAGS="-xtarget=ultra3 -m32
-xarch=sparcvis2 -xprefetch -xprefetch_level=2 -xvector=lib -Qoption cg -xregs=no%appl -xdepend=yes
-xbuiltin=%all -xO5 -Bstatic -lCrun -lCstd -Bdynamic"  FFLAGS="-xtarget=ultra3 -m32 -xarch=sparcvis2
-xprefetch -xprefetch_level=2 -xvector=lib -Qoption cg -xregs=no%appl -stackvar -xO5" 
FCFLAGS="-xtarget=ultra3 -m32 -xarch=sparcvis2 -xprefetch -xprefetch_level=2 -xvector=lib -Qoption
cg -xregs=no%appl -stackvar -xO5"  
--mandir=${prefix}/man  --bindir=${prefix}/bin  --libdir=${prefix}/lib 
--includedir=${prefix}/include   --with-tm=/ws/ompi-tools/orte/torque/current/shared-install32 
--enable-contrib-no-build=vt --with-package-string="Oracle Message Passing Toolkit "
--with-ident-string="@(#)RELEASE VERSION 1.9openmpi-1.5.4-r1.9a1r27092"

and the error he gets is:

make[2]: Entering directory
  CCLD     ompi_info
Undefined			first referenced
 symbol  			    in file
mca_coll_ml_memsync_intra           ../../../ompi/.libs/
ld: fatal: symbol referencing errors. No output written to .libs/ompi_info
make[2]: *** [ompi_info] Error 2
make[2]: Leaving directory
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory
make: *** [install-recursive] Error 1

On Aug 24, 2012, at 4:30 PM, Paul Hargrove <> wrote:

I have access to a few different Solaris machines and can offer to build the trunk if somebody tells me what configure flags are desired.


On Fri, Aug 24, 2012 at 8:54 AM, Ralph Castain <> wrote:
Eugene - can you confirm that this is only happening on the one Solaris system? In other words, is this a general issue or something specific to that one machine?

I'm wondering because if it is just the one machine, then it might be something strange about how it is setup - perhaps the version of Solaris, or it is configuring --enable-static, or...

Just trying to assess how general a problem this might be, and thus if this should be a blocker or not.

On Aug 24, 2012, at 8:00 AM, Eugene Loh <> wrote:

> On 08/24/12 09:54, Shamis, Pavel wrote:
>> Maybe there is a chance to get direct access to this system ?
> No.
> But I'm attaching compressed log files from configure/make.
> <tarball-of-log-files.tar.bz2>_______________________________________________
> devel mailing list

devel mailing list

Paul H. Hargrove                
Future Technologies Group
Computer and Data Sciences Department     Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900

devel mailing list