| 1 |
Should I *not* emerge this gcc? I usually hold off on gcc updates when |
| 2 |
I'm in the middle of other testing. Right now, I'm doing a lot of beta |
| 3 |
testing with R and Atlas, so I held off when the latest gcc showed up |
| 4 |
after "emerge sync". |
| 5 |
|
| 6 |
Spider wrote: |
| 7 |
|
| 8 |
>On Sun, 2005-04-10 at 16:22 -0400, Mike Frysinger wrote: |
| 9 |
> |
| 10 |
> |
| 11 |
>>On Sunday 10 April 2005 11:31 am, Spider wrote: |
| 12 |
>> |
| 13 |
>> |
| 14 |
>>> A touch late, but this uncovered a bug in libtool. |
| 15 |
>>> |
| 16 |
>>> |
| 17 |
>>re-emerge libtool and it'll fix itself |
| 18 |
>> |
| 19 |
>> |
| 20 |
> |
| 21 |
> |
| 22 |
>Yep, I know that. |
| 23 |
> |
| 24 |
>Unfortunately, thats -not- going to be a "solution" for the people who |
| 25 |
>just installed 2005.0, got a gcc update and suddenly everything broke. |
| 26 |
> |
| 27 |
>the ~x86 version doesn't exhibit this problem, btw. stabilizing this |
| 28 |
>version might be prudent. |
| 29 |
> |
| 30 |
>//Spider |
| 31 |
> |
| 32 |
> |
| 33 |
> |
| 34 |
-- |
| 35 |
gentoo-dev@g.o mailing list |
Archives