HP eld Manual page 124

Output Listings and Error Handling
Recovery. If there already was a file with the same name as the file you wanted to
create, and you didn't have permission to delete it, either find some other way to delete
that old file, or specify a different filename for the import library that you want to create.
If there was no file of that name already, and you are not able to rename a file to
another name in the same location (Guardian subvolume, OSS directory, or PC folder),
that is an operating system question that is beyond the scope of this document.
1065 Floating point type inconsistency among input linkfiles.
File <filename> specifies 'tandem'.
specifies 'ieee'.
Cause. As shown in the message, one of the input object files said it wanted the
"Tandem" type of floating point, and another one specified "IEEE", and you didn't
specify which one you wanted to take precedence on the eld command line. That is
an error.
Effect. Error (The linker cannot do what was requested of it and will eventually stop,
but may continue for the purpose of detecting additional errors before stopping).
Recovery. If these files really do need to use the respective types of floating point,
then that is impossible, and you'll have to change your source code to use one type of
floating point consistently. More often, one or both files specifies a floating point type
unnecessarily, because the compilers may do that by default. In that case, use the -set
floattype option to specify the type of floating point that eld should assume is really
needed, or "neutral" if neither type is required.
1081 Cannot open <filename>: <reason>.
Cause. A filename was specified directly on the command line, for eld to open, but
either that file doesn't exist or you don't have permission to read it.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Check that you really intended to specify a file of the indicated name, that
you spelled it correctly, and that you do have permission to read it.
1082 Cannot find <name>.
Cause. You specified the -l option, to tell eld to search for a DLL or archive based on
the string given as the parameter to the -l option, and eld could not find that DLL or
archive, and you also specified the -allow_missing_libs option, to say that it was not an
error if a DLL could not be found.
Effect. Information (This is not indicative of a problem).
Recovery. No action required (assuming you did specify the -allow_missing_libs
option on purpose, for a good reason).
eld Manual—527255-009
6-14
File <filename>
Error Messages