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

eld(1) OSS Shell and Utilities Reference Manual
-y symbol_name5
Tells eld to report which linkfiles define and use the symbol symbol_name5. The
linkfiles are listed in the order encountered.
This information can be useful if a previous eld command produced error or warn-
ing messages about a symbol being either undefined or defined more than once.
Operands
filename17 Specifies one or more files for the eld utility to process.
The files used can be:
• Linkfiles that eld will combine into a new linkfile or loadfile
• DLLs that eld will use to resolve references in a new loadfile that it is
creating, or in a loadfile being processed by the -alf flag
• DLLs that are input to the -make_import_lib flag
This operand is required for all flags except the alf, -change, and -strip flags.
DESCRIPTION
The eld utility links one or more TNS/E native position-independent code (PIC) linkfiles to pro-
duce an executable or nonexecutable native PIC loadfile. You can also modify existing loadfiles
using eld. You can invoke eld directly or, if you are creating a C or C++ program, you can use the
c89 or the c99 utility to invoke eld automatically for you.
Flag Names
Names of flags obey the following rules:
• If a flag name is one letter and the flag takes a value, the space between the flag name and
the value is optional
• Flag names and keyword values are not case sensitive, except for the separate -l and -L
flags
If no flags or operands are used, the eld command displays usage help in its output listing.
Input Files
eld cannot process a linkfile that contains a code section larger than 16 megabytes. This size res-
triction is imposed by the Itanium standard.
Output Files
eld creates loadfiles on the host platform with an OSS file mode of 777 (rwxrwxrwx), which is
then ANDed with the umask value of the user creating the file. eld creates all other object files
with an OSS file mode of 666 (r-xr-xr-x), which is then ANDed with the umask value of the user
creating the file.
Any text file created by ld in the Guardian file system has a file code of 180. You can use the
CTOEDIT utility to convert such files to code 101 files for viewing with TEDIT.
Loadfiles or linkfiles created in the Guardian file system have a Guardian file code of 800.
Maintaining DLL Registry Files
A DLL registry file is a C text file that contains attribute information associated with a set of
DLLs. The file contains:
• An optional -dllarea specification that defines the first and last addresses of the virtual
memory area that is to be assigned to all DLLs. This specification has the form:
-dllarea dllarea_start_address dllarea_end_address
3−76 Hewlett-Packard Company 527188-021