On Jul 22, 2017, at 5:12 PM, Alain Miniussi <alain.miniu...@oca.eu<mailto:alain.miniu...@oca.eu>> 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. Noel
_______________________________________________ Boost-mpi mailing list Boost-mpi@lists.boost.org https://lists.boost.org/mailman/listinfo.cgi/boost-mpi
