eld Manual

Output Listings and Error Handling
eld Manual—527255-009
6-124
Error Messages
Recovery. If you really wanted to use a name that begins with an equal sign in this
context, you can’t. On the PC or OSS, the Guardian DEFINE mechanism is not
present, so you need to directly specify the intended filename.
Cause. Multiple global symbols are present in the link files. The common data file is
larger in size than the defined data file.
Effect. The application might not work because of possible data loss.
Recovery. Ensure that the application does not include duplicate global symbols of
different sizes.
Cause. The contents of the specified input filename might not be correct. As a result,
eld does not process the file.
Effect. Fatal error. eld stops immediately without creating an output file.
Recovery. Contact your HP representative.
Cause. The contents of the specified input filename might not be correct. As a result,
eld does not process the file.
Effect. Fatal error. eld stops immediately without creating an output file.
Recovery. Contact your HP representative.
For details on Cause and Recovery, see eld Functionality for 64-Bit
on page 4-12.
Effect. Fatal error. eld stops immediately without creating an output file..
For details on Cause and Recovery, see eld Functionality for 64-Bit
on page 4-12.
Effect. Fatal error. eld stops immediately without creating an output file.
1657 Common data is larger in size, possible loss of data.
1659 < filename>: the resident procedure <procedure name> is
in <section name>, which is not a resident code section.
1660 <filename>: the procedure <procedure name> is in
<section name>, which is a resident code section, but is not
a RESIDENT procedure.
1665 The -set data_model neutral option is not allowed when a
program is being created.
1666 Bad value given for the -change data_model option; the
only allowed value is ‘neutral’.
1667 The -change data_model option is not allowed because the
existing file <filename> is a program.