eld Manual

Output Listings and Error Handling
eld Manual—527255-009
6-17
Error Messages
Recovery. If you specified the -make_implicit_lib option for no reason, stop doing it.
Otherwise, this indicates some problem with the procedure for building and installing
the NSK operating system, which is beyond the scope of this document.
Cause. eld was searching for a DLL based on a liblist entry of some other already
opened DLL, to indirectly bring another DLL into this link, and eld was able to find and
open a file, but the file was an archive, 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 an archive 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. eld has found a file, specified on the command line, possibly through a -l
option, and opened it, and found that it was an archive, but the -b dllsonly option was
in effect at this point on the command line, which says that it is an error if eld finds an
archive as opposed to a DLL.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery. If you really don’t want to find an archive at this point on the command line,
then you need to figure out why eld did find an archive, rather than a DLL. If the
archive was found through a -l option that did a search, you may need to review all the
rules for how eld does that search, which is complicated. You might decide it’s easier
to just put the fully qualified name of the DLL directly on the command line, without
using the -l option at all. On the other hand, if you really do want to find an archive,
then don’t specify the -b dllsonly option, or at least not at this place on the command
line.
Cause. eld has found a file, specified on the command line, possibly through a -l
option, and opened it, and found that it was an archvie, but the name of the file ends in
“.so”. eld considers that an error, since the convention is to use such filenames for
DLLs rather than archives.
Effect. Fatal error (eld immediately stops without creating an output file).
Recovery
. You shouldn’t have an archive whose filename ends in “.so”, so you need
to fix your build procedure.
1103 <filename> is an archive, but it was found as an
indirect DLL.
1104 <filename> is an archive, but the -b dllsonly option was
in effect.
1105 <filename> is an archive, but the filename ends '.so'.