Latest Boost.Threads regression results on meta-como-win32-4.3.3-vc7
The Boost.Threads regression results for meta-como-win32-4.3.3-vc7 at http://boost.sourceforge.net/regression-logs/developer/thread.html all fail because: <quote> "C:\Users\Administrator\boost\main\boost\boost/config/requires_threads.hpp", line 29: catastrophic error #35: #error directive: "Threading support unavaliable: it has been explicitly disabled with BOOST_DISABLE_THREADS" # error "Threading support unavaliable: it has been explicitly disabled with BOOST_DISABLE_THREADS" </quote> The reason BOOST_DISABLE_THREADS is defined is because -DBOOST_DISABLE_WIN32 being passed on the command line. Does anyone know whether this option is on the command line on purpose, or should I consider it a configuration error for that toolset? Mike
Michael Glassford wrote:
The Boost.Threads regression results for meta-como-win32-4.3.3-vc7 at http://boost.sourceforge.net/regression-logs/developer/thread.html all fail because:
[snip]
The reason BOOST_DISABLE_THREADS is defined is because -DBOOST_DISABLE_WIN32 being passed on the command line. Does anyone know whether this option is on the command line on purpose, or should I consider it a configuration error for that toolset?
That option is not in the toolsets in CVS. But given where it's placed in the command invocation it must be coming from within a toolset file. Which leaves the only possibility that Metacomm's toolset adds that option. But at the same time the Metacomm docs on this don't show it: http://www.boost.org/regression-logs/cs-win32_metacomm/patches.html Non boost files and patched used in regression tests So the docs must be outdated? Aleksey, what's going on?? -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq
Rene Rivera writes:
Michael Glassford wrote:
The Boost.Threads regression results for meta-como-win32-4.3.3-vc7 at http://boost.sourceforge.net/regression-logs/developer/thread.html all fail because:
[snip]
The reason BOOST_DISABLE_THREADS is defined is because -DBOOST_DISABLE_WIN32 being passed on the command line. Does anyone know whether this option is on the command line on purpose, or should I consider it a configuration error for that toolset?
Probably it was motivated by this thread -- http://thread.gmane.org/gmane.comp.lib.boost.devel/85599.
That option is not in the toolsets in CVS. But given where it's placed in the command invocation it must be coming from within a toolset file. Which leaves the only possibility that Metacomm's toolset adds that option.
It does.
But at the same time the Metacomm docs on this don't show it:
http://www.boost.org/regression-logs/cs-win32_metacomm/patches.html Non boost files and patched used in regression tests
So the docs must be outdated?
Nope, they are auto-generated, and the option is there (see "tools\build\v1\meta-como-win32-4.3.3-vc7-tools.jam" subsection).
Aleksey, what's going on??
I hope the above clarifies things a little. -- Aleksey Gurtovoy MetaCommunications Engineering
participants (3)
-
Aleksey Gurtovoy -
Michael Glassford -
Rene Rivera