On 23/07/2017 05:09, Belcourt, Kenneth wrote:
On Jul 22, 2017, at 5:12 PM, Alain Miniussi <[email protected]
<mailto:[email protected]>> wrote:
On 23/07/2017 00:41, Alain Miniussi via Boost-mpi wrote:
On 22/07/2017 22:11, Belcourt, Kenneth wrote: I see that your recent
changes have now broken develop for clang-linux-3.8.1, and
gcc-4.7.2. So I guess Boost is dropping support for gcc-4.7.x, or
was that unintentional on your part Alain? Can you look at that and
see if we can either revert the broken develop change, or fix it so
it’s still buildable with gcc-4.7?
Unintentional, and weird, the change were already on develop, was
just a resync to make them unconflictig with master.
Work fine with 4.4.7 and intel mpi 5.0.3.
Can you point me to the error messages ?
They were all green, but perhaps I’m not patient enough and tests need
to cycle again. Look at the Sandia-gcc-4.7.2, Sandia-gcc-4.7.2-c++11,
and Sandia-clang-3.8, all available from this link.
http://www.boost.org/development/tests/develop/developer/mpi.html
Thanks for looking into this Alain.
There is an issue specific to the 2 cartesian test which is probably
https://github.com/boostorg/mpi/pull/47 waiting for merge (I'll check
and merge if relevant). These are the ones failing with clang3.8 and
warning with g++5.4.0/no c++11. I'll check with 4.4.7/no11.
As for the 4..7.2 tests, they all (well, picked a few randomly) indicate
that the compilation succeeds. The test is marked failed but there is no
output, could that be a config problem, a link issue maybe ?
s there a way to get the full ouput for, say,
http://www.boost.org/development/tests/develop/developer/output/Sandia-gcc-4-7-2-c++11-boost-bin-v2-libs-mpi-test-all_reduce_test-11-test-gcc-4-7-2-debug-threading-multi.html
?
Thanks
Alain
Noel
_______________________________________________
Boost-mpi mailing list
[email protected]
https://lists.boost.org/mailman/listinfo.cgi/boost-mpi