Re: [Boost-build] Compiling Boost.MPI and mpich2 under Suse Linux

Subject: Re: [Boost-build] Compiling Boost.MPI and mpich2 under Suse Linux
From: Belcourt, Kenneth (kbelco_at_[hidden])
Date: 2010-05-27 13:41:45

On May 27, 2010, at 11:16 AM, Michael1984 wrote:

>
> This was what I tried initially, however, the error message by boost
> made me try to use the -fPIC flag.
>
> Having tried the original way you suggested again, I find that the  
> error
> message for ./bjam install is exactly the same as before.

Well, we've avoided using MPICH2 and haven't had any problems with,  
for example, MPICH 1.2.7p1.

Here's the MPICH information from bjam --debug-configuration with the  
gcc-4.2.4 toolset in 64 bit mode.

===============MPI Auto-configuration===============

Found MPICH wrapper compiler: /sierra/Sntools/extras/mpi/mpich-1.2.7p1- 
gcc-4.2.4-64Bit/bin/mpicxx

MPI compilation flags: -DUSE_STDARG -DHAVE_STDLIB_H=1 - 
DHAVE_STRING_H=1 -DHAVE_UNISTD_H=1 -DHAVE_STDARG_H=1 -DUSE_STDARG=1 - 
DMALLOC_RET_VOID=1 -DHAVE_MPI_CPP -I/home/sntools/extras/mpi/ 
mpich-1.2.7p1-gcc-4.2.4-64Bit/include/mpi2c++ -c -I/home/sntools/ 
extras/mpi/mpich-1.2.7p1-gcc-4.2.4-64Bit/include

MPI link flags: -DUSE_STDARG -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 - 
DHAVE_UNISTD_H=1 -DHAVE_STDARG_H=1 -DUSE_STDARG=1 -DMALLOC_RET_VOID=1 - 
Wl,-rpath -Wl,/home/sntools/extras/compilers/gcc-4.2.4/lib64 -Wl,- 
rpath -Wl,/home/sntools/extras/compilers/gcc-4.2.4/lib -L/home/sntools/ 
extras/mpi/mpich-1.2.7p1-gcc-4.2.4-64Bit/lib -Wl,-rpath -Wl,/home/ 
sntools/extras/compilers/gcc-4.2.4/lib64 -Wl,-rpath -Wl,/home/sntools/ 
extras/compilers/gcc-4.2.4/lib -lpmpich++ -lmpich -lpthread -lrt

MPI build features:

<define>USE_STDARG <define>HAVE_STDLIB_H=1 <define>HAVE_STRING_H=1  
<define>HAVE_UNISTD_H=1 <define>HAVE_STDARG_H=1 <define>USE_STDARG=1  
<define>MALLOC_RET_VOID=1 <define>HAVE_MPI_CPP <include>/home/sntools/ 
extras/mpi/mpich-1.2.7p1-gcc-4.2.4-64Bit/include/mpi2c++ <include>/ 
home/sntools/extras/mpi/mpich-1.2.7p1-gcc-4.2.4-64Bit/include  
<cxxflags>-c <define>USE_STDARG <define>HAVE_STDLIB_H=1  
<define>HAVE_STRING_H=1 <define>HAVE_UNISTD_H=1  
<define>HAVE_STDARG_H=1 <define>USE_STDARG=1 <define>MALLOC_RET_VOID=1  
<library-path>/home/sntools/extras/mpi/mpich-1.2.7p1-gcc-4.2.4-64Bit/ 
lib <find-shared-library>pmpich++ <find-shared-library>mpich  
<threading>multi <find-shared-library>rt <linkflags>-Wl,-rpath -Wl,/ 
home/sntools/extras/compilers/gcc-4.2.4/lib64 -Wl,-rpath -Wl,/home/ 
sntools/extras/compilers/gcc-4.2.4/lib -Wl,-rpath -Wl,/home/sntools/ 
extras/compilers/gcc-4.2.4/lib64 -Wl,-rpath -Wl,/home/sntools/extras/ 
compilers/gcc-4.2.4/lib

MPI launcher: /sierra/Sntools/extras/mpi/mpich-1.2.7p1-gcc-4.2.4-64Bit/ 
bin/mpirun -all-local
====================================================

Here's how this mpich version was built

../mpich-1.2.7p1-src/configure --prefix=/home/sntools/extras/mpi/ 
mpich-1.2.7p1-gcc-4.2.4-64Bit --enable-sharedlib -opt=-O2

Here's the mpi toolset description in user-config.jam.

using mpi
   : /sierra/Sntools/extras/mpi/mpich-1.2.7p1-gcc-4.2.4-64Bit/bin/mpicxx
   :
   : /sierra/Sntools/extras/mpi/mpich-1.2.7p1-gcc-4.2.4-64Bit/bin/ 
mpirun -all-local
   ;

Notice that the Sandia-gcc-4.2.4 tester

http://www.boost.org/development/tests/trunk/developer/summary.html

uses exactly this configuration.

Sorry I can't be of more help.

-- Noel