Ken Moffat wrote: > On Mon, Feb 04, 2013 at 04:46:01PM -0600, Bruce Dubbs wrote: >> >> I'm not sure about why you would have a problem with the memory. I did >> do a LFS build recently on a cloud server with only 512M of ram. gcc >> did run it oom, but adding a swap file cleared that up -- it just took >> longer. >> >> I don't understand why the number of processors would matter.
> It's a desktop - when compiling some c++ packages the desktop > becomes totally unresponsive for tens of seconds. This also > happened on my other single-processor x86_64 which had adequate > memory and faster cpu, faster disk. On my current multiprocessor > desktops I haven't seen the problem. Be nice. Pun intended. Actually, I thought that the scheduler would handle that properly by itself, but you may have selected something in the kernel to change the behavior. However, low memory does lead to swapping and I can see the problems there. Building gcc does use a large amount of memory. Testing gcc even more. Did you change the preemption model or other processor settings in the kernel? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
