[Prev][Next][Index]

Re: How to upgrade libc?



Excerpt of message (sent 15 April 1996) by Daniel Vainer:
> I've tryed to upgrade libc-5.0.5 to libc-5.3.9. I untared bin distribution of it, did everything release.libc-5.3.9 stays about and run ldconfig.
> After this I did ldconfig -p to see what happaned and it showed me that libc.so.5 still points to libc-5.0.5 and some strange thing called dnname points
>  to libc-5.3.9. Than I changed the link libc.so.5 to point to the new libc
>  mannualy and did ldconfig -v again - it changed it back with great consistancy.
>  Than I've compiled some Ada program with no problem, but when I tryed to run it I've seen the message: "can not resolve __libc_opendir". The same thing with
> compiled by me C program. It's not happaning all the time: with some things does, with others doesn't. 
> What I'm doing wrong?
> 
> In general - is there some good routine to upgrade slakware linux? ( I tryed to remove old libc package with pkgtool, but after that my system crashed with the messages like "can't resolve link libc.so.5" or something like this).
> Any help will be appreciated.
> 	Regards,

I went through some of the above mensioned hussle when upgrading to
libc.2.18, and then back to libc.5.0.9. While I am sure there is a
better way to do it, here is what I did:

1. When actually installing the libc package, I booted linux up  with
the option root=/dev/fd1 (or root=/dev/fd0) passed to LOADLIN (or
LILO), and used a root diskette - for safety reasons.

2. I had the same problems with soft links to libc.so.5 being
consistently changed back to the original. ld is responsible for it, I 
beleive - to prevent loaded-up shared libraries from being mistakenly
erased, or something like that. What I did was moving the older
libc.so.5.2.18 to another directory, deleting /etc/ld.so.cache and rebooted.

3. I had to recompile some packages I compiled myself against
libc.so.2.18 (and its include files - each libc must be installed with 
its own include files, of course).