ldd(1)
NAME
ldd − list dynamic dependencies of executable files or shared objects
SYNOPSIS
ldd [ −d | −r ] filename...
DESCRIPTION
ldd lists the dynamic dependencies of executable files or shared objects. If filename is an executable file, ldd lists the pathnames of all shared objects that would be loaded as a result of executing filename.
If filename is a shared object, ldd lists the pathnames of all shared objects that would be loaded as a result of loading filename. ldd requires shared objects to have execute permission.
ldd processes its input one file at a time. For each input file ldd does one of the following:
Lists the object dependencies if they exist.
Succeeds quietly if dependencies do not exit.
Prints an error message if processing fails.
OPTIONS
ldd can also check the compatibility of filename with the shared objects it uses. The following options indicate to ldd to print warnings for any unresolved symbol references that would occur if filename were executed.
−d Check references to data objects.
−r Check references to both data objects and functions.
Only one of the above options may be given during any single invocation of ldd.
FILES
/usr/lib/lddstub Fake executable loaded to check the dependencies of shared objects.
SEE ALSO
SunOS 5.1 Linker and Libraries Manual
DIAGNOSTICS
ldd prints the record of shared object path names to stdout. The optional list of symbol resolution problems are printed to stderr. If filename is not an executable file or a shared object, or if it cannot be opened for reading, a non-zero exit status is returned.
NOTES
ldd does not list shared objects explicitly attached using dlopen(3X).
Using the −d or −r option with shared objects can give misleading results. ldd does a “worst case” analysis of the shared objects. However, in practice some or all of the symbols reported as unresolved can be resolved by the executable file referencing the shared object.
ldd uses the same algorithm as the dynamic linker to locate shared objects.
SunOS 5.1/SPARC — Last change: 5 Jul 1990