Intel iAPX 86 User Manual page 146

iAPX 86,88 Family Utilities LINK86 Controls and Error Messages
WARNING 64: PUBLIC SYMBOLS NOT SORTED DUE TO INSUFFICIENT
MEMORY
Meaning
The amount of
m~~mory
required to sort the public symbols for the LINK86 print file
listing is insufficient.
Cause
The number of public symbols in the input-list modules is too large for LINK86 to
sort with the available memory resources.
Effect
The LINK86 print file listing provides public symbols in the order in which they were
encountered in the input files. This condition has no effect on the correctness or
validity of the output module.
User Action
Increase the amount of available RAM or decrease the number of public symbols.
WARNING 65: ILLEGAL FIXUP: INCORRECT DECLARATION OF
EXTERNAL SYMBOL
F I L E:
pathname containing external declaration
MOD U L E:
name of module containing external declaration
S Y M B 0 L: name of external symbol
F RAM E:
identification of reference location
TAR GET:
identification of target location
Meaning
The declaration of the specified SYMBOL was found to be inconsistent with a
corresponding public symbol definition, and LINK86 could not resolve the
reference.
Cause
This condition may exist for several reasons. The modules containing the external
and public symbols may have been compiled under different translator controls
(e.g., SMALL, LARGE). In the case of assembly language programs, the SYMBOL
may be defined in a group, segment, or frame different from that in which it is
declared as external. Or an attempt has been made to access absolute entry points
from pre-located code without using the PUBLICSONLY control explicitly.
Effect
LINK86 internally converts these illegal fixups to legal formats to identify all
occurrences in a single execution. Thus the output object module may not be cor-
rect, although it will be a valid 8086 object module.
User Action
If the warning occurred because of an attempted access of absolute entry points
from pre-located code, use the PUBLICSONL Y control in conjunction with the file
that contains public definitions for those entry points. Otherwise, use the FRAME
and TARGET information given in the warning message to pinpoint the source of
the error, then correct the code.
0-25