A very small step in the right direction...I unzipped the quickpkg I made into the /mnt/gentoo and now I am able to chroot in there. If I try to re-emerge glibc-2.3.6 though it complains that "downgrading" is a sure way to destruction. I'm pretty sure it would be safe for me to downgrade because I didn't really do much of anything after installing 2.4 so I'm not sure what the problem would be. The problem is that it still think 2.4 is installed.
Ah, here we go. emerge -C =glibc-2.4* worked fully this time (it didn't work fully before, which I forgot to mention). Now it will let me re-emerge =glibc-2.3* overtop of the quickpkg that I unpacked. I am also not compiling with nptlonly (which came in to my profile through 2006.1), so it is now emerging with the exact same use flags that it was before (and the same as what the quickpkg is made from). So hopefully everything will be cool and I will be able to reboot into this machine (I couldn't even boot into it after this b0rking happend). Dave On 9/1/06, David Grant <[EMAIL PROTECTED]> wrote:
Here's what I did: I have sticking with gcc-3.x for now... I wanted to upgraded glibc to 2.4. I upgraded it and at the end of the emerge I got this error similar to this one, mine involved libresolv: http://forums.gentoo.org/viewtopic-t-443051-postdays-0-postorder-asc-highlight-libresolv+glibc-start-0.html I then did emerge -C =glibc-2.4-r4 to remove glibc-2.4 completely and leave 2.3. Now my whole system is b0rked. I can't even chroot in because it can't run /bin/sh or /bin/bash on the new system. Basically all binaries are screwed on the new system. I do have a quickpkg of glibc2.3 but I'm not sure what good that will do. If anyone can help me I'm desperate to save this system and not have to reinstall. -- David Grant http://www.davidgrant.ca
-- David Grant http://www.davidgrant.ca -- gentoo-user@gentoo.org mailing list
