Don't update glibc if your running unstable.

Message

zypher · Post by **zypher** » Fri Oct 25, 2002 8:44 am

This whole bleeding edge thing has

a) provided me with a new gentoo-ut2003-live-cd
b) a fresh system and the possibility to change my fs
c) a spoiled weekend...

Hmm as I suggested months ago, the "~arch" thingie is nice, better would be a customized package.mask (in /usr/porlage.local).

Good idea?
Yes.

Greetz,
Zypher

Kinou- · Post by **Kinou-** » Fri Oct 25, 2002 9:25 am

I've resolve my problem :

Boot from the live CD
Mount my partitions
Copy the stage3 (/bin /lib ..) to my parition where Gentoo was.

Juste save some configurations files (like your modules.autoload ...)

And reboot.

That works fine now.

EzInKy · Post by **EzInKy** » Fri Oct 25, 2002 10:18 am

I also ran into some problems after upgrading to glibc 2.3.1, but mostly of my own making. After the upgrade and recompiling, one binary program, crossover plug-in, quit working. I too tried going back to 2.2.5, which of coarse broke everything compiled for 2.3.1.

My fix was to boot into Mandrake, chroot into Gentoo, and use Midnight Commander (sure would be nice if MC was part of the base install, btw) to relink all my libs to anything 2.3.1, then reboot back to Gentoo and unmerge 2.2.5.

An email for support to Codeweaver's got me a response that stated they were working on a fix in their beta. The whole ordeal reminded me of Window's dll hell, lol...but does go to show why source is better than precompiled binaries.

sven · Post by **sven** » Fri Oct 25, 2002 12:45 pm

I also managed to rescue my system! What I did was

1) Booted from the live cd
2) Mounted the root partition
3) Backuped /bin/bash and /lib/libncurses.so.5 from the root partition
4) Copied these two files from the cd to the root fs
5) chrooted into the root fs
6) ldconfig
6) ebuild /usr/portage/sys-libs/glibc/glibc-2.3.1.ebuild merge
7) exit chroot
8) copy backuped files back to /bin/bash and /lib/libncurses.so.5
9) reboot and done!

phew, that one was close!!!

Exci · Post by **Exci** » Fri Oct 25, 2002 3:01 pm

sven wrote:I also managed to rescue my system! What I did was

1) Booted from the live cd
2) Mounted the root partition
3) Backuped /bin/bash and /lib/libncurses.so.5 from the root partition
4) Copied these two files from the cd to the root fs
5) chrooted into the root fs
6) ldconfig
6) ebuild /usr/portage/sys-libs/glibc/glibc-2.3.1.ebuild merge
7) exit chroot
copy backuped files back to /bin/bash and /lib/libncurses.so.5
9) reboot and done!

phew, that one was close!!!

this didn't work for me

as soon as i did a ldconfig everyhting was relinked back to 2.3.1 libs
if i want to do it the other way around (first ebuild then ldconfig) i get a error with ebuild

Code: Select all

/usr/bin/python2.2: /lib/libc.so.6: version 'GLIBC_2.3' not found (required by /usr/bin/python2.2)

ow and i'm booting from a 1.2 boot cd .. but it has the 2.5.1 libs, is that a problem?

--edit--
do i have to relink everything to 2.3.1 or does everything has to point to the 2.2.5 libs? i'm confused now :/ not much sleep .. to much stress ..AAAH

sven · Post by **sven** » Fri Oct 25, 2002 3:57 pm

Exci wrote:ow and i'm booting from a 1.2 boot cd .. but it has the 2.5.1 libs, is that a problem?

try to boot from the 1.4_rc1 live cd, I've used it!

Exci · Post by **Exci** » Fri Oct 25, 2002 3:58 pm

sven wrote:
Exci wrote:ow and i'm booting from a 1.2 boot cd .. but it has the 2.5.1 libs, is that a problem?
try to boot from the 1.4_rc1 live cd, I've used it!

gonna download it right now

sven · Post by **sven** » Fri Oct 25, 2002 4:09 pm

Exci wrote:gonna download it right now

Wish you luck!

Exci · Post by **Exci** » Fri Oct 25, 2002 7:33 pm

same problem :'(

anduhm .. is it correct that i only have one version of libc?
i only have libc-2.2.5.so and not libc-2.3.1

kepe · Post by **kepe** » Fri Oct 25, 2002 8:39 pm

sven wrote:
kepe wrote:I made the same mistake of not checking what I was updating. I fixed the problem here by booting to an alternate distro, mounting /lib and manually relinking the approariate libs, which are, to best of my recollection [...]
How do I manually relink these files?

I booted into another distro, mounted gentoo's /lib partition, then I removed the links pointing to 2.2.5 and relinked them to 2.3.1
I worked here perfectly

Exci · Post by **Exci** » Fri Oct 25, 2002 8:46 pm

that's what ldconfig does for me... but i miss libc2.3.1 :/

is it possible that someone can upload it for me ?

i'm not sure that helps tho

kepe · Post by **kepe** » Fri Oct 25, 2002 9:04 pm

Exci wrote:that's what ldconfig does for me... but i miss libc2.3.1 :/

is it possible that someone can upload it for me ?
i'm not sure that helps tho

If you didnt remove 2.3.1, then libc.so.6 is a link pointing to 2.2.5....just remove that link and link libc.so.6 to 2.3.1

Exci · Post by **Exci** » Fri Oct 25, 2002 9:08 pm

i think i removed it yesterday, when i was relinking everything ..
it was 6 in the moring :/

stupid me... is it fixable ?

