ldd <binary-executable>
list the dynamic libraries which the binary executable requires.
A really good tip for finding out what the name of a command is (which I
stumbled across in the Debian Users Manual) is:
apropos <keyword>
which lists appropriate man page titles with a brief overview. eg:
$ apropos library
GDBM_File (3pm) - Perl5 access to the gdbm library.
dh_shlibdeps (1) - calculate shared library dependancies
hdf (5) - Hierarchical Data Format library
hosts_access (3) - access control library
intro (3) - Introduction to library functions
ldd (1) - print shared library dependencies
paperdone (3paper) - begin and end using the paper library
paperinit (3paper) - begin and end using the paper library
resolv+ (8) - enhanced DNS resolver library
stdio (3) - standard input/output library functions
svgalib (7vga) - a low level graphics library for linux
undocumented (3) - undocumented library functions
uselib (2) - select shared library
(7vga) - a fast framebuffer-level graphics library
based ion svgalib
and there is ldd.
HTH
Rich
ktb wrote:
>
> A few weeks ago someone posted a command that showed the dependencies of
> a program. I must have inadvertently deleted it and can't find it in
> the archives. Anyway I would like to know how to reveal what libs a
> program uses or needs and once I find the libs know how to find the
> package the libs reside in. How do I do this?
> Thanks,
> kent
>
> --
> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
