Don't update glibc if your running unstable.

[AutoBot]

If your running unstable, I recommend you don't update glibc as I did and it blew up my test system beyone repair. Can't give anymore information than that as I don't exactally know what happen, I ran emerge --update world and somewhere down the line the update terminated on glibc but not before portage managed to uninstall it first.

[Lovechild]

Works relatively painlessly for me - I however didn't notice all that prelinking stuff everyone so crazy about, I'm guessing that it's some sort of setting I forgot to set.

So aside that this is a glibc that natively compiles with a gcc3 compile (ok, it's a branch release, the gcc boys are late.... again... but hey, it works), there's really no reason to upgrade right now.

Did you remember to do a emerge -e world to fix the staticly linked stuff and make sure everything is linked against your new glibc?

-edit-

to ensure that stuff worked(tm) I did this

emerge rsync && emerge binutils gcc glibc && emege binutils gcc && emerge -u world && emerge -e world

[AutoBot]

It was a 1.4 install, not a 1.2 update...This only applies the the glibc currently on the unstable branch.

[Lovechild]

It was a 1.4 install, not a 1.2 update...This only applies the the glibc currently on the unstable branch.

This was from a 1.4rc1 install -> 1.4 unstable (~x86) install. My guess is that you have stuff still staticly linked to glibc 2.2.5

[Exci]

i emerged to 2.3 without any problems too..
but because i had some troubles with the linking i wanted to go back.. but never did it

but yesterday my emerge -up world said that he wanted to install the old glibc again .. I did it and this morning my total system is ..uhm .. well not very nice to me ..

i remembered a ld-config from the ncursus problem from a week ago .. and that totally blew my system

someone with advise?

[AutoBot]

It was a 1.4 install, not a 1.2 update...This only applies the the glibc currently on the unstable branch.

This was from a 1.4rc1 install -> 1.4 unstable (~x86) install. My guess is that you have stuff still staticly linked to glibc 2.2.5

Thats what I believe also.

[synonymousca]

Exci: Provided gcc still works, unmask glibc-2.3.1 in package.mask, and then reupgrade to it.

Alternatively, rebuild every package that does not work, as well as dependencies.

There's something in Bugzilla about the problems that the late masking of glibc-2.3.1 will (and already has) caused people, which you may want to look up. At present, it's just a 'This was a really bad idea' post, though.

[Exci]

I wish I could

i can't boot, only with the boot cd, i can't chroot to my gentoo-system because of linking problems.

if i knew how to relink and to what i could mount my gentoo system from the disk and do some relinking :/

[Kinou-]

I've got the same problem with glibc ....

Hope I'll be able to repair it this evening.

Gentoo 1.4 (no upgrade from 1.2)

[Lowspirit]

I'm officially freaked out... I emerged all the unstable stuff when the unstable tree news was posted, everytjomg have been working without any problem since, but reading this kind of makes me wonder... I'm pretty sure I've already compiled a couple of things with new glibc, should I just stay with 2.3.1 or should I emerge the old one again?

[Exci]

DON'T emerge the old one

that's what caused my problems

[AutoBot]

If everything is working your ok, never unmerge glibc.

[IWBCMAN]

I did the unstable thing too....I treated the new glibc as a case for bootstrapping....I did the little circular dependency dance and everything works fine for-except:
a) it kill my java(libjavaplugin) iiiieeeeee......I get a relocation error
b) the new xfree 4.2.1 does funky things with cursive fonts in konqueror...have you ever seen diagonal fonts ?
c) for some reason opgengl-update forgets its settings.....I have to re-run opengl-update nvidia-each time I play a game .....

as part of the little dance
after setting UNSTABLE in /etcv/make.conf
emerge -pu world
USE="bootstrap" emerge gcc baselayout gettext textutils libtools binutil glibc && emerge gcc glibc && emerge -e system && emerge -e world

it was a bit overkill, I know, and it never suceeeded in re-emerging world...bombed out half way through....but everything *seems* to be ok.....

[jkozak]

emerge -e world completely hosed my system as well; kernel panic on boot. Things like bash and ls moan about lack of GLIBC_2.3

Can I recover from via the install CD? I can get a shell up by copying a version of bash over from the CD

[jkozak]

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?

[sven]

It happend to me, too ;(
I can not boot my system anymore!! How can I rescue my system? Please help!

[Lolo-]

exactly the same
tried to boot with the cd but after mounting/chrooting/etc , it still complains that bash needs glibc 2.3
another idea to repair ?

[Exci]

we need alot of libraries relinked..
wasn't it possible to do a ld-config with a cache/config file?

so can't someone make that so that we can normally boot and maybe can do something to fix the rest of the system?

just a wild guess.. :/

[kepe]

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:
ld-linux.so.2
libnss_compat.so.2
libpthread.so.0
librt.so.1
libdl.so.2
libutil.so.1
libresolv.so.2
libnss_nis.so.2
libnss_hesiod.so.2
libnss_files.so.2
libnss_dns.so.2
libm.so.6
libc.so.6
libcrypt.so.1
libdl.so.2

I think thats all of them.
Then I was able to reboot into gentoo, and remerge glibc 2.3.1
Hope this helps

[jkozak]

well, I booted off the install CD, copied /bin/bash from that to /tmp/bash on my sickly system, chroot'd into it, ran ldconfig and rebooted. System back, now it's the long dark "emerge -e world" of the soul.

[dbacon]

DON'T emerge the old one

that's what caused my problems

wow, so I read this forum to my horror while the update was running.
I scrammed back to the term to interrupt it, and it was unzipping glibc-2.2.5.
Thanks for the heads up, guys, my system is spared.

[Exci]

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:
ld-linux.so.2
libnss_compat.so.2
libpthread.so.0
librt.so.1
libdl.so.2
libutil.so.1
libresolv.so.2
libnss_nis.so.2
libnss_hesiod.so.2
libnss_files.so.2
libnss_dns.so.2
libm.so.6
libc.so.6
libcrypt.so.1
libdl.so.2

I think thats all of them.
Then I was able to reboot into gentoo, and remerge glibc 2.3.1
Hope this helps

i tried that but i got this sort of errors:

Code: Select all

python2.2: /lib/libc.so.6: version 'GLIBC 2.3' not found (required by python2.2)
python2.2: /lib/libc.so.6: version 'GLIBC 2.3' not found (required by /lib/libpthread.so.0)
python2.2: /lib/libc.so.6: version 'GLIBC_PRIVATE' not found (required by python2.2)

(this is what i got when i tried a emerge -s)

[sven]

I managed to chroot into my system by copying /bin/bash and /lib/libncurses.5 from the cd to my system but I still can not run emerge. I get the same error message as Exci.

[sven]

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?

[sven]

I think a lot of people have fragged their system after an emerge -u world...

Could a Gentoo developer please create a rescue .tbz file with all the needed GLIBC 2.3 files which we then can extract over the damaged system by using the rescue cd, please?