Native Object Files - HP nld Manual

Introduction to the Utilities

Native Object Files

nld, noft, ar, and strip operate on native object files. Native object files are in
Executable and Linking Format (ELF), a standard format used for object files, with HP
extensions. For details on the structure of native object files, see
Object File Structure.
Native object files are either linkfiles or loadfiles, but not both.
Linkfiles
Loadfiles
The native compilers produce only linkfiles. The nld utility can produce either linkfiles
or loadfiles.
Linkfiles can be used as nld input or noft input.
Loadfiles can be used as nld input in several ways:
For change of attributes or stripping options
For use in determining the libraries to be used at run time
As symbol bindings.
Loadfiles can also be used as noft input.
For example:
nld newobj.o crtlmain.o zcrtlsrl
specifies a linkfile (newobj.o), a library linkfile (crtlmain.o), and a library loadfile
(zcrtlsrl). Including the library load file in the nld command makes its facilities
available at run time.
Native object files in the Guardian environment have a file code of 700.
nld
The nld utility allows you to:
Link one or more non-PIC TNS/R native object files to produce a single non-PIC
loadfile or linkfile
Modify existing loadfiles
The nld utility runs in the following environments:
Guardian
OSS
Windows NT, Windows 2000, and Windows XP, by means of the HP Enterprise
Toolkit—NonStop Edition (ETK), which is based on Microsoft Visual Studio .NET
Can Be Linked to Produce a Loadfile
Yes
No
nld and noft Manual—520384-003
Can Be Loaded for Execution
1 -2
Native Object Files
Section 8, Native
No
Yes