Re: [Boost-users] Boost.MPI build problem: auto-configuration fails

Subject: Re: [Boost-users] Boost.MPI build problem: auto-configuration fails
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2010-10-22 07:01:39

Kondov, Ivan wrote:

> They exist and both are actually links to the same binary
> 'opal_wrapper':
> 
> user_at_host:~/boost/boost_1_43_0$ file
> /software/all/openmpi/1.4.2/bin/mpic++
> /software/all/openmpi/1.4.2/bin/mpic++: symbolic link to `opal_wrapper'
> 
> user_at_host:~/boost/boost_1_43_0$ file
> /software/all/openmpi/1.4.2/bin/mpiCC
> /software/all/openmpi/1.4.2/bin/mpiCC: symbolic link to `opal_wrapper'
> 
> user_at_host:~/boost/boost_1_43_0$ file
> /software/all/openmpi/1.4.2/bin/opal_wrapper
> /software/all/openmpi/1.4.2/bin/opal_wrapper: ELF 64-bit LSB executable,
> AMD x86-64, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked
> (uses shared libs), for GNU/Linux 2.6.4, not stripped
> 
> user_at_host:~/test/openmpi$ mpic++ -v
> Using built-in specs.
> Target: x86_64-linux-gnu
> Configured with: ../gcc-4.4.4/configure --enable-threads=posix
> --enable-shared --prefix=/software/all/gcc/4.4.4
> --enable-languages=c,c++,fortran,java --enable-checking=release
> --with-tune=generic --build=x86_64-linux-gnu --host=x86_64-linux-gnu
> --target=x86_64-linux-gnu
> --with-gmp=/software/all/gcc_infrastructure/gmp/4.3.2
> -with-mpfr=/software/all/gcc_infrastructure/mpfr/2.4.2
> --with-ppl=/software/all/gcc_infrastructure/ppl/0.10.2
> --with-cloog=/software/all/gcc_infrastructure/cloog-ppl/0.15.9
> Thread model: posix
> gcc version 4.4.4 (GCC)
> 
> I just tested and it can also produce executables so than it is the
> right binary. I suppose that the autoconfiguration in bjam expects
> something from openmpi but I have no idea what is expected. 

Could you please answer this question:

        Does

            /software/all/openmpi/1.4.2/bin/mpiCC -showme:compile

        work?

This is what is used for auto-configuration.

- Volodya