Hi, here is the output of those commands, modified to reflect the actual tool I told boost to use, which is mpiCC, not mpicxx.  What should I do with this output, and why does boost not accept it?  Thanks!  

rcook@rzgpu2 (~ ): /usr/local/tools/openmpi-intel-debug-1.8.4/bin/mpicxx --showme:compile 
-I/usr/local/tools/openmpi-intel-debug-1.8.4/include/openmpi/opal/mca/hwloc/hwloc191/hwloc/include -I/usr/local/tools/openmpi-intel-debug-1.8.4/include/openmpi/opal/mca/event/libevent2021/libevent -I/usr/local/tools/openmpi-intel-debug-1.8.4/include/openmpi/opal/mca/event/libevent2021/libevent/include -I/usr/local/tools/openmpi-intel-debug-1.8.4/include -I/usr/local/tools/openmpi-intel-debug-1.8.4/include/openmpi -pthread

rcook@rzgpu2 (~ ): /usr/local/tools/openmpi-intel-debug-1.8.4/bin/mpicxx --showme:link    
-pthread -Wl,-rpath -Wl,/usr/local/tools/openmpi-intel-debug-1.8.4/lib -Wl,--enable-new-dtags -L/usr/local/tools/openmpi-intel-debug-1.8.4/lib -lmpi


Subject: Re: [Boost-users] Cannot build boost with MPI using Intel openMPI wrapper
From: Alain Miniussi (alain.miniussi_at_[hidden])
Date: 2015-06-10 10:07:41


What is the result of: 
$/usr/local/tools/openmpi-intel-debug-1.8.4/bin/mpicxx --showme:compile 
$/usr/local/tools/openmpi-intel-debug-1.8.4/bin/mpicxx --showme:link 


On 10/06/2015 11:08, Boris Schäling wrote: 
> On Wed, 10 Jun 2015 02:37:26 +0200, Cook, Rich <cook47_at_[hidden]> wrote: 

>> Hello, I'm seeing this in my build output. I'm hoping someone can 
>> help me find out what the actual problem is. Thanks for any assistance. 
>> 
>> ===============MPI Auto-configuration=============== 
>> MPI auto-detection failed: unknown wrapper compiler 
>> /usr/local/tools/openmpi-intel-debug-1.8.4/bin/mpiCC 
>> Please report this error to the Boost mailing list: http://www.boost.org 
>> You will need to manually configure MPI support. 
>> MPI launcher: mpirun -np 
>> ==================================================== 
>> 
>> 
>> Here are the commands that generated it: 
>> 
>> + mkdir -p //usr/local/tools/boost-intel-1.57.0 
>> + mkdir -p //usr/local/bin 
>> + pushd boost_1_57_0 
>> /tmp/dpkg-mkdeb.1Tdcc4kqMi/src/boost_1_57_0 
>> /tmp/dpkg-mkdeb.1Tdcc4kqMi/src 
>> + ./bootstrap.sh --prefix=/usr/local/tools/boost-intel-1.57.0 
>> + echo 'using mpi : 
>> /usr/local/tools/openmpi-intel-debug-1.8.4/bin/mpiCC ;' >> 
>> tools/build/src/user-config.jam 
>> 
>> + ./b2 -j20 --debug-configuration install 

> It's a while ago that I was using Boost.MPI. But if auto-detection 
> fails, you could pass MPI-related options explicitly. There is this 
> remark in the MPI Jamfile: 

> # If your MPI implementation does not have a wrapper compiler, or the MPI 
> # auto-detection code does not work with your MPI's wrapper compiler, 
> # you can pass MPI-related options explicitly via the second parameter 
> to the 
> # mpi module: 
> # 
> # using mpi : : <find-shared-library>lammpio 
> <find-shared-library>lammpi++ 
> # <find-shared-library>mpi <find-shared-library>lam 
> # <find-shared-library>dl ; 

> HTH, 
> Boris 

>> [...] 

> _______________________________________________ 
> Boost-users mailing list 
> Boost-users_at_[hidden] 
http://lists.boost.org/mailman/listinfo.cgi/boost-users 



-- 
---
Alain

-- 
✐Richard Cook   
✇ Lawrence Livermore National Laboratory
Bldg-453 Rm-4024, Mail Stop L-557        
7000 East Avenue,  Livermore, CA, 94550, USA
☎ (office) (925) 423-9605    
☎ (fax) (925) 423-6961
---
Information Management & Graphics Grp., Services & Development Div., Integrated Computing & Communications Dept.
(opinions expressed herein are mine and not those of LLNL)