From: Andreas Huber (ahd6974-spamgroupstrap_at_[hidden])
Date: 2005-01-19 11:15:58
John Maddock wrote:
>> Given ...
>> ... it seems that the GCC toolset should define BOOST_DISABLE_THREADS
>> for single-threaded builds on GCC >= 3.4.0?
> Except that would make single-thread builds binary incompatible with
> the default Boost behaviour with that compiler.
Hmmm, wasn't the same true for GCC < 3.4.0? AFAICS the only thing that
has changed is that there is no longer a safe way to detect whether the
user requested an MT or ST build on the compiler command line. Instead,
MT-ness is discovered through a define in std headers that the compiled
> For now I believe
> it's safer to make Boost "always thread safe" with gcc 3.4.
Even when the user explicitly requests ST with <threading>single on the
bjam command line? Sure, a user can compile a boost lib with
<threading>single and then use that lib from code compiled normally
(without bjam), which would presumably lead to a disaster. However,
(s)he could have done the same with GCC < 3.4.0, right?
What am I missing?
-- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk