| 1 |
On Mon, Feb 20, 2012 at 11:58:02AM -0800, walt wrote: |
| 2 |
> On 02/20/2012 01:37 AM, José Romildo Malaquias wrote: |
| 3 |
> > Hello. |
| 4 |
> > |
| 5 |
> > Recently emerge behavior became strange on my ~amd64 system. When a |
| 6 |
> > package fails to compile, emerge does not terminate, but goes to 100% of |
| 7 |
> > CPU usage. Is anybody seeing this too? |
| 8 |
> > |
| 9 |
> > # emerge --version |
| 10 |
> > 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) |
| 11 |
> |
| 12 |
> No such problem on my ~amd64 (but I'm staying with gcc-4.5.3 for now). |
| 13 |
> |
| 14 |
> Portage is a collection of python scripts, so you might want to run |
| 15 |
> python-updater just for insurance. |
| 16 |
> |
| 17 |
> Which version of python is your portage using? (See the useflags on your |
| 18 |
> sys-apps/portage package.) |
| 19 |
|
| 20 |
The problem seems to be fixed with the newer release of portage. |
| 21 |
|
| 22 |
See https://bugs.gentoo.org/show_bug.cgi?id=404995. |
| 23 |
|
| 24 |
Romildo |
Archives