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

From: Robert Ramey (ramey_at_[hidden])
Date: 2004-11-24 02:30:49

These are the only modules in the serialization library ( and probably all
of boost that use the spirit library.  It would be interesting to know if
the spirit library and associated tests build and run correctly.

Also, for now the issue is just the compilation of these modules in release
mode.  This is relatively easy to narrow down if you're so inclined.

Start out commenting out the whole module with

#if 0

...

#endif

It better compile.

Move the above statements progressivly compiing the module. Eventually
you'll find a small part of the program or perhaps some include module that
makes the compiler bomb.

I know, its tedious, time consuming, and crude - but effective.  I'll double
check that my windows version of gcc 3.3 can compile this module in release
mode.  If your lucky - it won't be able to.

Robert Ramey

"Mail Delivery Subsystem" <MAILER-DAEMON_at_[hidden]> wrote in message
news:BC839C6D-3D17-11D9-AC04-000A9588A24E_at_mac.com...
>
> 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 ?
>
> thanks
>
> Yarden