Re: [Boost-testing] [bronf][mingw] pthreads not linked (was Re: [sandia][intel-linux] pthreads not linked)

Subject: Re: [Boost-testing] [bronf][mingw] pthreads not linked (was Re: [sandia][intel-linux] pthreads not linked)
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2008-12-15 03:41:06

frederic.bron_at_[hidden] wrote:

> 
> 
> boost-testing-bounces_at_[hidden] a écrit sur 13/12/2008 17:58:39 :
>> frederic.bron_at_[hidden] wrote:
>>
>> >
>> >
>> > I have just rerun the regression tests with the following user-config.jam:
>> >
>> > using gcc : mingw_3.4.4  : /usr/bin/g++ : <compilerflags>-mno-cygwin
>> > <compileflags>-DBOOST_WINDOWS_API <compileflags>-
>> DBOOST_HAS_WINTHREADS <linkflags>-mno-cygwin ;
>> >
>> > However, the result is not better because:
>> >
>> > nearly each time -DBOOST_HAS_WINTHREADS is used, -
>> DBOOST_THREAD_POSIX is used (257 times)!
>> > 82 times, -DBOOST_HAS_WINTHREADS is used alone.
>> >
>> > I am pretty sure it is because I run mingw from cygwin... any
>> workaround to say to bjam I am using
>> > a pure win32 application?
>>
>> I am not sure what you're trying to say. Are you using target-
>> os=windows when building mingw
>> tests?
> 
> No, did not know this option. Seems like what I am looking for. Is it an option of bjam that I
> should give to run.py as --bjam-options=? 

I think so. It is probably best to run tests for mingw only, specifying the mingw gcc as
toolset, and target-os=windows as bjam options.

> Can I remove the compileflags options from 
> user-config.jam if I use target-os=windows?

        -mno-cygwin

will have to stay. The defines probably should go.

- Volodya