Open System Services Shell and Utilities Reference Manual (G06.28+, H06.05+)

eld(1) OSS Shell and Utilities Reference Manual
If you are creating an import library to represent a set of implicit DLLs, (all of the
specified DLLs have the implicit bit set in their headers), then you can also use a
private DLL registry. The value specified for filename9 is used as the entry name
for the implicit libraries in the private DLL registry.
To use this flag, at least one DLL file must be specified somewhere in the com-
mand line or obey file.
-must_preset Tells eld to treat the situation as an error when presetting fails. If this flag is omit-
ted, the linker continues.
-must_use_iname
Tells eld to treat the situation as an error when it cannot delete an existing file to
create an import library file of the same name.
The default behavior is to issue a warning message.
-must_use_oname
Tells eld to treat the situation as an error when it cannot delete an existing file to
create the new object file created from a set of linkfiles, or the output file of the
-alf or -strip flags, with the same name.
The default behavior is to issue a warning message.
-must_use_rname
Tells eld to treat the situation as an error when it cannot delete an existing file to
create a private DLL registry file of the same name.
The default behavior is to issue a warning message.
-no_optional_lib | -optional_lib
Specifies whether a DLL specified in the command line or obey file should be con-
sidered optional when creating a loadfile.
When -no_optional_lib behavior is in effect, any specified library is included in
the .liblist section of the loadfile being created. When -optional_lib behavior is in
effect, a specified library can be omitted from the .liblist section of the loadfile
being created if omitting it would not affect how symbolic references are resolved.
For example, a DLL can be omitted when all of the following are true:
• The DDL does not export symbols that resolve any references in the
loadfile being created
• The DLL does not cause other DLLs to be added to the search list, where
the other DLLs resolve references in the loadfile being created
• The DLL does not cause other DLLs to be placed in a different order
within the search list when those DLLs resolve references in the loadfile
being created
These flags can be specified as many times as needed in the command line or obey
file. Providing either flag overrides the current setting, so that the linker actions
can be controlled on a library-by-library basis.
If a library is specified more than once, eld uses the specification in effect for the
first instance of the DLL that it processes and ignores the other specifications.
The default behavior is -no_optional_lib.
3−68 Hewlett-Packard Company 527188-007