22 Jan
2014
22 Jan
'14
4:43 p.m.
Does anyone happen to have an instance of this for a test that fails on Windows? That would let me test locally. Otherwise, I would need the bjam log from the test runner, since the usual source of this kind of error is a bug the log scrapper program and that is impractical to debug without the log itself.
The library build is failing, and the tool is picking a random source file to display. Unfortunately, it isn't the one that failed.
OK, some hunting around shows it's an issue with Boost.Thread not building on that platform: http://www.boost.org/development/tests/develop/developer/thread.html John.