| 1 |
MAL wrote: |
| 2 |
> Terje Kvernes wrote: |
| 3 |
> |
| 4 |
>> the same thing happens here. reverting to portage 2.0.46-whatever |
| 5 |
>> fixed the problem. this also made forkbombs on my box, since even |
| 6 |
>> restarting X uses the GCC preprocessor, which didn't quite do it's |
| 7 |
>> thing. this is, for the record, a 1.2-based system. I'll submit to |
| 8 |
>> bugzilla eventually, when it's not 4am. :-) |
| 9 |
> |
| 10 |
> For the record, i'm on a was-1.2 system that I upgraded to 1.4 with the |
| 11 |
> update scripts and info here: |
| 12 |
> http://www.gentoo.org/doc/en/upgrade-to-gentoo-1.4.xml |
| 13 |
> |
| 14 |
> A good chunk of my system is probably still linked against the old |
| 15 |
> libraries, as I emerged the compat libs instead of doing an emerge -e |
| 16 |
> world. |
| 17 |
|
| 18 |
Sorry about replying to my own post, but for the record, downgrading |
| 19 |
portage to 2.0.46-r12 allowed me to emerge gcc-config successfully and |
| 20 |
then emerge xpm fine. |
| 21 |
|
| 22 |
Please could someone explain why this happened? Don't want to be stuck |
| 23 |
on a version of portage forever :/ |
| 24 |
|
| 25 |
Cheers, |
| 26 |
MAL |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
gentoo-dev@g.o mailing list |
Archives