Output Listings and Error Handling
eld Manual—527255-009
6-41
Error Messages
eld
will print out informational messages about all the DLLs that it used if you supply
the -verbose option. A symbol in a DLL also needs to be exported from that DLL for
eld
to find it. A symbol might also be a member of an archive, but the archive needs
to come later on the command line than the reference to the symbol to guarantee that
eld
finds the symbol in the archive. Depending on the situation, you may be able to
use the
-unres_symbols
option to specify whether
eld
should consider unresolved
references to be errors, warnings, or neither.
Cause.
You used the -y option, to ask
eld
to provide information about the symbol
mentioned in the message, and
eld
is telling you that there is a reference to that
symbol in the indicated file.
Effect.
Information (This is not indicative of a problem).
Recovery.
No action required.
Cause.
You used the -y option, to ask
eld
to provide information about the symbol
mentioned in the message, and
eld
is telling you that there is a definition of that
symbol in the indicated file.
Effect.
Information (This is not indicative of a problem).
Recovery.
No action required.
Cause.
Procedures are contained within code “sections”. The C++ compiler may
create duplicate copies of procedures, and
eld
can remove the duplicates if the
compiler gives permission. When this is done, the entire section containing the
unneeded copy of the procedure is removed. There may be references to the
procedure, but those references should be done by giving the name of the procedure,
and they will be fixed up to another copy of the procedure that was not removed. It is
also possible to make references to something within a code section by telling, not the
name of a symbol, but rather the name of the section and the offset within the section.
If there are such references into a section, the C++ compiler should not give
eld
permission to remove it, because there would be no way to fix up the references. That
is what has happened. The message tells what input file this happened in, and where
1266 <filename>: reference to <symbol name>.
1267 <filename>: definition of <symbol name>.
1273 Bad input file: relocation table entry <number> for the
<section name> section of input file <filename> is a local
reference to the <section name> section. That is an error
because the <section name> section has been omitted from the
link, since it only contains an unneeded duplicate copy of a
procedure.
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 ...