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:
Hello,
Just to get your attention to this : https://github.com/easybuilders/easybuild-easyconfigs/issues/1065
It hasn't build with that syntax in years (edit, just saw it's from 2017), Intel's MPI does not support the -show* options family (and don't plan to).
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...
I have no clue where the "using mpi"... is it called a directive ?.. is implemented, and if I did, I don't know how to detect we're using Intel's Implementation with bjam, nor how to pass the retrieved options, nor to what.
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.
I remember greping mpi in the build system a few year ago, but could not find a way to touch it (it failed with no meaningful message).
Look at build/src/tools/mpi.jam. The 'init' rule corresponds to the 'using mpi ... ;' line(s).
Hi Alain,
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? Previously you’d mentioned IMPI not working with Boost.Build, can you remind me what that failure involved?
Noel
