Boost.MPI build problem: auto-configuration fails
Hi, I would like to build boost.mpi from boost/1.43.0 with gcc/4.4.4, openmpi/1.4.2 on GNU/Linux 2.6.18-128.1.14.el5.8hp.2sp SMP x86_64 bjam always skips the MPI section (see below). Adding a line in user-config.jam "using mpi : /software/all/openmpi/1.4.2/bin/mpiCC ;" or "using mpi : /software/all/openmpi/1.4.2/bin/mpic++ ;" does not change the result: username@host:~/boost/boost_1_43_0$ bjam -v Boost.Jam Version 3.1.18. OS=LINUX. username@host:~/boost/boost_1_43_0$ bjam --with-mpi warning: No toolsets are configured. warning: Configuring default toolset "gcc". warning: If the default is wrong, your build may not work correctly. warning: Use the "toolset=xxxxx" option to override our guess. warning: For more configuration options, please consult warning: http://boost.org/boost-build2/doc/html/bbv2/advanced/configuration.html Building the Boost C++ Libraries. warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. Component configuration: - date_time : not building - filesystem : not building - graph : not building - graph_parallel : not building - iostreams : not building - math : not building - mpi : building - program_options : not building - python : not building - random : not building - regex : not building - serialization : not building - signals : not building - system : not building - test : not building - thread : not building - wave : not building ...found 1 target... The Boost C++ Libraries were successfully built! The following directory should be added to compiler include paths: ......................../username/boost/boost_1_43_0 The following directory should be added to linker library paths: ......................../username/boost/boost_1_43_0/stage/lib username@host:~/boost/boost_1_43_0$ which mpic++ /software/all/openmpi/1.4.2/bin/mpic++ username@host:~/boost/boost_1_43_0$ 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) Many thanks in advance for any help! Best regards, Ivan
Kondov, Ivan wrote:
Hi,
I would like to build boost.mpi from boost/1.43.0 with gcc/4.4.4, openmpi/1.4.2 on GNU/Linux 2.6.18-128.1.14.el5.8hp.2sp SMP x86_64
bjam always skips the MPI section (see below).
Adding a line in user-config.jam
"using mpi : /software/all/openmpi/1.4.2/bin/mpiCC ;" or
"using mpi : /software/all/openmpi/1.4.2/bin/mpic++ ;"
I'm confused -- what is the right binary? Do both exist? Does /software/all/openmpi/1.4.2/bin/mpiCC -showme:compile work? - Volodya
They exist and both are actually links to the same binary 'opal_wrapper': user@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@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@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@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. I tried the instructions in http://www.boost.org/doc/libs/1_43_0/doc/html/mpi/getting_started.html#m pi.config "--debug-configuration" says nothing more about MPI. I also want to try but unfortunately do not understand the hint for user-config.jam: using mpi : : <find-shared-library>lammpio <find-shared-library>lammpi++ <find-shared-library>mpi <find-shared-library>lam <find-shared-library>dl ; Best, Ivan
-----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users- bounces@lists.boost.org] On Behalf Of Vladimir Prus Sent: Friday, October 22, 2010 8:11 AM To: boost-users@lists.boost.org Subject: Re: [Boost-users] Boost.MPI build problem: auto-configuration fails
Kondov, Ivan wrote:
Hi,
I would like to build boost.mpi from boost/1.43.0 with gcc/4.4.4, openmpi/1.4.2 on GNU/Linux 2.6.18-128.1.14.el5.8hp.2sp SMP x86_64
bjam always skips the MPI section (see below).
Adding a line in user-config.jam
"using mpi : /software/all/openmpi/1.4.2/bin/mpiCC ;" or
"using mpi : /software/all/openmpi/1.4.2/bin/mpic++ ;"
I'm confused -- what is the right binary? Do both exist?
Does
/software/all/openmpi/1.4.2/bin/mpiCC -showme:compile
work?
- Volodya
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
Kondov, Ivan wrote:
They exist and both are actually links to the same binary 'opal_wrapper':
user@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@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@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@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
Sorry, now I understand. Yes, it works: user@host:~/test/intel-openmpi$ /software/all/openmpi/1.4.2/bin/mpiCC -showme:compile -I/software/all/openmpi/1.4.2/include -pthread Best, Ivan
-----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users- bounces@lists.boost.org] On Behalf Of Vladimir Prus Sent: Friday, October 22, 2010 1:02 PM To: boost-users@lists.boost.org Subject: Re: [Boost-users] Boost.MPI build problem: auto-configuration fails
Kondov, Ivan wrote:
They exist and both are actually links to the same binary 'opal_wrapper':
user@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@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@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@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
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
participants (2)
-
Kondov, Ivan -
Vladimir Prus