rld Manual

RLD Overview
RLD Manual—528857-006
1-7
Load-time Path Specifications
Default locations for a 64-bit process:
On OSS: /lib64, /usr/lib64, /usr/local/lib64, /lib, /usr/lib, /usr/local/lib,
/G/SYSTEM/YDLL, /G/SYSTEM/ZDLL, in that order
The linker, can place either or both of two path lists in the loadfile, using the following
options:

-RLD_L <path>[:<path>]…
This option specifies one or more places for the runtime loader to look for
libraries.

-RLD_first_L <path>[:<path>]…
This option is like -RLD_L except that it specifies places to look first (before the
public libraries). The resulting path list is placed as a separate rpath_first item
in the ".dynamic" section of the loadfile.
The loader uses these path names in the target environment. Invalid or absent path
locations are ignored, so the list can contain a mix of Guardian subvolumes and OSS
paths.
Load-time Path Specifications
At runtime, users can modify the path list specified at link time.
For OSS, the load-time path lists can be specified using the following environment
variables:

_RLD_LIB_PATH=<path>[:<path>]…
The specified paths are to be searched before the default locations.

_RLD_FIRST_LIB_PATH=<path>[:<path>]…
The specified paths are to be searched before the public libraries and linker-
specified places.
For example:
export_RLD_FIRST_LIB_PATH=/G/data05/testdlls
For Guardian only, =_RLD_LIB_PATH and =_RLD_FIRST_LIB_PATH (DEFINEs of
CLASS SEARCH; for format details, see the Guardian Procedure Calls Reference
Manual) serve the same purpose as the two OSS environment variables. On OSS, the
Guardian DEFINEs are ignored. DEFINES of CLASS SEARCH have several
attributes: SUBVOL0, RELSUBVOL0, SUBVOL1, RELSUBVOL1, SUBVOL3,
RELSUBVOL3... Each attribute can hold a subvolume name or a parenthesized
comma separated list of subvolume names. Incompletely qualified names are qualified
by defaults when assigned to the SUBVOLn attributes but are left unresolved in the
RELSUBVOLn attributes. The search list consists of all the subvolumes specified in the
above order. If any attribute is a list, the search order is from left to right within the list.
For example: