Dnia czwartek, 28 września 2006 09:24, Petter Haggholm napisał:
> Without having tried it yet -- I need to finish some work first -- I'm > curious about the MAKEOPTS thing, especially -j?. The other reply (so > far) in this thread suggests -j1 and asserts that "[-j2] has no sense > anyway, if you have no multicore or don't use distcc...". This is in > contrast to all the recommended settings I have seen so far -- standard > procedure seems to be -j$(no. cores+1), I presume so that one make > process can do some CPU work while the other is I/O bound? I suppose one > could keep the system more responsive at the cost of longer compiles by > running only one make process, but I have never heard of anyone else > having problems with -j2 on a single-core system ... Well, problem is not CPU but memory. Having -j2 + kdeenablefinal + gcc-4 eats ENORMOUS amounts of memory. This is the reason it kills some running applications (as in your case). Put some memory usage monitor and observe, especially the VM bar. In my system it goes up as if it had at least a foot of scale to collect, not mere half an inch... Remember that 'kdeenablefinal' works this way: it prepares application as one huge source file and then compiles it. Without kdeenablefinal each .cc file of app is compiled separately and then linked together, which significantly decreases memory usage - it is easier to compile 100 1MB files than 1 100MB file... -- Pawel Kraszewski www.kraszewscy.net -- [email protected] mailing list
