[gentoo-user] gcc ebuild is hogging CPU?

[gentoo-user] gcc ebuild is hogging CPU?

[walt]

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.

[gentoo-user] Re: gcc ebuild is hogging CPU?

[walt]

On 06/26/2011 12:56 PM, walt wrote:
> 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.

Well, so far I've tracked the problem down to enabling the graphite
useflag while emerging >=gcc-4.4.x.  Disabling the graphite useflag
returns the cpu usage to normal while emerging gcc.

Could I ask some kind geek to try enabling the graphite useflag and
then to begin emerging gcc, please?  You don't need to sit through
the whole emerge -- five minute is more than enough to confirm this
bug if you see it too.

Just run top while emerging gcc and see who uses most cpu (after the
sources are bunzipped and the configure scripts have started running.)

Many thanks.