Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: jason@cs.odu.edu (Jason "dedos" Austin)
Newsgroups: comp.sys.sun
Subject: Re: ld.so looks for wrong libc.so
Keywords: Miscellaneous
Message-ID: <2149@brchh104.bnr.ca>
Date: 24 Mar 91 12:32:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 15
Approved: Sun-Spots@rice.edu
X-Original-Date: Sat, 23 Mar 91 20:55:08 -0500
X-Refs:  Original: v10n58
X-Sun-Spots-Digest: Volume 10, Issue 65, message 2
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

In article <2005@brchh104.bnr.ca> mea@sparta.com (Mike Anderson) writes:

-> Now comes the strange part.  When I try to run certain programs like vi, I
-> get a message from ld.so saying it can't find libc.so.2 and the program
-> sputters and dies.  Now when I look at my /usr/lib, I see libc.so.1.6 but
-> no libc.so.2.  The ld.so.cache looks right (it shows libc.so.1.6) as does
-> LD_LIBRARY_PATH.

Vi uses libc.so.2 which is the system V version of the C library, and that
library is kept in /usr/5lib.  ld.so should default to scanning that
directory along with /usr/lib.  I would check to make sure /usr/5lib
exists.

Jason C. Austin
jason@cs.odu.edu