Michael [Plouj] Ploujnikov ha scritto:
> Hi,
> Before I file this as a bug I'd like to make sure it's not caused by
> something wrong with my system. Please help me determine that.
> In the past two days I was trying to upgrade my glibc from version 2.4
> to 2.5. Each time I tried it the emerge process failed at the very
> last point - I think when the actual files were being installed into
> my system. Here is the relevant output:
Don't know if it's your system or a glibc bug (my upgrade went OK), but
anyway in the forums I found what seems to be a possible solution to
have a working system back (the poster had a similar, but not identical
problem):
"I downloaded the 2006.0 livecd, boot it, chroot into my system and had
the same issues with grep, sed, et al. (not able to emerge anything).
exited the chroot, built a binary of glibc-2.3.5 in the CD environment
(emerge -B sys-libs/glibc), moved it to my packages dir
(/mnt/gentoo/usr/portage/packages/{All,sys-libs}/glibc-2.3.5...whatever
it was), jumped back into the chroot, emerged the binary which worked
and now i'm in the process of rebuilding my system (emerge linux-headers
&& emerge -e system && emerge -e ...). I'm taking the opportunity to
move to gcc 4.1 (already done) and am building a new binary for glibc
2.3.6-r3 just incase the emerge of 2.4 dies && blows things up again.
i'll report back here if and when it's working."
m.
--
gentoo-user@gentoo.org mailing list
