[Boost-users] Re: compiling 1_32 in release mode brings the computerto its knees (Modified by Yarden Livnat)

From: Robert Ramey (ramey_at_[hidden])
Date: 2004-11-24 01:59:55

note the boost test page:

http://boost.sourceforge.net/regression-logs/cs-Darwin.html

shows build and tests all passing with gcc 3.3 build 1666.

I don't know if that helps.

Robert Ramey

"Thomas Costa" <oohrah_at_[hidden]> wrote in message
news:ECC0A694-3D82-11D9-84B9-00039303FB26_at_mac.com...
> Are these problems maybe fixed with Apple's updated gcc 3.3 build 1671
> that got posted to the Apple developer site recently?
>
> On Nov 23, 2004, at 10:19 AM, Chris Little wrote:
>
> > on 11/23/04 9:32 AM, Glen Simmons at gsimmons_at_[hidden] wrote:
> >
> >> On 23 Nov, 2004, at 12:17 AM, Mail Delivery Subsystem wrote:
> >>
> >>>
> >>> Hi,
> >>>
> >>> I'm trying to compile 1_32 on OSX with the latest gcc (GCC) 3.3
> >>> 20030304 (Apple Computer, Inc. build 1666)
> >>> however, while the debug version compile in just a few minutes, the
> >>> 'release' start trashing on :
> >>>    libs/serialization/src/xml_grammar.cpp
> >>>    libs/serialization/src/xml_wgrammar.cpp
> >>>
> >>> in effect the compilation takes all the memory and then pages
> >>> endlessly for hours, bringing the machine down to its knees.
> >>>
> >>> my compile command is:
> >>>
> >>> sudo bjam -sTOOLS=darwin "-sBUILD=release <threading>multi
> >>> <define>BOOST_SIGNALS_NAMESPACE=Signals " install
> >>>
> >>> where the <define> is for Qt,
> >>>
> >>>
> >>> Anybody has a clue why this is happaning and how to get the
> >>> compilation to complete (other then copy the two .o from the debug
> >>> tree into the release tree ?
> >>
> >> The same thing happened to me. Since I'm not using the serialization
> >> library, I used the --without-serialization option. Not an ideal
> >> solution, especially if you need the serialization lib, but a
> >> workaround if you don't.
> >>
> >> HTH,
> >> Glen Simmons
> >
> > On the main list Troy Straszheim post about this problem also.  Troy
> > found
> > that it is a compiler bug.  If you remove the -O flag from the build
> > options
> > then everything is fine.  Troy filed a bug with Apple.
> >
> > Chris
> >
> > _______________________________________________
> > Boost-users mailing list
> > Boost-users_at_[hidden]
> > http://lists.boost.org/mailman/listinfo.cgi/boost-users