kepe · Post by **kepe** » Fri Oct 25, 2002 9:32 pm

yes, use the live cd, or boot another OS, then mount gentoo's /lib...then relink it to 2.3.1

Exci · Post by **Exci** » Fri Oct 25, 2002 9:34 pm

how can i link to something that isn't there?
i deleted it by mistake

kepe · Post by **kepe** » Fri Oct 25, 2002 9:40 pm

Oh, you deleted the lib, and not just the link.....

Exci · Post by **Exci** » Fri Oct 25, 2002 9:42 pm

yeah, i don't know how these libs are created .. and i don't know what will happen when i use such a lib from somebody else (from another system)

--edit---

hmm .. a emerge does a make install right?
so there must be a copy of the 2.3.1 somewhere on my system..
locate/updatedb doesnt work .. so i'll look in the 'find' manpage as soon as i have time :/

synonymousca · Post by **synonymousca** » Sat Oct 26, 2002 3:17 am

emerge wipes the build directory after it completes an install.

Otherwise, it'd be in (by default) /var/tmp/portage/(package)/work/(package)/

pdouble · Post by **pdouble** » Sat Oct 26, 2002 5:22 am

Just did an emerge rsync a couple of hours ago and there's glibc-2.3.1-r1, unmasked. It has a patch for the "ctype" stuff which is what is breaking in the static libs. emerge this and things should work OK. It fixed my problems with glibc-2.3.1.

zypher · Post by **zypher** » Sat Oct 26, 2002 1:11 pm

Ok, built a new system.
Backed up everything I thought was important and erased all partitions and startet from stage1.
Hmmm as often, the impression is that everything runs a bit faster and is just a tiny bit snappier than before.
Althoug I was in a bad mood because of the mess I made of my system downgrading to glibc2.2, I must admit, I like it better now.
And of course, I'm using 2.3.1-r1 now, would'nt be the same fun, would it

Exci · Post by **Exci** » Sat Oct 26, 2002 3:29 pm

I did a ebuild glibc-2.3.1 fetch unpack compile install on my other gentoo comp and took the libc-2.3.1.so from that one ..

i copied it to my other gentoo system chrooted into it and did a ldconfig
i tried a 'ls' and it worked

.. but when i tried a emerge or ebuild i got a
segmentation fault.

i'm gonna try to download the whole /var/tmp/portage/glibc-2.3.1 on my broken system (if it lets me) and see if i can build it myself :/

do i have to do a ebuild glibc-2.3.1 qmerge? or can i use the files without it?

bertrand · Post by **bertrand** » Sun Oct 27, 2002 2:44 am

I just brought my box back from the dead...
So I'm gonna tell what I did, in case some has the same trouble.

I updated to glibc-2.3.1-r1 and once it was done everything worked fine....except that I had trouble resolving names.

I didn't know about the emerge -e world stuff before I read the forum. I don't even know if it would have fix my trouble.
Anyway, I changed back to a stable tree and reemerge glibc-2.2.5.
Still wasn't able to resolve name. Humm, so I went for an emerge -c glibc to remove the glibc 2.3.1.
So I fired that, seen emerge telling me that glibc 2.2.5 was protected and 2.3.1 has been selected for removal.
Then it start removing files and then failed...
Oh oh, looks bad. Indeed, I was been able to a 'ls' neither an emerge glibc to fix something.

Well at this point I needed to search the web and since I only have one box, I restarted under XP and found this thread. Oh, well, that doesn't look right.
I restarted with the live cd and took the bash and libncurses like I read on the forum and try to chroot. It failed.
Damn, it's badly broken. I looked for the depencies of bash using ldd and started from that.
libncurses.so.5, libdl.so.2, libc.so.6, lib/ld-linux.so.2 are the depencies for bash. I checked them and some links were missing. I also replace the libraries with the one from the live cd. And it worked, I was able to chroot. Unfortunatly anything else worked, ls failed by telling me some rellocation error. I copied the 2 libs that was failing libpthread and librt and was able to make 'ls' works back.

Well, now the big test, reboot.
Yes, I'm backed up!

I don't know what to do now! Should I reemerge
glibc 2.3.1-r1 and do an emerge -e world after that?
Yes, I'm still willing to try 2.3.1, crazy me.

Anyway, I hope that can help some of the people that have trouble!

I had trouble when trying to recompile glibc with /usr/bin/ld.
Try 'ld --version' and if it complains about not having glibc 2.3.1, copy the one from the stage tarball and trying 'ld --version' again, it should display a banner.

Tuxisuau · Post by **Tuxisuau** » Mon Oct 28, 2002 12:13 am

I upgraded it. Let's cross fingers...

clattuc · Post by **clattuc** » Tue Oct 29, 2002 10:28 am

jkozak wrote:I *think* I can just chroot in to the copy of bash I punted over, unmask glibc-2.3.1, then run bootstrap.sh &c. Is this a reasonable thing to do?

That's what I did - (yes, I unmerge my current version of GLIBC. Not the smartest thing to do

- but, hey! I had fun)
Booted from the cd, chrooted in one vconsole, copied files over from the other cd, bootstrapped, and presto! reanimated system...

Good luck!

Nefreyu · Post by **Nefreyu** » Thu Oct 31, 2002 7:53 am

What I find odd is the following:

Clean install of gentoo, unmask glibc-2.3.1 emerge glibc installs new version.

BUT if I would not have disabled autoclean by hand emerge would clean the old version!!! All of my system is still linked to it but no, lets remove that old version... Why is autoclean / and clean for that matter so stupid?

I br0ke my last install with it... now almost this one too.