From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: gcc ebuild is hogging CPU?
Date: Mon, 27 Jun 2011 16:14:47 -0700 [thread overview]
Message-ID: <iub2t5$rt4$1@dough.gmane.org> (raw)
In-Reply-To: <iu82tg$9h7$1@dough.gmane.org>
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.
prev parent reply other threads:[~2011-06-27 23:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 19:56 [gentoo-user] gcc ebuild is hogging CPU? walt
2011-06-27 23:14 ` walt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='iub2t5$rt4$1@dough.gmane.org' \
--to=w41ter@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox