Output Listings and Error Handling
eld Manual—527255-009
6-15
Error Messages
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
cound not find that DLL or
archive.
Effect.
Fatal error (
eld
immediately stops without creating an output file).
Recovery.
The rules for searching for DLLs and archives are complicated. For
example, the DLL or archive may be present in your current location (Guardian
subvolume, OSS directory, or PC folder), but that is not a place where
eld
looks by
default. You can tell
eld
to look there with the appropriate -L option. More generally,
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. You might also decide
that you didn’t need that DLL or archive anyway. Or, you may be specifying everything
as you should, to tell
eld
how to find the DLL or archive in the location you expect it to
be, but the DLL or archive is not there, or you don’t have permission to read it.
Cause.
eld
has found a file, specified on the command line, possibly through a -l
option, and opened it, and found that it was a DLL, but the -b static option was in effect
at this point on the command line, which says that it is an error if
eld
finds a DLL as
opposed to an archive.
Effect.
Fatal error (
eld
immediately stops without creating an output file).
Recovery.
If you really don’t want to find a DLL at this point on the command line,
possibly through a -l option, then you need to figure out why
eld
did find a DLL, rather
than an archive. If the DLL 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 archive directly on the
command line, without using the -l option at all. On the other hand, if you really do
want to find a DLL, then don’t specify the -b static option, or at least not at this place on
the command line.
Cause.
eld
has found a file, specified on the command line, and opened it, and found
that it was a DLL, but the name of the file ends in “.a”.
eld
considers that an error,
since the convention is to use such filenames for achives rather than DLLs.
Effect.
Fatal error (
eld
immediately stops without creating an output file).
1083 Cannot find <name>.
1098 <filename> is a DLL, but the -b static option was in
effect.
1099 <filename> is a DLL, but the filename ends in '.a'.
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 ...