Интерактивная система просмотра системных руководств (man-ов)
ild (1)
>> ild (1) ( Solaris man: Команды и прикладные программы пользовательского уровня )
NAME
ild - incremental link editor (ild) for object files
SYNOPSIS
ild [ -a ] [ -i ] [ -m ] [ -s ] [ -t ]
[ -V ] [ -B dynamic|static ] [ -d y|n ]
[ -e epsym ] [ -I name ] [ -L path ] [ -l x ]
[ -o outfile ] [ -Q y|n ] [ -R path ] [ -u symname ]
[ -Y P,dirlist ]
[ -z allextract|defaultextract|weakextract ]
[ -z defs|nodefs ] [ -z i_dryrun ]
[ -z i_full ] [ -z i_noincr ] [ -z i_quiet ]
[ -z i_verbose ]
filename ...
DESCRIPTION
iilldd links incrementally so you can insert modified object
code into an executable built previously. The time required
to link depends upon the amount of code changed. Linking
your application on every build does not require the same
amount of time; small changes in code can be linked very
quickly.
The iilldd command combines relocatable object files, performs
relocation, and resolves external symbols. iilldd operates in
two modes, static or dynamic, as governed by the --dd option.
In static mode, --ddnn, relocatable object files given as argu-
ments are combined to produce an executable object file. In
dynamic mode, --ddyy, the default, relocatable object files
given as arguments are combined to produce an executable
object file that will be linked at execution with any shared
object files given as arguments. In all cases, the output
of iilldd is left in aa..oouutt by default.
If any argument is a library, it is searched exactly once at
the point it is encountered in the argument list. The
library may be either a relocatable archive or a shared
object. For an archive library, only those routines defin-
ing an unresolved external reference are loaded. The
archive library symbol table (see ar(4)) is searched sequen-
tially with as many passes as are necessary to resolve
external references that can be satisfied by library
members. Thus, the ordering of members in the library is
functionally unimportant, unless there exist multiple
library members defining the same external symbol. A shared
object consists of a single entity all of whose references
must be resolved within the executable being built or within
other shared objects with which it is linked.
The compilation system options that control whether a link
step is performed by iilldd or lldd are: -xildon, always use iilldd;
-xildoff, always use lldd (if -xildon and -xildoff are both
present, the last governs); -g, when neither -xildoff or -G
are given, use iilldd for link-only invocations (no source
files on the command line); -G, prevents the -g option from
having any effect on linker selection.
Note: Both -g and -G have other meanings that are documented
as part of the compilation systems.
When you use the -g option to invoke iilldd, and you have the
default Makefile structure (which includes compile-time
options such as -g on the command line for the link step),
you use iilldd automatically when doing development.
If iilldd determines that an iilldd option is unimplemented (see
NOTES), iilldd directly invokes //uussrr//ccssss//bbiinn//lldd to perform the
link.
OVERVIEW OF INCREMENTAL LINKING
In incremental mode, the initial link causes the various
text, data, bss, exception table sections, etc., to be pad-
ded with additional space for future expansion. Addition-
ally, all relocation records, rraannlliibb indices, and the global
symbol table are saved by ild in the executable file.
On subsequent incremental links, iilldd uses timestamps to dis-
cover which object files have changed and patches the
changed object code into a previously built executable.
That is, the previous versions of the object files are
invalidated and the new object files are loaded into the pad
sections of the executable. All references to symbols in
invalidated object files are patched to point to the correct
new object files.
OPTIONS
--aa In static mode only, produce an executable
object file; give errors for undefined refer-
ences. This is the default behavior for static
mode.
--ii Ignore LD_LIBRARY_PATH setting. This option is
useful when an LD_LIBRARY_PATH setting is in
effect to influence the runtime library search,
which would interfere with the link editing
being performed. (This also applies to the set-
ting of LD_LIBRARY_PATH_64 )
--mm Produce a memory map or listing of the
input/output sections on the standard output.
(See BUGS.)
--ss Strip symbolic information from the output file.
Any debugging information, that is .debug,
.line, and .stab sections and their associated
relocation entries, will be removed. Except for
relocatable files or shared objects, the symbol
table and string table sections will also be
removed from the output object file.
--tt Turn off the warning about multiply defined sym-
bols that are not the same size.
--VV Output a message giving information about the
version of iilldd being used.
--BB ddyynnaammiicc|ssttaattiicc
Options governing library inclusion. --BBddyynnaammiicc
is valid in dynamic mode only. These options
may be specified any number of times on the com-
mand line as toggles: if the --BBssttaattiicc option is
given, no shared objects will be accepted until
--BBddyynnaammiicc is seen. See also the --ll option.
--dd yy|nn When --ddyy, the default, is specified, iilldd uses
dynamic linking; when --ddnn is specified, iilldd uses
static linking. Also see --BB ddyynnaammiicc|ssttaattiicc.
--ee epsym Set the entry point address for the output file
to be that of the symbol epsym.
--II name When building an executable, use name as the
path name of the interpreter to be written into
the program header. The default in static mode
is no interpreter; in dynamic mode, the default
is the name of the runtime linker,
//uussrr//lliibb//lldd..ssoo..11. Either case may be overridden
by --IIname. eexxeecc will load this interpreter when
it loads the aa..oouutt and will pass control to the
interpreter rather than to the aa..oouutt directly.
--LL path Add path to the library search directories. iilldd
searches for libraries first in any directories
specified by the --LL options, and then in the
standard directories. This option is useful
only if it precedes the --ll options to which it
applies on the command line. The environment
variables LD_LIBRARY_PATH and LD_LIBRARY_PATH_64
may be used to supplement the library search
path (see ENVIRONMENT below).
--ll x Search a library lliibbx..ssoo or lliibbx..aa, the conven-
tional names for shared object and archive
libraries, respectively. In dynamic mode,
unless the --BBssttaattiicc option is in effect, iilldd
searches each directory specified in the library
search path for a file lliibbx..ssoo or lliibbx..aa. The
directory search stops at the first directory
containing either. iilldd chooses the file ending
in ..ssoo if --