The problem I have is pretty simple, which is what grabbed my attention to this problem in the first place. I have projects where I specify the thread library in my Jamfile: <library>$(BOOST_ROOT)/libs/thread/build//boost_thread <threading>multi <link>static In 1.34.1, bjam picks up the dependency and builds just fine. This has worked for a few revs back without a hitch. I was able to upgade Boost without any problems. Now, in 1.35.0, the builds break. Removing build//boost_thread line certainly works in in 1.34.1 and 1.35.0, however, it is still irksome in that things changed, and in this case, were not documented. The <threadapi> and <thread-os> aren't mentioned and caused a little bit of some confusion trying to compile my projects. Anthony Williams wrote:
Roland Schwarz <roland.schwarz@chello.at> writes:
Roland Schwarz wrote:
Hmm, this is interesting. This would indicate a missing dependency in the wave Jamfile.
No, the dependency is there.
Does it help if you specify:
bjam --with-thread threading=multi ?
No. On my linux system,
bjam --with-wave --with-thread
compiles fine, but if you omit the --with-thread then you get an error. Even if you specify
bjam --with-wave threading=multi threadapi=pthread
it doesn't work. This time you get "unknown feature threadapi" though.
It does appear that it is not reading the thread Jamfile in the same way when it is implicitly picked up from --with-wave vs when it is explicitly requested with --with-thread.
Anthony