Output Listings and Error Handling
eld Manual—527255-009
6-16
Error Messages
Recovery.
You shouldn’t have a DLL whose filename ends in “.a”, so you need to fix
your build procedure.
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
was able to find and open a
file, but the file was a linkfile, such as an object file produced from a compilation, not a
DLL or archive.
eld
considers that an error, since the convention is to only use -l
options to search for DLLs and archives, not linkfiles.
Effect.
Fatal error (
eld
immediately stops without creating an output file).
Recovery.
Perhaps there is a DLL or archive that you wanted
eld
to find, but instead
eld
first found a linkfile of the same name. The rules for searching for DLLs and
archives are complicated. You may need to review all the rules by which
eld
does the
search, to determine where the DLL or archive should be placed, and how
eld
should
be told to look there. You might decide it’s easier to just put the fully qualified name of
the DLL or archive directly on the command line, without using the -l option at all. If
you really did intend to use the linkfile that was found, the easiest thing is to just put its
fully qualified name on the command line.
Cause.
eld
was searching for a DLL based on a liblist entry of some other previously
opened DLL, to indirectly bring another DLL into this link, and
eld
was able to find and
open a file, but the file was a linkfile, such as an object file produced from a
compilation, not a DLL.
Effect.
Fatal error (
eld
immediately stops without creating an output file).
Recovery.
Perhaps there is a DLL that you expected
eld
to find, but instead
eld
first
found a linkfile of the same name. The rules for searching for DLLs are complicated.
You may need to review all the rules by which
eld
does the search, to determine
where the DLL should be placed, and how
eld
should be told to look there.
Cause.
You specified the -make_implicit_lib option, to build one of the implicit DLLs
that contain the contents of system library. Such implicit DLLs may refer to other
implicit DLLs, but not to any other DLLs. However, during this link,
eld
was given
another DLL to use, where that other DLL wasn’t marked as an implicit DLL, so that’s
an error.
Effect.
Fatal error (
eld
immediately stops without creating an output file).
1100 <filename> is a linkfile, but it was found for a -l
option.
1101 <filename> is a linkfile, but it was found as an
indirect DLL.
1102 Making an implicit DLL, but <filename> isn't implicit.
Summary of Contents for eld
Page 4: ......
Page 8: ...Contents eld Manual 527255 009 iv ...
Page 12: ...What s New in This Manual eld Manual 527255 009 viii Changes to the 527255 005 Manual ...
Page 34: ...Introduction to eld eld Manual 527255 009 1 14 Example of Use ...
Page 54: ...eld Input and Output eld Manual 527255 009 2 20 Using Archives ...
Page 98: ...Other eld Processing eld Manual 527255 009 4 20 Merging Source RTDUs ...
Page 242: ...Output Listings and Error Handling eld Manual 527255 009 6 132 Glossary of Errors ...