Hello.

Recently emerge behavior became strange on my ~amd64 system. When a
package fails to compile, emerge does not terminate, but goes to 100% of
CPU usage. Is anybody seeing this too?

# emerge --version
Portage 2.1.10.47 (default/linux/amd64/10.0/desktop, gcc-4.6.2, glibc-2.14.1-r2, 3.2.6-gentoo x86_64)

Romildo

On 02/20/2012 01:37 AM, José Romildo Malaquias wrote:
> Hello.
>
> Recently emerge behavior became strange on my ~amd64 system. When a
> package fails to compile, emerge does not terminate, but goes to 100% of
> CPU usage. Is anybody seeing this too?
>
> # emerge --version
> Portage 2.1.10.47 (default/linux/amd64/10.0/desktop, gcc-4.6.2, glibc-2.14.1-r2, 3.2.6-gentoo x86_64)

No such problem on my ~amd64 (but I'm staying with gcc-4.5.3 for now).

Portage is a collection of python scripts, so you might want to run
python-updater just for insurance.

Which version of python is your portage using? (See the useflags on your
sys-apps/portage package.)

On Mon, Feb 20, 2012 at 11:58:02AM -0800, walt wrote:
> On 02/20/2012 01:37 AM, José Romildo Malaquias wrote:
> > Hello.
> >
> > Recently emerge behavior became strange on my ~amd64 system. When a
> > package fails to compile, emerge does not terminate, but goes to 100% of
> > CPU usage. Is anybody seeing this too?
> >
> > # emerge --version
> > Portage 2.1.10.47 (default/linux/amd64/10.0/desktop, gcc-4.6.2, glibc-2.14.1-r2, 3.2.6-gentoo x86_64)
>
> No such problem on my ~amd64 (but I'm staying with gcc-4.5.3 for now).
>
> Portage is a collection of python scripts, so you might want to run
> python-updater just for insurance.
>
> Which version of python is your portage using? (See the useflags on your
> sys-apps/portage package.)

The problem seems to be fixed with the newer release of portage.

See https://bugs.gentoo.org/show_bug.cgi?id=404995.

Romildo