id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc
8458,-DBOOST_THREAD_DONT_USE_CHRONO in thread.obj.rsp but not explicitly set,lukeocamden@…,viboes,"Wondering if anyone can reproduce this on Windows. In my setup I don't specify BOOST_THREAD_DONT_USE_CHRONO anywhere but it appears in the generated rsp files which are used to build boost. Unless I'm doing something wrong this would contradict the documentation at http://www.boost.org/doc/libs/1_53_0/doc/html/thread/build.html which states:

""Boost.Thread uses by default Boost.Chrono for the time related functions and define BOOST_THREAD_USES_CHRONO if BOOST_THREAD_DONT_USE_CHRONO is not defined. The user should define BOOST_THREAD_DONT_USE_CHRONO for compilers that don't work well with Boost.Chrono.""

An unfortunate consequence is that boost::thread::try_join_until(const chrono::time_point<chrono::system_clock, chrono::nanoseconds>&) is marked with dllimport but is not actually exported by the boost thread dll. LNK2001 ensues!

I attach a patch which seems to fix the problem for me.",Bugs,closed,Boost 1.54.0,thread,Boost 1.53.0,Problem,fixed,,