4.3BSD-Tahoe/usr/man/cat1/ld.0
LD(1) UNIX Programmer's Manual LD(1)
NNAAMMEE
ld - link editor
SSYYNNOOPPSSIISS
lldd [ option ] ... file ...
DDEESSCCRRIIPPTTIIOONN
_L_d combines several object programs into one, resolves
external references, and searches libraries. In the sim-
plest case several object _f_i_l_e_s are given, and _l_d combines
them, producing an object module which can be either exe-
cuted or become the input for a further _l_d run. (In the
latter case, the --rr option must be given to preserve the
relocation bits.) The output of _l_d is left on aa..oouutt. This
file is made executable only if no errors occurred during
the load.
The argument routines are concatenated in the order speci-
fied. The entry point of the output is the beginning of the
first routine (unless the --ee option is specified).
If any argument is a library, it is searched exactly once at
the point it is encountered in the argument list. Only
those routines defining an unresolved external reference are
loaded. If a routine from a library references another rou-
tine in the library, and the library has not been processed
by _r_a_n_l_i_b(1), the referenced routine must appear after the
referencing routine in the library. Thus the order of pro-
grams within libraries may be important. The first member
of a library should be a file named `__.SYMDEF', which is
understood to be a dictionary for the library as produced by
_r_a_n_l_i_b(1); the dictionary is searched iteratively to satisfy
as many references as possible.
The symbols `_etext', `_edata' and `_end' (`etext', `edata'
and `end' in C) are reserved, and if referred to, are set to
the first location above the program, the first location
above initialized data, and the first location above all
data respectively. It is erroneous to define these symbols.
_L_d understands several options. Except for --ll, they should
appear before the file names.
--AA This option specifies incremental loading, i.e. link-
ing is to be done in a manner so that the resulting
object may be read into an already executing program.
The next argument is the name of a file whose symbol
table will be taken as a basis on which to define addi-
tional symbols. Only newly linked material will be
entered into the text and data portions of aa..oouutt,, but
the new symbol table will reflect every symbol defined
before and after the incremental load. This argument
Printed 7/9/88 May 8, 1986 1
LD(1) UNIX Programmer's Manual LD(1)
must appear before any other object file in the argu-
ment list. The --TT option may be used as well, and will
be taken to mean that the newly linked segment will
commence at the corresponding address (which must be a
multiple of 1024). The default value is the old value
of _end.
--DD Take the next argument as a hexadecimal number and pad
the data segment with zero bytes to the indicated
length.
--dd Force definition of common storage even if the --rr flag
is present.
--ee The following argument is taken to be the name of the
entry point of the loaded program; location 0 is the
default.
--LL_d_i_r
Add _d_i_r to the list of directories in which libraries
are searched for. Directories specified with --LL are
searched before the standard directories.
--ll_x This option is an abbreviation for the library name
`lib_x.a', where _x is a string. _L_d searches for
libraries first in any directories specified with --LL
options, then in the standard directories `/lib',
`/usr/lib', and `/usr/local/lib'. A library is
searched when its name is encountered, so the placement
of a --ll is significant.
--MM produce a primitive load map, listing the names of the
files which will be loaded.
--NN Do not make the text portion read only or sharable.
(Use "magic number" 0407.)
--nn Arrange (by giving the output file a 0410 "magic
number") that when the output file is executed, the
text portion will be read-only and shared among all
users executing the file. This involves moving the
data areas up to the first possible 1024 byte boundary
following the end of the text.
--oo The _n_a_m_e argument after --oo is used as the name of the
_l_d output file, instead of aa..oouutt.
--rr Generate relocation bits in the output file so that it
can be the subject of another _l_d run. This flag also
prevents final definitions from being given to common
symbols, and suppresses the `undefined symbol' diagnos-
tics.
Printed 7/9/88 May 8, 1986 2
LD(1) UNIX Programmer's Manual LD(1)
--SS `Strip' the output by removing all symbols except
locals and globals.
--ss `Strip' the output, that is, remove the symbol table
and relocation bits to save space (but impair the use-
fulness of the debuggers). This information can also
be removed by _s_t_r_i_p(1).
--TT The next argument is a hexadecimal number which sets
the text segment origin. The default origin is 0.
--tt ("trace") Print the name of each file as it is pro-
cessed.
--uu Take the following argument as a symbol and enter it as
undefined in the symbol table. This is useful for
loading wholly from a library, since initially the sym-
bol table is empty and an unresolved reference is
needed to force the loading of the first routine.
--XX Save local symbols except for those whose names begin
with `L'. This option is used by _c_c(1) to discard
internally-generated labels while retaining symbols
local to routines.
--xx Do not preserve local (non-.globl) symbols in the out-
put symbol table; only enter external symbols. This
option saves some space in the output file.
--yy_s_y_m
Indicate each file in which _s_y_m appears, its type and
whether the file defines or references it. Many such
options may be given to trace many symbols. (It is
usually necessary to begin _s_y_m with an `_', as external
C, FORTRAN and Pascal variables begin with under-
scores.)
--zz Arrange for the process to be loaded on demand from the
resulting executable file (413 format) rather than
preloaded. This is the default. Results in a 1024
byte header on the output file followed by a text and
data segment each of which have size a multiple of 1024
bytes (being padded out with nulls in the file if
necessary). With this format the first few BSS segment
symbols may actually appear (from the output of
_s_i_z_e(1)) to live in the data segment; this to avoid
wasting the space resulting from data segment size
roundup.
FFIILLEESS
/lib/lib*.a libraries
/usr/lib/lib*.a more libraries
Printed 7/9/88 May 8, 1986 3
LD(1) UNIX Programmer's Manual LD(1)
/usr/local/lib/lib*.a still more libraries
a.out output file
SSEEEE AALLSSOO
as(1), ar(1), cc(1), ranlib(1)
BBUUGGSS
There is no way to force data to be page aligned. _L_d pads
images which are to be demand loaded from the file system to
the next page boundary to avoid a bug in the system.
Printed 7/9/88 May 8, 1986 4