Subject: Re: [boost] [EXTERNAL] boost no longer builds mpi libraries when using intel mpi
From: Alain Miniussi (Alain.Miniussi_at_[hidden])
Date: 2017-07-20 20:58:25
On 20/07/2017 19:55, Belcourt, Kenneth via Boost wrote:
>> On Jul 20, 2017, at 2:34 AM, Alain Miniussi <alain.miniussi_at_oca.eu> wrote:
>> On 20/07/2017 03:53, Belcourt, Kenneth via Boost wrote:
>>> On Jul 19, 2017, at 4:00 PM, Edward Diener via Boost <boost_at_[hidden]<mailto:boost_at_[hidden]>> 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:
>>> 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?
> Good. Note that the above user-config.jam doesnât require you to set 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.
Maybe we should change the doc then.
>> 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.
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost