On 25/11/2007, Lukas Oboril <oboril.lukas at gmail.com> wrote: > On Nov 25, 2007 6:33 PM, Stefan Teleman <stefan.teleman at gmail.com> wrote: > > On Nov 25, 2007 9:43 AM, Lukas Oboril <oboril.lukas at gmail.com> wrote: > > > Hi, > > > > > > this is quite interesting ... when was my build machine under heavy > > > load, this message has discovered in build log ... and build failed > > > (boost64). > > > > > > When the load was in normal, then i tried once again build boost64 and > > > then was OK. > > > > This means you ran out of memory. > > > > When compiling with aggressive/high levels of optimization, ube and iropt > > can reserve *very large* amounts of memory. > > > > As an experiment, you can try rebuilding the same object files while running > > top in a separate window, and monitor the memory usage of iropt and ube. > > > yes I did it. It was interesting
I personally have 2GiB of mem in my system, plus 4GiB of swap space for this reason. -- Shawn Walker, Software and Systems Analyst http://binarycrusader.blogspot.com/ "We don't have enough parallel universes to allow all uses of all junction types--in the absence of quantum computing the combinatorics are not in our favor..." --Larry Wall
