| 1 |
Hi everyone, |
| 2 |
|
| 3 |
I have recently updated portage, did an emerge -avuD system and world. |
| 4 |
Everything was doing great until it hit kmail. First time i tried to compile |
| 5 |
it it hogged the processor to max |
| 6 |
and wasted all the RAM + swap space. You can imagine what that did to rest |
| 7 |
of the system response time. |
| 8 |
Well i managed to kill the compilation with Ctrl-C. |
| 9 |
|
| 10 |
I tried to compile it again with the same result, after that i wanted kmail |
| 11 |
out of my system for good so did |
| 12 |
emerge -aC kmail. |
| 13 |
|
| 14 |
I was all happy about it been gone, so i did an update again, left it |
| 15 |
compile through the night, but didn't notice that kmail |
| 16 |
wanted to be compiled again. i left it running over the night and it didn't |
| 17 |
compile. Just stood there eating all the resources. |
| 18 |
|
| 19 |
ATM i cant post the gcc output when kmail compilation breaks as i am not on |
| 20 |
work until tomorrow and our shitty router |
| 21 |
seems to have problem with port forwarding again... :( |
| 22 |
|
| 23 |
If someone has any idea on either how to remove kmail completely or make it |
| 24 |
compile right id appreciate it. |
| 25 |
|
| 26 |
-- |
| 27 |
r. |
Archives