Binding of References
eld Manual—527255-009
3-10
Using User Libraries
the
flags
field of the
.tandem_info
section. This tells
rld
how it should treat
unresolved references at runtime. Even if this loadfile is preset, and even if
rld
can
verify that the presetting is correct,
rld
will still repeat the presetting process in order
to generate the error or warning messages requested by the
RUNTIME_UNRES_CHECKING
bits if the LIC says that there were unresolved
references.
The bits set by
-set rld_unresolved
also provide defaults for how
-alf
treats
unresolved references.
There is no option for specifying the treatment of unresolved references based on a
symbol’s name.
Using User Libraries
A user library is a DLL that is found in a special way by a program.
The
-set libname
option, given to the linker when it is building a program, tells the
filename for the user library as it needs to be present at runtime.
eld
reports an error if
you give this option when not building a program. The
-set
option is described
The -
set and -change Options
on page 4-8.
The option
-libname
may be used as a synonym for
-set libname
. The specified
user library name must always have the form
$a.b.
c, i.e., a valid Guardian file name,
fully qualified up to the volume name, and not including the system name, because this
is the only type of name that will work at runtime. Note that, when running the linker on
OSS, one would need to do something such as putting the name in single quotation
marks or preceding it with a backslash to avoid the special meaning of the dollar sign
to the shell. The linker places the name specified by the
-set libname
e option into
the .
tandem_info
section of the program that it is creating. The linker also converts the
name to upper case, if not done already. On Guardian APIs, single quotes do not work
because they are not recognized by the HP Tandem Advanced Command Language
(TACL); therefore, it is not important to specify them.
The
-local_libname
option tells the linker the filename of the user library to use at
link time.
Section 3, Binding of References
explains how this user library is used,
similarly to other DLLs, when the linker is fixing up references. It is not an error if the
linker can’t find the user library, but it does mean that the linker cannot preset the
program that it is creating.
The locations of the
-set libname
and
-local_libname
options in the command
stream are irrelevant. These options may only be used when building a program.
Additional rules related to these options depend on the platform:
The PC hosted linker knows that it is building a program that uses a user library
because the
-set libname
option is used. If the
-local_libname
option is not
used then the linker can’t find the user library.
eld
reports an error if you specify
-
local_libname
without
-set libname
.
Summary of Contents for eld
Page 4: ......
Page 8: ...Contents eld Manual 527255 009 iv ...
Page 12: ...What s New in This Manual eld Manual 527255 009 viii Changes to the 527255 005 Manual ...
Page 34: ...Introduction to eld eld Manual 527255 009 1 14 Example of Use ...
Page 54: ...eld Input and Output eld Manual 527255 009 2 20 Using Archives ...
Page 98: ...Other eld Processing eld Manual 527255 009 4 20 Merging Source RTDUs ...
Page 242: ...Output Listings and Error Handling eld Manual 527255 009 6 132 Glossary of Errors ...