On Sun, Jun 30, 2002 at 02:00:15PM +0530, Vinay Pai wrote: > Glibc was another matter. I installed glibc 2.2.3 with the prefix > /usr/local (the default) and everything seemed fine. But when I later > upgraded to 2.2.5 things went nuts. I don't know what I did, but > somehow the linker (ld-linux) couldn't find glibc 2.2.3 so everything > I'd compiled on my system failed. When I copied ld-2.2.3.so to /lib > hoping it would be found there, all of redhat's stuff (cp, ls etc!!!) > stopped working. I had to boot from the rescue CD to fix that. > Ultimately I ended up compiling both the glibc 2.2.3 and 2.2.5 and > installing them both with /usr prefix, and everything's been working > fine ever since. > > My conclusion, upgrading glibc can break your system totally if you > don't know that you're doing!
Of course, it won't help if you just upgrade your glibc. Because all programs are dynamically linked to glibc ( not all .. but almost ). So, you need to recompile them, or, in case that everything is compatible except the version numbers, create symlinks. For the kernel .... [root@tachyon root]# file /boot/vmlinux-2.4.18-3 /boot/vmlinux-2.4.18-3: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, not stripped [root@tachyon root]# Note: statically linked. -- jaju _______________________________________________ http://mm.ilug-bom.org.in/mailman/listinfo/linuxers
