> I guess what I don't understand is the version numbering scheme.  If I
> understand correctly, I would need to have libc.so.6.* in order to make a
> link from libc.so.6.  However, I can't find anyting above libc.5.4.38 on
> any of the sites.  Could someone give a quick explanation?
> 
> Also, once I do find the needed libraries, I probably shouldn't be
> deleting old libraries and links, right?  (ie. if I have libc.so.5 which
> points to libc.so.5.4.38 and I go out and get libc.so.6.* which I point
> libc.so.6 at, should I make sure to keep around libc.so.5 for backwards
> compatability of older programs, or will the old programs just go ahead
> and use the new libraries?)

libc.so.6 is glibc.  I got it in package glibc-2.0.5c-10 (RH 5, but
might be an update or contrib).  In /lib, libc.so.6 is a link to
glibc-2.0.5.so .

I also thought that the convention was that libthing.so.x.y should be
linked to by libthing.so.x .  Doesn't ldconfig rely on this?

You do need to keep libc.so.5 around for non-glibc programs - StarOffice
needs it, for example.  On RH5, it's moved to /usr/i486-linux-lib/lib
(except that a typo in the 5.4.38 rpm puts it in /usr/i486-linuxlib/lib
- adjust /etc/ld.so.conf accordingly).



Jon Moore


-- 
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
         To unsubscribe: mail [EMAIL PROTECTED] with 
                       "unsubscribe" as the Subject.

Reply via email to