Re: [boost] [EXTERNAL] boost no longer builds mpi libraries when using intel mpi

20 Jul 2017

      On 20/07/2017 22:58, Alain Miniussi wrote:
...
On 20/07/2017 19:55, Belcourt, Kenneth via Boost wrote:
...
...
...
On Jul 19, 2017, at 4:00 PM, Edward Diener via Boost 
mailto:boost@lists.boost.org> wrote:
On 7/19/2017 5:40 PM, Alain Miniussi via Boost wrote:
On 19/07/2017 22:57, Edward Diener via Boost wrote:
On 7/19/2017 3:04 PM, Alain Miniussi via Boost wrote:
On 19/07/2017 16:26, Franck Houssen via Boost wrote:
There is a specific piece of doc for that in:
http://www.boost.org/doc/libs/1_64_0/doc/html/mpi/getting_started.html#mpi.c...
The 'using mpi' is a Boost Build rule which sets up a Boost Build 
toolset for use, as explained at 
http://www.boost.org/build/doc/html/bbv2/reference/tools.html.
Yes, what I don't know is where/how that rule is implemented. Nor 
how to implement one like mpi.
Look at build/src/tools/mpi.jam. The 'init' rule corresponds to the 
'using mpi ... ;' line(s).
I think I’ve sent this before, but here’s the user-config.jam I use 
to build and run Boost.MPI tests with Intel 17 and Intel MPI 5.1.
using mpi
   : /projects/linux_rh6/SDK/mpi/intel/5.1/bin64/mpicxx
   ;
using intel
   ;
cd libs/mpi/test
../../../b2 -d+2 toolset=intel
Does this work for you?
Sure.
Good.  Note that the above user-config.jam doesn’t require you to set
On Jul 20, 2017, at 2:34 AM, Alain Miniussi  
wrote:
On 20/07/2017 03:53, Belcourt, Kenneth via Boost wrote:
the include, lib paths or libraries.  So I’m not sure why you say this:
...
As a result, with most currently deployed Intel's MPI, you need to 
explicitly set the include and lib path and libraries.
Can you provide me an example of an Intel MPI that requires you to 
explicitly set the include, lib path and libraries?   Intel MPI 
doesn’t require you to do this any more than any other MPI 
implementation does.
On linux, IMPI 5.0.1.035 and a few versions before that one (I do not 
have access to them anymore). I hadn't tried to move back to the 
simple solution since then since the ugly one still worked, but it 
seems to be working again with 5.0.3.
It uses the same options for compilation and link (since 
--compile_info and -link_info boths falls back on "echo") but it works.
FWIW, I guess the problem was that, from ???? to 5.0.1:
[alainm@gurney ~]$ mpiicc -show:compile
icc: command line warning #10006: ignoring unknown option '-show:compile'
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/crt1.o: In 
function `_start':
(.text+0x20): undefined reference to `main'
[alainm@gurney ~]$ echo $?
0
[alainm@gurney ~]$

While, starting 5.0.3 (at least):
[alainm@tagir ~]$ mpiicc  -show:compile
icc: command line warning #10006: ignoring unknown option '-show:compile'
/usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../lib64/crt1.o: dans la 
fonction « _start »:
(.text+0x20): référence indéfinie vers « main »
[alainm@tagir ~]$ echo $?
1
[alainm@tagir ~]$

Still:
[alainm@tagir ~]$ mpiicc  -compile_info
icc 
-I/softs/softs-centos7/intel2017/compilers_and_libraries_2017.2.174/linux/mpi/intel64/include 
-L/softs/softs-centos7/intel2017/compilers_and_libraries_2017.2.174/linux/mpi/intel64/lib/release_mt 
-L/softs/softs-centos7/intel2017/compilers_and_libraries_2017.2.174/linux/mpi/intel64/lib 
-Xlinker --enable-new-dtags -Xlinker -rpath -Xlinker 
/softs/softs-centos7/intel2017/compilers_and_libraries_2017.2.174/linux/mpi/intel64/lib/release_mt 
-Xlinker -rpath -Xlinker 
/softs/softs-centos7/intel2017/compilers_and_libraries_2017.2.174/linux/mpi/intel64/lib 
-Xlinker -rpath -Xlinker 
/opt/intel/mpi-rt/2017.0.0/intel64/lib/release_mt -Xlinker -rpath 
-Xlinker /opt/intel/mpi-rt/2017.0.0/intel64/lib -lmpifort -lmpi -lmpigi 
-ldl -lrt -lpthread
[alainm@tagir ~]$ mpiicc  -link_info
icc 
-I/softs/softs-centos7/intel2017/compilers_and_libraries_2017.2.174/linux/mpi/intel64/include 
-L/softs/softs-centos7/intel2017/compilers_and_libraries_2017.2.174/linux/mpi/intel64/lib/release_mt 
-L/softs/softs-centos7/intel2017/compilers_and_libraries_2017.2.174/linux/mpi/intel64/lib 
-Xlinker --enable-new-dtags -Xlinker -rpath -Xlinker 
/softs/softs-centos7/intel2017/compilers_and_libraries_2017.2.174/linux/mpi/intel64/lib/release_mt 
-Xlinker -rpath -Xlinker 
/softs/softs-centos7/intel2017/compilers_and_libraries_2017.2.174/linux/mpi/intel64/lib 
-Xlinker -rpath -Xlinker 
/opt/intel/mpi-rt/2017.0.0/intel64/lib/release_mt -Xlinker -rpath 
-Xlinker /opt/intel/mpi-rt/2017.0.0/intel64/lib -lmpifort -lmpi -lmpigi 
-ldl -lrt -lpthread
[alainm@tagir ~]$

But it works, so...
...
Maybe we should change the doc then.
Alain
...
...
And of course, some MPI implementations do not have wrappers.
Right.  Cray, for example, does not provide a separate wrapper 
script, and it works just fine with Boost.MPI and Boost.Build.
Noel
_______________________________________________
Unsubscribe & other changes: 
http://lists.boost.org/mailman/listinfo.cgi/boost