Hmmm... My intel box just started compiling the latest kdelibs when all
of a sudden everything slowed down. And I mean EVERYTHING. The compiler
had "taken" 92% of the memory in the box (I've moved the 512Mb from my
alpha to my intel, for testing, it didn't work nice in my alpha). Here's
the output:
make[3]: Entering directory
`/data/users/cooker/RPM/BUILD/kdelibs/arts/mcopidl'
g++ -DHAVE_CONFIG_H -I. -I. -I../.. -I../../dcop -I../../kdecore
-I../../kdeui -I../../kssl -I/usr/lib/qt2/include -I/usr/X11R6/include
-I/usr/include -I./../mcop -O3 -fomit-frame-pointer -pipe -s
-march=pentium -ffast-math -fexpensive-optimizations -DNDEBUG -frtti -c
mcopidl.cc
mcopidl.cc: In function `class string
createTypeCode(basic_string<char,string_char_traits<char>,__default_alloc_template<true,0>
>, const string &, long int,
>basic_string<char,string_char_traits<char>,__default_alloc_template<true,0> > = "")':
mcopidl.cc:688: virtual memory exhausted
Is this normal? What kind of box do you need to be able to compile this
stuff? A 2Gb quad Xeon "I normally simulate nucular blasts in office
hours, but in the evenings I compile kdelibs-1.94-14mdk" kind of box?
You _must_ be kidding!!! 512Mb + 256 swap (yeah yeah, 256Mb swap is too
small, but for a box that normally only has 128Mb it's fine) is clearly
not enough....
Stefan
