Anyone emerged gcc lately?  I've been doing it all day (it seems)
so I finally used top to see if something besides gcc is using cpu.

Sure enough, emerge is constantly using 50% cpu while the compiler
is using the other half.

I tried using ebuild directly instead of emerge and I find that now
ebuild is using 50% cpu instead of emerge.

I just tried emerging firefox and I see that the compiler is getting
all of the cpu now instead of half.

Can anyone reproduce this agonizing sloth?

Thanks.


Reply via email to