Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ ldd(1) — Motorola System V 88k Release 4 Version 4.3

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

cc(1)

ld(1)

ldd(1)  —  USER COMMANDS

NAME

ldd − list dynamic dependencies

SYNOPSIS

ldd [−d | −r] file

DESCRIPTION

The ldd command lists the path names of all shared objects that would be loaded as a result of executing file.  If file is a valid executable but does not require any shared objects, ldd will succeed, producing no output. 

ldd may also be used to check the compatibility of file with the shared objects it uses.  It does this by optionally printing warnings for any unresolved symbol references that would occur if file were executed.  Two options govern this mode of ldd:

−d Causes ldd to check all references to data objects. 

−r Causes ldd to check references to both data objects and functions. 

Only one of the above options may be given during any single invocation of ldd. 

SEE ALSO

cc(1), ld(1). 

DIAGNOSTICS

ldd prints its record of shared object path names to stdout.  The optional list of symbol resolution problems are printed to stderr.  If file is not an executable file or cannot be opened for reading, a non-zero exit status is returned. 

NOTES

ldd doesn’t list shared objects explicitly attached via dlopen(3X). 

ldd uses the same algorithm as the dynamic linker to locate shared objects. 

  —  C Development Set

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026