On 03/16/2015 03:19 PM, John Maddock wrote:
http://lists.boost.org/Archives/boost/2015/03/220552.php
looks as though a fix is still needed?
Since I did not get a response, I went ahead removing all <asynch-exceptions>on from Boost.Test Jamfile, and pushed to devel branch. Could you give it a try?
Should further changes be needed, they can be done at later time - subject to keeping top-level build with no options working.
I'm not at all sure this is the right fix: I believe Boost.Test really does need asynch-exception support turned on to work it's magic.
In that thread, Gennadiy say it does not need that from Boost.System, that it only needs client to set that. It's not quite clear whether Boost.Test itself should be built with that or not. Anyway, my primary point, if you allow a bit of ranting, is that it's clearly Boost.Test that tries to use custom settings that cause issues, but the people who appear to care most are Jürgen and Paul and you and I, neither of whom are Boost.Test maintainers. That's not really productive. So with this change, it's up to Boost.Test maintainers to do whatever is right, which might be updating documentation, or using just explicit /EHa cflags, or something else. -- Vladimir Prus CodeSourcery / Mentor Embedded http://vladimirprus.com