| 1 |
Alex Bennee posted <1121624098.9429.5.camel@malory>, excerpted below, on |
| 2 |
Sun, 17 Jul 2005 18:14:57 +0000: |
| 3 |
|
| 4 |
> On Fri, 2005-07-15 at 09:13 -0700, Zac Medico wrote: |
| 5 |
> |
| 6 |
>> I had a similar problem (actually with plain x86) a couple months ago. |
| 7 |
>> That was with glibc-2.3.4.20040808-r1. |
| 8 |
> |
| 9 |
> Yes that one. I've been unable to succesfully upgrade to 2.3.5 without |
| 10 |
> hitting the failure. However I left my system building a fresh partition |
| 11 |
> from scratch over the weekend - it managed to upgrade to 2.3.5 without a |
| 12 |
> problem. |
| 13 |
> |
| 14 |
> Something has obviously broken on my main partition that is preventing the |
| 15 |
> update. Perhaps the difference in ld.so.conf explain things? |
| 16 |
|
| 17 |
I've been running glibc-2.3.5 fine since April, save for the time I was |
| 18 |
running 2.3.5-20050421, the snapshot with gcc-4.x fixes. (The snapshot |
| 19 |
worked in amd64 mode, compiled with gcc4 of course, but the x86 ABI |
| 20 |
version failed, causing further gcc/glibc/sandbox emerge failures because |
| 21 |
they have multilib elements and failed during the 32-bit configure step |
| 22 |
due to being unable to load a library, presumably glibc, when testing for |
| 23 |
a working (32-bit) gcc-compiler. After I figured out that was the |
| 24 |
problem, I simply returned to the normal 2.3.5 version, compiled with |
| 25 |
gcc-3.4.x since it didn't have the gcc4 patches applied.) |
| 26 |
|
| 27 |
-- |
| 28 |
Duncan - List replies preferred. No HTML msgs. |
| 29 |
"Every nonfree program has a lord, a master -- |
| 30 |
and if you use the program, he is your master." Richard Stallman in |
| 31 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-amd64@g.o mailing list |
Archives