Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: racerx!ken@uunet.uu.net (Ken Hardy)
Newsgroups: comp.sys.sun
Subject: Sun shared library dependencies
Keywords: Miscellaneous
Message-ID: <2509@brchh104.bnr.ca>
Date: 17 Apr 91 21:14:13 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 21
Approved: Sun-Spots@rice.edu
X-Original-Date: 16 Apr 91 19:27:57 GMT
X-Sun-Spots-Digest: Volume 10, Issue 83, message 12
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

Is there a utility available (or programmable) that can tell which shared
libraries an application depends upon?  I'll program it myself if
necessary, given the requisite how-to information.

I recently had to lead a user through a simple command-line-oriented
utility over then phone, but it complained that libsuntool.so.0 was
missing.  The user had not loaded SunView since his plan was to use X
exclusively, and the application did not use SunView.  It had been
inadvertantly linked with "-lsuntool".  I had to re-link and air-express a
new copy of the utility.

This apparently was the first time that someone has had to run this on a
system where SunView had never been loaded.  The "file" command on Sun
386i's tells you what shared libraries an executable will expect to find
at runtime.  The Sparc version does not do this.  I need such a facility
to avoid these situations in the future, to be used in a validation step
while configuring releases of the software.  It is apparently not enough
to check that an executable runs as expected on a given system due to the
use of dynamicly linked modules.

Ken Hardy		uunet!racerx!ken		ken@racerx.UUCP