So if I upgrade glibc, the kernel won't work?
On Jun 29, 2002 at 19:49, Satya wrote:
So if I upgrade glibc, the kernel won't work?
Obviously, not enough information.
I'm about to upgrade everything: kernel, gcc, glibc. If I upgrade glibc, the current kernel won't work, right? Or will it?
If I put the new glibc in a separate location, how will the new kernel find it when it is being compiled?
Meanwhile, when would I compile gcc, and how, to prevent similar deadlocks?
On Sat, Jun 29, 2002 at 08:10:55PM -0700, Satya wrote:
On Jun 29, 2002 at 19:49, Satya wrote:
So if I upgrade glibc, the kernel won't work?
Obviously, not enough information.
I'm about to upgrade everything: kernel, gcc, glibc. If I upgrade glibc, the current kernel won't work, right? Or will it?
If I put the new glibc in a separate location, how will the new kernel find it when it is being compiled?
Meanwhile, when would I compile gcc, and how, to prevent similar deadlocks?
I think that the kernel does not depend on shared libraries. So, it shouldn't matter if you change your glibc. Just go ahead.
( To support the above view -- I tried out LFS : linux from scratch : where I had to recompile my own glibc and gcc, and i had no problems with the old kernel while in "chroot" into this partition, as well as booting into this partition as root with the old kernel )
gcc - i suggest you use a different prefix .. say, /usr/local/gccx, because some programs ( esp. c++ ones ) need some libraries with gcc ( esp. gcc3 )
hth.
-
Ravindra Jaju -
Satya