eld Manual

Table Of Contents
Output Listings and Error Handling
eld Manual527255-009
6-58
Error Messages
Cause. You gave the -instance_data option more than once on the command line,
and you specified a different value for it each time. You can give this option more than
once, but only if you specify the same value each time.
Effect. Fatal error (eld immediately stops without modifying the file).
Recovery. The -instance_data option is a speical option that should only be used
when you know why you are using it. If you need to use it, decide which value you
need to specify, and specify only that value.
Cause. You specified the -check_registry or -update_registry option, and the file that
you specified as the private DLL registry does exist, but you don’t have permission to
open it for reading. The problem is not that the file was in use by another link, because
eld would give a different message about that.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. Check that you spelled the name correctly and that you do have
permission to read it.
Cause. You specified the -make_import_lib option, which means that you are either
making an import library to represent a single DLL, or that you are making the zimpimp
file that represents all the implicit DLLs that constitute system library. You also
specified either the -temp_r, -must_use_rname, -check_registry, -update_registry, or -
t option, and these are options that are allowed when you are creating the zimpimp
file, but not when creating other kinds of import libraries. On the other hand, you also
put the name of a DLL on the command line, and this DLL isn’t an implicit DLL, but
only implicit DLLs are allowed when you are creating the zimpimp file. So, this set of
conditions is inconsistent.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If your intention is to create a zimpimp file, then the other filenames on the
command line should be implicit DLLs. If you are trying to create an import library to
represent a single (ordinary) DLL, then don’t use the option that was mentioned in the
message. If you are not trying to create an import library, don’t specify the -
make_import_lib option.
1337 Multiple values specified for the -instance_data option.
1338 Error opening DLL registry <filename>.
1339 The <option name> option would be allowed if you were
making a zimpimp file, but because the DLL on the command
line isn't an implicit DLL, you are instead making an
ordinary import library, in which case this option isn't
allowed.