| 1 |
Richard Fish wrote: |
| 2 |
> On 9/6/06, Jarry <jarry@×××.net> wrote: |
| 3 |
>> Well, gcc upgrade is not so painless as one might think. |
| 4 |
>> Any ideas how to fix this? |
| 5 |
> |
| 6 |
> Looks like you need to use dietlibc-0.30 with gcc-4.1: |
| 7 |
> |
| 8 |
> http://bugs.gentoo.org/show_bug.cgi?id=140905 |
| 9 |
|
| 10 |
Hm, but 0.28 is stable, 0.30 is "~" (amd64) |
| 11 |
Moreover, I have read it, but there is remark: |
| 12 |
|
| 13 |
"dietlibc-0.30 is broken on amd64, see bug #138468" |
| 14 |
|
| 15 |
OK, I will try it, but how? I'm in the middle of |
| 16 |
updating my world after gcc-update. I will add |
| 17 |
"dev-libs/dietlibc ~amd64" into packages.keywords, |
| 18 |
but what then? Again "emerge -eav world"? |
| 19 |
Or should I first update only dietlibc and then world? |
| 20 |
|
| 21 |
Jarry |
| 22 |
|
| 23 |
-- |
| 24 |
gentoo-user@g.o mailing list |
Archives