Input Object Files - HP eld Manual

eld Input and Output
whether entries already in the registry overlap. Whenever a DLL registry is updated by
the linker and the DLL had previously been mentioned in the file, the old entry is
replaced by the new one so that the DLL is not mentioned more than once in the
registry.
A new registry file is always created, mostly following the same rules as given earlier in
The Creation of Output Object Files
One difference is that the name of the work file is ZLDARnnn rather than ZLDAFnnn
and the name of the intermediate file, if desired, is specified by the -temp_r option
rather than the -temp_o option. Also, there is a -must_use_rname option, instead
of -must_use_oname.
Also, if the linker cannot create a new DLL successfully (i.e., terminates in error before
that point), then the linker does not modify the existing DLL registry. However, once the
linker has succeeded in creating its output DLL, the linker will not consider any
subsequent problems with the DLL registry to be errors. If the linker cannot update the
registry as desired, that will only be reported as a warning.
Note that the linker must first read an existing private DLL registry before it writes out a
new version of it. As explained above, if the linker can't read it,
So, the -temp_r and -must_use_rname options are only relevant to situations
where the linker had permission to read the existing private DLL registry, but not delete
it.

Input Object Files

TNS/E linkfiles have no object file version number associated with them.
Loadfiles have a version number stored in the .tandem_info section, placed there by
the linker. At the present time the version number is zero. When the linker reads a
loadfile for any reason the linker considers it an error if the loadfile contains a version
number different from zero. This version checking is disabled by the -
no_version_check option.
On the Guardian platform the linker does not check that object files have the proper file
code. If the file was not the right kind of file, the linker would soon realize it in some
other way.
How the Linker Finds Its Input Files and Creates the .liblist
Section
The linker locates linkfiles, archives, DLLs, and import libraries based on items
specified in its command stream. This section provides the rules for doing this. As part
of this process, the linker also creates the .liblist section for its output loadfile.
See Using Archives
files to use from an archive.
on page 2-5.
on page 2-16 for an explanation of how the linker decides which
eld Manual—527255-009
2-12
Input Object Files
reports an error.
eld