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