Open System Services Shell and Utilities Reference Manual (G06.27+, H06.04+)

User Commands (d - f) eld(1)
4. the directory containing the loadle (which might be a program or a DLL) **
5. the les specied by L
6. locations specied by the current -rld_l or -rpath ag
7. default locations:
/lib:/usr/lib:/usr/local/lib:/G/SYSTEM/ZDLL * **
The value of the COMP_ROOT environment variable is added to the beginning of /lib,
/usr/lib, and /usr/local/lib. By default, the value of COMP_ROOT is null in the OSS
environment.
The steps marked by an asterisk (*) are skipped when the -nostdlib or -no_stdlib ag is in effect.
When the -limit_runtime_paths
ag has been used for the loadle, the following are omitted
from rlds search:
The steps marked by two asterisks (**) in the previously described search order
Paths indicated by the TACL DEFINEs _RLD_FIRST_LIB_PATH and
_RLD_LIB_PATH.
For More Information
eld is not an interactive tool like Binder. For more information on using eld, see the eld Manual.
For more information on run-time library use, see the rld Manual.
EXAMPLES
1. The following example:
eld objecta objectb -o objectc
links together the input linkles named objecta and objectb to create a program named
objectc.
2. The following example:
eld -dll -o objecta objectb
creates a DLL whose DLL name is objecta and whose lename is objecta from the
linkle named objectb.
3. The following example:
eld obj1.o obj2.o -ul -o lib
links the linkles named obj1.o and obj2.o together into a user library named lib.
4. The following example:
eld obj3.o obj4.o -o prog -libname \$A.B.C
links linkles named obj3.o and obj4.o together into a loadle named prog. When prog
runs, it has a user library with the Guardian name $A.B.C. The backslash (\) prevents the
shell from misinterpreting the dollar sign ($).
5. The following example:
eld obj6.o obj7.o -o prog -set systype guardian
links the linkles named obj6.o and obj7.o into a loadle named prog that you intend to
run as a Guardian process.
527188-004 Hewlett-Packard Company 377