Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: comp.unix.wizards
Subject: Re: Shared libraries: what functions are dynamically linked in?
Message-ID: <7355@auspex.auspex.com>
Date: 23 Apr 91 17:44:43 GMT
References: <47601@ut-emx.uucp> <1991Apr22.211732.3896@cbnewsl.att.com>
Distribution: usa
Organization: Auspex Systems, Santa Clara
Lines: 18

>You can see what functions whould be linked in by typing in:
>	mn /usr/lib/libc.so.1

(Assuming you meant "nm", not "mn"), that'll show all the functions that
are in the shared library, regardless of whether any particular
executable uses them or not.  I'm not sure which the original poster
wanted.

>To see which executables are using dynamic shared libraries, type in:
>	mcs -p -n .interp full_path_name
>
>At least this is how it works on: AT&T UNIX System V/386 Release 4.0

Somewhat the same in SunOS 4.x (not surprisingly...), except that there
ain't no "mcs" command or ".interp" section, so you just use "file" to
see if an executable is using dynamic shared libraries.  "ldd" should
work in S5R4 (the stuff shown for S5/386R4.0 should apply to any S5R4
implementation) and in SunOS 4.x.