Open System Services Shell and Utilities Reference Manual (G06.29+, H06.08+, J06.03+)

User Commands (d - f) eld(1)
• 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 linkfiles 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 filename is objecta from the
linkfile named objectb.
3. The following example:
eld obj1.o obj2.o -ul -o lib
links the linkfiles 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 linkfiles named obj3.o and obj4.o together into a loadfile 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 linkfiles named obj6.o and obj7.o into a loadfile named prog that you intend to
run as a Guardian process.
6. The following example:
eld -change highpin off exeobj
changes the value of the HIGHPIN attribute in the loadfile exeobj to OFF.
7. The following is an example of a valid private DLL registry file:
-- Specify the overall domain area that DLLs
-- can reside in (high to low)
-dllarea 0x68000000 0x60000000
-- Set up two DLLs that overlap each other
-- (one entry manually inserted)
-range $SYSTEM.ZDLL.ABC 0x67D00000 0x100000
-range /bin/usr/don/libmy.lib 0x67D00000 0x300000
527188-021 Hewlett-Packard Company 3−79