Re: [boost] Building boost.

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-02-28 19:01:01

BTW, most of the tests are not supposed to be run in release mode because
assert() gets turned off. Some even forcibly error if you compile them that
way, so that will make your error count higher.

----- Original Message -----
From: "Rene Rivera" <grafik666_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Thursday, February 28, 2002 6:45 PM
Subject: Re: [boost] Building boost.

> On 2002-02-28 at 02:01 PM, kevin.vanhorn_at_[hidden] (Kevin S. Van
Horn)
> wrote:
>
> >According to the compiler status tables, Boost passes all tests on gcc
> >gcc 3.0.3.  This has me a bit perplexed, as I just tried to build Boost
> >with gcc 3.0.4 (I know, not exactly the same, but close), and got quite a
> >large number of errors -- Jam reports that it failed to update 79 targets
> >and skipped 40 targets.  I used
> >
> >  jam -sBOOST_ROOT=. -sTOOLS=gcc -sBUILD="debug release"
> >
> >The only thing I can think of is that perhaps it was getting the wrong
> >compiler (gcc 3.0.4 is installed in /opt/bin), although 'which g++'
> >verifies that the correct compiler is the first one in the my search
path.
> >Does anyone have any suggestions as to what might be wrong?  How can I
> >make sure that Jam uses the compiler I want it to use?
>
> A bit more detail would be cool...
>
> Where are you getting errors?
>
> Is it possible the Python targets that aren't building?
>
> If it's the Python stuff, try setting PYTHON_ROOT to where you normally
have
> Python installed. I set mine by adding -sPYTHON_ROOT="/usr".
>
> By the way , I get 17 failures and 5 skipped targets, so even I have
problems
> :-) Although some of them are expected.
>
>
> -- grafik - Don't Assume Anything
> -- rrivera_at_[hidden] - grafik_at_[hidden]
> -- 102708583_at_icq - Grafik666_at_AIM - Grafik_at_[hidden]
>
> Info: http://www.boost.org  Send unsubscribe requests to:
<mailto:boost-unsubscribe_at_[hidden]>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>