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

eld(1) OSS Shell and Utilities Reference Manual
at the next 64K boundary after the end of the text segment. The -d flag can be
used to place the data segment at some other address, rather than directly after its
text segment. You should do this only if there is a special need to do so; HP
recommends using the default placement whenever possible.
You cannot use this flag if you use the -check_registry or -update_registry flags.
-data_resident Specifies that the loadfile being created can contain both resident code and vari-
able data.
When you create a loadfile with both resident code and variable data, you must
either specify the -data_resident flag or the -instance_data flag with one of the
values data2, data2hidden,ordata2protected. Otherwise, an error occurs and
no loadfile is created.
When you use the -data_resident flag, eld also sets the
EF_TANDEM_DATA_RESIDENT
bit in the e_flags field of the file header.
This is a special flag that can be used when building a proto-process.
{-dllname | -soname } DLL_name
Tells eld the DLL name to store in the DLL being created. When this DLL is
specified in the link step of another loadfile, the DLL name stored in this DLL is
placed in the libList of the loadfile for later use by rld or the eld -alf flag when
searching for DLLs.
If the DLL being created will reside in the Guardian file system, DLL_name must
conform to Guardian filename rules. If the DLL being created will reside in the
OSS file system, DLL_name must conform to OSS pathname rules. If you want
the DLL to be able to reside in either file system, use an unqualified Guardian file
identifier as both its DLL_name and its OSS filename.
If you specify both a DLL_name and the -o flag, the output loadfile file name is
determined by the -o specification and DLL_name is saved in the DLL being
created. HP recommends that you do not do this unless there is a specific need to
do so; making DLL_name differ from the DLL’s file name can cause problems,
especially when the DLL needs to reside in both the OSS and Guardian file sys-
tems.
If you specify DLL_name but do not use the -o flag, the output loadfile file name
uses the DLL_name value.
If you do not specify DLL_name but use the -o flag, the output loadfile unqualified
filename is used as the DLL name stored in the DLL being created; that is, only
the unqualified part (rightmost part) of the output file pathname is used.
If you omit both a DLL_name and the -o flag, the output loadfile filename and
DLL_name in the libList both default to a.out. HP recommends against using this
default value because it is too generic to allow for proper administration of files.
-e symbol_name1
Specifies a function identifier. The specified function is the entry point, that is, the
point at which to begin executing the program when the program is loaded.
You should use this flag only when linking a program that will execute without
standard run-time support facilities and without linking a module such as
CCPLMAIN (in the Guardian file system) or ccplmain.o (in the OSS file system)
that contains a function with the MAIN attribute. Do not use this flag for libraries.
3−62 Hewlett-Packard Company 527188-003