A problem after upgrading/downgrading glibc

Message

Koala Kid · Post by **Koala Kid** » Sat Mar 11, 2006 7:10 pm

I've installed glibc 2.4 today (as part of usual emerge -uDv world) and experienced some troubles after that (couldn't load the X), so I decided to go to the previous version 2.3.6. After reboot I can't even acces my system, thanks to the following nice error message:

Code: Select all

/sbin/init: relocation error: /lib/tls/libc.so.6: symbol_dl_out_of_memory, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with time preference.
[   33.848825] kernel panic - not syncing: attempted to kill init!

How do I fix that ? It looks very bad anyway...
Thank you...

zwik · Post by **zwik** » Sat Mar 11, 2006 7:57 pm

I'm having similar experiences

. I also downgraded after an upgrade of glibc. I can't get into my system anymore. Something with init. I booted up Knoppix and tried to chroot into my system. There I get this error:

Code: Select all

# chroot /mnt/gentoo/ /bin/bash
chroot: cannot run command `/bin/bash': No such file or directory

No idea what to do

.

darkphader · Post by **darkphader** » Sat Mar 11, 2006 9:27 pm

My system was running fine with glibc-2.4 but I realized I hadn't restarted X since the upgrade. After reading this post I did that and got the relocation error but after remerging xorg all was well again.

Chris

Maedhros · Post by **Maedhros** » Sat Mar 11, 2006 10:00 pm

zwik wrote:No idea what to do .

You might be able to use the statically linked busybox instead (if it's installed) - try chroot /mnt/gentoo /bin/bb sh...

I have no experience with actually making busybox work though, but it's worth a try.

brihall · Post by **brihall** » Sat Mar 11, 2006 10:59 pm

Re-emerging xorg-x11 fixed it for me.

However, with glibc-2.4 on one of my Gentoo 2006.0 boxen (~x86), oooqs DOSes the KDE startup (so much HDD access you cannot access the box). "emerge -C oooqs" fixes that, but now of course the first OOo start takes a little longer.

zwik · Post by **zwik** » Sat Mar 11, 2006 11:55 pm

Maedhros wrote:
zwik wrote:No idea what to do .
You might be able to use the statically linked busybox instead (if it's installed) - try chroot /mnt/gentoo /bin/bb sh...

I have no experience with actually making busybox work though, but it's worth a try.

While "playing" with ldd on bash on the mount i found out all symlinks in /lib were pointing to files that would belong to glibc-2.4. I fixed every symlink in /lib manually to the "old" files of glibc

.

zwik · Post by **zwik** » Sat Mar 11, 2006 11:57 pm

brihall wrote:Re-emerging xorg-x11 fixed it for me.

However, with glibc-2.4 on one of my Gentoo 2006.0 boxen (~x86), oooqs DOSes the KDE startup (so much HDD access you cannot access the box). "emerge -C oooqs" fixes that, but now of course the first OOo start takes a little longer.

So if i remerge xorg X should work again?

Did you had nptl before? On glibc other than 2.4 that is.

houtworm · Post by **houtworm** » Sun Mar 12, 2006 4:34 am

zwik wrote: I fixed every symlink in /lib manually to the "old" files of glibc .

Wow! you saved my day, thanks!
dank je wel

dufeu · Post by **dufeu** » Sun Mar 12, 2006 4:53 am

I had the same problem starting X after emerging glibc-2.4.

I re-emerged =sys-libs/glibc-2.3.6-r3 and all is now well.

I'm not going to yet upgrade to glibc-2.4 again because I don't know what other packages might be effected. Besides xorg that is. I'm guessing that we'll need to do a revdep-rebuild on the .so object.

In the meantime, I suspect a number of people will be hit with this problem so making this topic sticky might be a good idea.

edit: The following bugs have recently appeared in bugzilla and most appear related.

Code: Select all

125809    nor  	P2  PPC  	x11@gentoo.org  	NEW  	  	mesa-6.4.2-r1 fails to build on ppc64 with glibc-2.4/gcc-...
125818 	nor 	P5 	AMD 	toolchain@gentoo.org 	NEW 		sys-libs/glibc-2.4 and problem with locale
125832 	maj 	P2 	All 	mozilla@gentoo.org 	NEW 		Compilation of mozilla 1.7.12 (and probably firefox/thund...
125861 	nor 	P2 	All 	games@gentoo.org 	NEW 		zsnes 1.42 crashes with glibc 2.4
125868 	maj 	P2 	All 	base-system@gentoo.org 	NEW 		After installation of glibc-2.4: /usr/bin/python: relocat...
125887 	nor 	P2 	AMD 	bug-wranglers@gentoo.org 	NEW 		net-misc/wget-1.10.2 fails (gcc 4.1/glibc 2.4)

nesl247 · Post by **nesl247** » Sun Mar 12, 2006 5:12 am

People upgrading from 2.3.6 need to upgrade glibc, then the toolchain (glibc binutils gcc libstdc++-v3 libtool portage) and then emerge -e world.

Code: Select all

# emerge glibc binutils gcc libstdc++-v3 libtool portage
# emerge -e world

There is a change between the linked version is why. (Probably something more complex, but this is my understanding)

Koala Kid · Post by **Koala Kid** » Sun Mar 12, 2006 6:29 am

zwik wrote:
Maedhros wrote:
zwik wrote:No idea what to do .
You might be able to use the statically linked busybox instead (if it's installed) - try chroot /mnt/gentoo /bin/bb sh...

I have no experience with actually making busybox work though, but it's worth a try.
While "playing" with ldd on bash on the mount i found out all symlinks in /lib were pointing to files that would belong to glibc-2.4. I fixed every symlink in /lib manually to the "old" files of glibc .

Hey buddy, could you explain a little more about what exactly you did ? I can't chroot my system from a LiveCD, always receive the message I mentioned in my original post...

zwik · Post by **zwik** » Sun Mar 12, 2006 10:21 am

Koala Kid wrote:
zwik wrote:
Maedhros wrote:
zwik wrote:No idea what to do .
You might be able to use the statically linked busybox instead (if it's installed) - try chroot /mnt/gentoo /bin/bb sh...

I have no experience with actually making busybox work though, but it's worth a try.
While "playing" with ldd on bash on the mount i found out all symlinks in /lib were pointing to files that would belong to glibc-2.4. I fixed every symlink in /lib manually to the "old" files of glibc .
Hey buddy, could you explain a little more about what exactly you did ? I can't chroot my system from a LiveCD, always receive the message I mentioned in my original post...

I mounted the partition where the /lib directory is found. I "cd'ed" into it for example "cd /mnt/gentoo/lib". With the command "ls -al" you see some symlinks are linked with files with the number 2.4 in it. Those are wrong! You unlinked those files with unlink and ln -s'ed the new symlinks with the files with the number 2.3.6 in it.

That's all

.

dufeu · Post by **dufeu** » Sun Mar 12, 2006 9:47 pm

nesl247 wrote:People upgrading from 2.3.6 need to upgrade glibc, then the toolchain (glibc binutils gcc libstdc++-v3 libtool portage) and then emerge -e world.
Code: Select all
# emerge glibc binutils gcc libstdc++-v3 libtool portage
# emerge -e world
There is a change between the linked version is why. (Probably something more complex, but this is my understanding)

That's an awful lot of work. Basically it means re-building the entire system.

I'm sure this will work, but is it really needed?

nesl247 · Post by **nesl247** » Sun Mar 12, 2006 10:20 pm

dufeu wrote:
nesl247 wrote:People upgrading from 2.3.6 need to upgrade glibc, then the toolchain (glibc binutils gcc libstdc++-v3 libtool portage) and then emerge -e world.
Code: Select all
# emerge glibc binutils gcc libstdc++-v3 libtool portage
# emerge -e world
There is a change between the linked version is why. (Probably something more complex, but this is my understanding)
That's an awful lot of work. Basically it means re-building the entire system.

I'm sure this will work, but is it really needed?

Alot of packages are linked to the older version, so I would do this. It might not be explicitly required but it is recommended. Plus this will allow your system have any benefits brought on by glibc2.4.

nmbrthry · Post by **nmbrthry** » Sun Mar 12, 2006 10:38 pm

I always use emwrap for rebuilding after a toolchain update. See this thread for more details.

dufeu · Post by **dufeu** » Mon Mar 13, 2006 3:45 am

nmbrthry wrote:I always use emwrap for rebuilding after a toolchain update. See this thread for more details.

Thank you very much. The thread explains and clarifies quite a bit for me. Including the need to rebuild everything clean after the toolchain gets updated.

I'll be following instructions this week.

Koala Kid · Post by **Koala Kid** » Wed Mar 15, 2006 4:11 pm

nesl247 wrote:
dufeu wrote:
nesl247 wrote:People upgrading from 2.3.6 need to upgrade glibc, then the toolchain (glibc binutils gcc libstdc++-v3 libtool portage) and then emerge -e world.
Code: Select all
# emerge glibc binutils gcc libstdc++-v3 libtool portage
# emerge -e world
There is a change between the linked version is why. (Probably something more complex, but this is my understanding)
That's an awful lot of work. Basically it means re-building the entire system.

I'm sure this will work, but is it really needed?
Alot of packages are linked to the older version, so I would do this. It might not be explicitly required but it is recommended. Plus this will allow your system have any benefits brought on by glibc2.4.

Hehe, nice tip

Anyway, I ended with re-installing the whole system cause too many things stopped working and it was easier to re-install.

A problem after upgrading/downgrading glibc

A problem after upgrading/downgrading glibc

Perhaps this should be made a sticky?

????????

Re: ????????

Thank you for the pointer to the thread.

Re: ????????