B
LINKER ERROR MESSAGES
1 Introduction
Error and warning messages of the linker start with a letter followed
by a number and an informational text. The error letter indicates the error
type:
2 Warnings (W)
W 100: Cannot create map file filename, turned
off -M option
The given file could not be created.
W 101: Illegal filename (filename) detected
A filename with an illegal extension was detected.
W 102: Incomplete type specification, type index = Thexnumber
An unknown type reference. Arises if a pointer to an unspecified structure is defined.
W 103: Object name (name) differs from filename
Internal name of object file not the same as the filename. The file
was probably renamed.
W 104: '-o filename' option overwrites previous
'-o filename'
Second -o option encountered, previous name is lost.
W 105: No object files found
No files where specified at the invocation.
W 106: No search path for system libraries. Use -L or env "variable"
System library files (those given with the -l option)
must have a search path, either supplied by means of the environment, or by means of
the option -L.
W 108: Illegal option: option (-H or -\? for help)
An illegal option was detected.
W 109: Type not completely specified for symbol <symbol> in file
Not a complete type specification in either the current file or the mentioned file. This could be an array with unknown depth, or a function with unknown parameters.
W 110: Compatible types, different definitions for symbol <symbol> in file
Name conflict between compatible types. This could be a member name, tag name for a struct, or a different type name for equal sized basic types (int, long). Note that a basic type conflict is a non
portable construct.
W 111: Signed/unsigned conflict for symbol <symbol>
in file
Size of both types is correct, but one of the types contains an unsigned where the other uses a signed type.
W 112: Type conflict for symbol <symbol> in file
W 113: Table of contents of file out of date,
not searched. (Use ar ts <name>)
The ar library has a symbol table which is not up
to date. Generate a new one with 'ar ts'.
W 114: No table of contents in file, not searched.
(Use ar ts <name>)
The ar library has no symbol table. Generate one with
'ar ts'.
W 115: Library library contains ucode which is
not supported
Ucode is not supported by the linker.
W 116: Not all modules are translated with the same threshold
(-G value)
The library file has an unknown format, or is corrupted.
W 117: No type found for <symbol>. No type check
performed
No type has been generated for the symbol
W 118: Variable <name>, has incompatible external
addressing modes with file <filename>
A variable is not yet allocated but two external references are made
by non overlapping addressing modes. This is always an error.
W 119: error from the Embedded Environment: message, switched off relaxed addressing mode check
If the embedded environment is readable for the linker, the addressing mode check is relaxed. For instance, a variable defined as data may
be accessed as huge. For an overview of the embedded environment error messages, see appendix E,
Embedded Environment Error Messages.
W 120: Cannot find target description file name,
relaxed addressing mode check disabled
The linker cannot find the description file (.dsc), this means that the linker cannot verify if addressing modes are compatible. For instance, the linker will now generate an error when far data is accessed as huge.
3 Errors (E)
E 200: Illegal object, assignment of non existing var var
The MUFOM variable did not exist. Corrupted object file.
E 201: Bad magic number
The magic number of a supplied library file was not ok.
E 202: Section name does not have the same attributes
as already linked files
Named section with different attributes encountered. Use -t
flag to see which files are already linked. It is possible that a previously linked file started a .out section with wrong attributes.
E 203: Cannot open filename
A given file was not found.
E 204: Illegal reference in address of name
Illegal MUFOM variable used in value expression of a variable. Corrupted object file.
E 205: Symbol 'name' already defined in <name>
A symbol was defined twice. The message gives the files involved.
E 206: Illegal object, multi assignment on var
The MUFOM variable was assigned more than once probably due to a previous error 'already defined', E205.
E 207: Object for different processor characteristics
Bits per MAU, MAU per address or endian for this object differs with the first linked object.
E 208: Found unresolved external(s):
There were some symbols not found. If -r is not set,
this is an error.
E 209: Object format in file not supported
The object file has an unknown format, or is corrupted.
E 210: Library format in file not supported
The library file has an unknown format, or is corrupted.
E 211: Function <function> cannot be
added to the already built overlay pool <name>
The overlay pool has already been built in a previous linker action.
Use option -r to prevent this.
E 212: Duplicate absolute section name <name>
Absolute sections begin on a fixed address. They cannot be linked.
E 213: Section <name> does not have the same
size as the already linked one
A section with the EQUAL attribute does not have the same size as other, already linked, sections.
E 214: Missing section address for absolute section <name>
Each absolute section must have a section address command in the object. Corrupted object file.
E 215: Section <name> has a different address
from the already linked one
Two absolute sections may be linked (overlaid) on some conditions. They must have the same address.
E 216: Variable <name>, name
<name> has incompatible external addressing modes
A variable is allocated outside a referencing addressing space. For instance, the variable was not allocated in the zero page and this variable was referenced with the zero page addressing mode. This is always an error.
E 217: Variable <name>, has incompatible external
addressing modes with file <filename>
A variable is not yet allocated but two external references are made
by non overlapping addressing modes. This is always an error.
E 218: Variable <name>, also referenced in <name> has an incompatible address format
Addresses are often expressed in bytes. In some special cases, the address is expressed in bits. This is necessary for bit variables.
An attempt was made to link different address formats between the current file and the mentioned file.
E 219: Not supported/illegal feature
in object format format
An option/feature is not supported or illegal in given object format.
E 220: page size (0xhexvalue) overflow for section
<name> with size 0xhexvalue
Section is too big to fit into the page.
E 221: message
Error generated by the object. These errors are in fact generated
by the assembler. It has been caused by a jump instruction which is out of range.
E 222: Address of <name> not defined
No address was assigned to the variable. Corrupted object file.
E 223: Illegal object, empty name assignment on variable name
An empty name assignment of a MUFOM variable (type N, X or I).
4 Fatal Errors (F)
F 400: Cannot create file filename
The given file could not be created.
F 401: Illegal object: Unknown command at offset offset
An unknown command was detected in the object file. Corrupted object file.
F 402: Illegal object: Corrupted hex number at offset offset
Wrong byte count in hex number. Corrupted object file.
F 403: Illegal section index
A section index out of range was detected. Corrupted object file.
F 404: Illegal object: Unknown hex value at offset offset
An unknown variable was detected in the object file. Corrupted object file.
F 405: Internal error number
Internal fatal error. Passed number will give more information!
F 406: message
No key no IBM compatible PC
F 407: Missing section size for section <name>
Each section must have a section size command in the object. Corrupted object file.
F 408: Out of memory.
An attempt to allocate more memory failed.
F 409: Illegal object, offset offset
Inconsistency found in the object module.
F 410: Illegal object
Inconsistency found in the object module at unknown offset.
F 413: Only name object can be linked
It is not possible to link object for other processors.
F 414: Input file file same as output
file
Input file and output file cannot be the same.
F 415: Demonstration package limits exceeded
One of the limits in this demo version was exceeded.
F 416: Only one description file allowed
The linker accepts only one description file.
5
Verbose (V)
V 000: Abort !
The program was aborted by the user.
V 001: Extracting files
Verbose message extracting file from library.
V 002: File currently in progress:
Verbose message file currently processed.
V 003: Starting pass number
Verbose message, start of given pass.
V 004: Rescanning....
Verbose message rescanning library. Rescanning is done if there were new unsatisfied externals during the last scan.
V 005: Removing file file
Verbose message cleaning up. Temp files are always removed, map file and .out file are removed if switch -e is on and the exit code is unequal to zero.
V 006: Object file file format format
Named object file does not have the standard toolchain object format TIOF-695.
V 007: Library file format format
Named library file does not have the standard toolchain archiver format
V 8: Embedded environment name read, relaxed addressing
mode check enabled
Embedded environment successfully read.
Copyright © 2002 Altium BV