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

From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2008-04-15 18:11:50

Hi Mat,

you are making alot of good points, one I favour most:
*) don't break anything.

However unfortunately the situation is far from ideal.

Didn't someone in this thread say the compiler should determine the
thread api? Do you know a reliable method? If so please
tell me. (I am not talking about macros here, we do not have
access to these.) Until then I use the approximation that
bjam gives me and rely on users tweaking their setup for
unusual setups. By unusual I mean: look at the boost regression
pages and try to find out how common your setup is.

What complicates things is, I am not the maintainer of gcc.jam.
gcc.jam already has a big load on it. It cannot omit any of the
gcc variants and also needs to deal with a stranger, i.e. mingw
compiler. Of course it is not a cross compiler, but perhaps it
is a good aproach to view it in this light.
It is hairy to change it without risk of break on some seemingly
unrelated platform.

I tried my best to to get at "make it just work". Ok I admit I
failed for your case. Others so far can use the setup, and so can I.

So what shall we do? Can you possibly supply not only a suggestion
of how it should work, but also how to implement it?

If so, please do.

Do you mean I should drop support of pthread for mingw and msvc builds?

If not please stick with Renes advice until a solution is found
that will also work for your environment without heavy user-config.jam
tweaking.

I admit it would be nice if everything goes auto-config like.
Still we are not there yet.

Btw. this is what I am doing most of the time. My user config
already contains lot of code to work around certain deficiencies,
I was not able yet to convince the maintainers to implement.

Also I did not complain, instead started to look into the problems
and tried to help solve some of them.

Btw. I just succeded building bjam both from 1.35.0 and trunk.
Possibly you can check if your self compiled gcc does not work
as you expect?

Regards Roland

-- 
_________________________________________
  _  _  | Roland Schwarz
 |_)(_  | aka. speedsnail
 | \__) | mailto:roland.schwarz_at_[hidden]
________| http://www.blackspace.at