ld Manual

ld Options
ld Manual—529650.001
2-13
-fl or -obey
•
an unqualified, partially qualified, or fully-qualified Guardian subvolume name
-first_l can be specified more than once in a command line or a command file.
See Searching for Archives and Libraries on page 1-19 for details about the effect of
this flag on search order.
-fl or -obey
Specifies the name of a text or command file containing ld command tokens.
file name
is an edit file (for the Guardian version of ld) or a C text file (for the OSS version of
ld).
Tokens can be separated by spaces, tabs, or ends of lines. In the OSS environment,
tokens can contain double quotation marks (") to group items into a single string,
consistent with OSS shell usage. Within the command file, two hyphens indicate a
comment that extends to the end of the current line. Command files can be nested,
and there is no limit to the depth of nesting. Recursive nesting does not cause an error
because ld does not read the same command file more than once.
You can specify -fl or -obey as often as you want in the command line or a
command file. Each specification is processed when encountered.
-include_whole or -no_include_whole
Directs ld whether to include in the loadfile all linkable archive members of the
archive libraries between this flag and the next library search control flag in the
command stream.
-include_whole
begins the linking action.
-no_include_whole
stops the linking action begun by -include_whole. Causes archive searches to
be controlled by the existence of undefined symbols. This is the default.
If -no_include_whole is specified, archives are searched in the order specified on
the command line. Symbols are marked as undefined by compilers or by the user
through -u. When an archive member is found that resolves an undefined symbol, the
member´s symbols are merged into the external symbol table for the loadfile being
created. After the merge, the undefined symbol that triggered the merge is resolved
{ -fl | -obey } file name
-include_whole | -no_include_whole