"Bronek Kozicki" <brok@rubikon.pl> wrote in message news:4124F942.8030302@rubikon.pl...
Michael Glassford wrote:
Bronek Kozicki says he has tracked down the problem for me: adding "<threading>multi" to boost_thread_lib_base and boost_thread_dll_base in libs\boost\thread\build\jamfile fixes the problem. I haven't been
I think I wrote about libs\boost\thread\test\Jamfile , not about libs\boost\thread\bjam\Jamfile .
Sorry, my mistake.
One have to append <threading>multi in template boost_thread_test_lib, just below : ## default build ## (see attached patch). The same line can be appended to template boost_thread_test_dll, but I did not put it in patch (this time).
Actually, it was in the patch you sent me and I included it in my commit.
I do not know why it works, I do not even know how to write Bjam files, but it does work - all tests passed fine. The point is that it has to be added in this place - modyfing libs/thread/build/Jamfile or adding "<threading>multi" line somewhere above ": ## default build ##" does not fix the problem - bjam will still use single-threaded unit test framework, then two different versions of statically linked CRT (single-threaded from test unit framework and multi-threaded from test units) are linked to single executable and we have linker errors. Maybe source of problem is not in the threads library, but in its test unit or bjam (or both)?s
I've fixed it in the right place now, I hope.
B.
PS. I'm using "Boost.Jam Version 3.1.10. OS=NT."
Mike