nld Manual

nld Utility
nld Manual—528272-001
2-15
Specifying SRLs
In the Guardian environment, each processor loads public SRLs at startup time from
the active SYSnn subvolume. The SYSnn subvolume, located on $SYSTEM, contains
a version of the operating system image for a particular node. A node can have more
than one SYSnn subvolume, but only one active (running) SYSnn subvolume. D42
and later product versions of nld automatically select the active SYSnn subvolume.
Previous versions of nld required you to specify the active SYSnn subvolume. (To
determine the SYSnn subvolume active on a particular node, use the Guardian
command STATUS 0,0.)
When you use nld to build a program file, nld fixes up references to the SRLs that
you have specified. You can also use nld to repeat the fix-up process on an existing
program to use a new version of an SRL or let the operating system update the
references when you execute the program.
The SRLs required to create a program file depend on the run-time resources a
program uses.
Topics:
•
Specifying SRLs on page 2-15
•
Determining Which SRLs Programs Require on page 2-16
Specifying SRLs
You can specify SRLs on the nld command line directly and with the options -l or -lib
on page 3-7. Using options to specify SRLs is a good choice for flexibility and ease of
use. A file specified in a -l or -lib option must be an SRL or an archive.
In the Guardian environment, an SRL often has a file name that starts with Z and ends
with SRL, such as ZCOBSRL.
In the OSS environment, an SRL often has a filename that starts with lib and ends
with the filename suffix .srl, such as libc.srl.
nld uses SRLs to resolve undefined symbols after all object files and archive files
specified on the command line have been used. nld uses SRLs in the order specified
on the command line and in -l or -lib options.
You can specify Guardian subvolumes or OSS directories where nld searches for
SRLs with the option -L or -libvol on page 3-8.
The -bdynamic and -bstatic flags determine if nld performs dynamic or static
linking, respectively. See Dynamic and Static Linking on page 2-27 for details.