Re: [Boost-users] "Compiler threading support not turned on" error

From: Glen Simmons (gsimmons_at_[hidden])
Date: 2004-09-27 12:00:16

On 25 Sep, 2004, at 7:29 AM, John Maddock wrote:

>
>> In re-reading my post, I realize that it may sound like I'm getting
>> this error when trying to build Boost. Not the case, Boost seems to 
>> build ok and I get the 2 thread dylibs. It's when trying to use the 
>> thread library in my code that I get the above. Am I wrong in 
>> assuming that, since I ended up with the 2 thread dylibs, the problem 
>> is not in the Boost build process?
>
> Correct, as I said you need to figure out why BOOST_HAS_THREADS is not 
> getting defined: as far as I can see gcc.hpp should set it 
> unconditionally for your platform, and as far as I can see the build 
> system doesn't do anything special to the gcc command line either, so 
> I'm mystified frankly,

OK, it turns out that BOOST_HAS_THREADS *was* getting enabled, but was 
later getting disabled in suffix.hpp because BOOST_HAS_PTHREADS was not 
enabled. I believe that it should be enabled by the inclusion of 
posix_features.hpp, but this is not happening because of this test in 
macos.hpp:
#  ifndef TARGET_CARBON
#     include <boost/config/posix_features.hpp>
#  endif
I'm building a Cocoa project in Xcode, which apparently defines 
TARGET_CARBON for me. Why is posix_features.hpp only included if 
TARGET_CARBON is not defined? You can use posix from a carbon target 
just fine. Commenting out the #ifndef so posix_features.hpp is included 
makes it build and work just fine. Is there some reason for this that 
I'm not seeing? Is this a bug?

Glen