Re: [Boost-build] [boost] [1.35.0] Threads - build failure using gcc on Win XP

From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2008-04-14 17:53:13

Mat Marcus wrote:
> On Mon, Apr 14, 2008 at 1:53 PM, Anthony Williams
> <anthony_w.geo_at_[hidden]> wrote:
> 
>> Oops. That should be a check on target-os. I don't know jamfile syntax well
>> enough to fix that though --- I don't think <target-os> is available at that
>> point.
>>
>> Anyway, that's the "default API" selection: threadapi=pthread can override
>> that.
>>
>> So: can we try target-os=cygwin threadapi=pthread?
>>
>> Anthony
>> --
> 
> Thanks! That succeeds for now. Ok, so a followup question is, for my
> (local) boost patch file, what modifications should I make? My goal is
> to restore the state of affairs to that of 1.34.1: the user didn't
> need to make any explicit mention of the threadapi or target-os on the
> command line or in the user-config.jam. Or will I need patches to both
> the boost thread Jamfile.v2 and the boost build system to restore
> auto-detection?

I'm sure we want auto-detection... But to make your immediate life 
easier you can add this to your user-config.jam:

====
import toolset ;
toolset.add-requirements
   <toolset>gcc-4.2.0:<target-os>cygwin
   <toolset>gcc-4.2.0:<threadapi>pthread ;
====

HTH

-- 
-- Grafik - Don't Assume Anything
-- Redshift Software, Inc. - http://redshift-software.com
-- rrivera/acm.org (msn) - grafik/redshift-software.com
-- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail