HP eld Manual page 205

Output Listings and Error Handling
installation. The procedure for creating and installing a public DLL registry file is
beyond the scope of this manual.
1555 <filename> is an archive, but it should have been a
public DLL.
Cause. You gave a -l option, to tell eld to search for a DLL based on the parameter to
the -l option. Based on that, eld decided that this was one of the standard DLLs,
found it in the standard place, and opened it. The file, however, was not a DLL, but
instead was an archive, as would be created by the "ar" tool.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. There is something wrong with your installation. Files that are not DLLs
have been placed in the location for the standard ("public") DLLs. The process of
installing the standard DLLs in the standard location is beyond the scope of this
manual.
1556 <filename> is a linkfile, but it should have been a
public DLL.
Cause. You gave a -l option, to tell eld to search for a DLL based on the parameter to
the -l option. Based on that, eld decided that this was one of the standard DLLs,
found it in the standard place, and opened it. The file, however, was not a DLL, but
instead was a linkfile, i.e., an object file created by a compilation or by running eld
with the option.
-r
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. There is something wrong with your installation. Files that are not DLLs
have been placed in the location for the standard ("public") DLLs. The process of
installing the standard DLLs in the standard location is beyond the scope of this
manual.
1557 The -set data_model neutral option is not allowed when a
program is being created.
For details on Cause and Recovery, see
Fatal error. eld stops immediately without creating an output file.
1558 The DLL <filename> contains the same DLL name as the
user library <filename> but is still being used in the link.
Cause. You are building a program, and you are using a user library. A user library is
a DLL, and like any other DLL has a "DLL name" inside it. eld has also opened
another DLL, whose filename is shown in the message, and found that it contained the
eld Functionality for 64-Bit
eld Manual—527255-009
6-95
Error Messages
on page 4-12.