Re: [boost] Boost.Threads, the Boost.Build system and GCC

From: David Abrahams (abrahams_at_[hidden])
Date: 2001-06-06 09:56:51

----- Original Message -----
From: <williamkempf_at_[hidden]>

> I've been trying to get the jamfiles included in the latest
> Boost.Threads upload to work with GCC (mingw32), the other compiler
> at my disposal.  Unfortunately, things don't work with
> <boost/stdint.h>.  This include results in the following compilation
> error:

First of all, it might be a good idea to make a new mingw-tools.jam file
based on gcc-tools.jam. I am not familiar with mingw, but gcc-tools.jam is
really designed to do Cygwin and linux builds. I'm not sure if the
requirements for mingw are sufficiently different.

> gcc-C++-action ..\src\bin\gcc\debug\runtime-link-dynamic\condition.obj
> In file included from ..\src\..\boost\thread\xtime.hpp:21,
>                  from ..\src\condition.cpp:19:
> c:\boost\boost\stdint.h:73: parse error
> c:\boost\boost\stdint.h:81: #error defaults not correct; you must
> hand modify bo
> ost/stdint.h
>
> Looking through the archives here there's a mention that -ansi -
> pedantic options should correct this.  So the first question is how
> do you add flags such as this to the commands in the Jamfiles?  I
> modified gcc-tools.jam changing actions gcc-C++-action, which works
> but is obviously not the "correct" way to do something like this.

It's not completely obvious to me. Don't we want to compile all boost code
with -ansi -pedantic?

If not, it sounds like a new simple feature definition is in order (see
features.jam). I think you'd want to put a default value for it in all of
the variant definitions so that subvariant directories were not created when
the feature has its default value.

> In any event, even after this change I still receive the same error
> message so I'm at a loss on how to get <boost/stdint.h> to work with
> gcc.

Not my department. Jens?