Fatal Error Messages 1100 - 1210
- LNK1100
- stub .EXE file invalid
Explanation: The stub file specified in the module definition file is not a valid
.EXE file.
Action: Ensure that the stub file is an executable file.
-
- LNK1101
- invalid object module
Explanation: One of the object modules was incorrectly formed during compilation or
assembly.
Action: Recompile or reassemble your source code. If the error persists, contact
your supplier.
-
- LNK1103
- name: attempt to access data outside segment bounds
Explanation: A data record in an object module specified data extending beyond the
end of a segment. This is a translator error.
Action: Note which translator (compiler or assembler) produced the incorrect object
module and the circumstances, and contact your supplier.
-
- LNK1104
- filename: not valid library
Explanation: The specified file is not a valid library file. This error causes
ILINK to stop running.
Action: Ensure that the named file is a valid library file and restart ILINK. If
this does not work, rebuild your library or contact your supplier.
-
- LNK1105
- invalid object due to aborted incremental compile
Explanation: An object file from an aborted compile is trying to be linked.
Action: Recompile the source that produced the bad compile and then relink.
-
- LNK1106
- unknown COMDAT allocation type for name; record ignored
Explanation: The COMDAT (record in .OBJ) allocation type for the named COMDAT was
not valid.
Action: Recompile or reassemble .OBJ and try again. If that does not work, contact
your supplier.
-
- LNK1107
- unknown COMDAT selection type for name; record ignored
Explanation: The COMDAT (record in .OBJ) selection type for the named COMDAT is not
valid.
Action: Recompile or reassemble .OBJ and try again. If that does not work, contact
your supplier.
-
- LNK1108
- invalid format of debugging information
Explanation: An error was detected in a segment that contains debug information.
Action: Recompile or reassemble and try again. If that does not work, try relinking
without using the /DE or /CO options.
-
- LNK1109
- absolute segments are not supported
Explanation: The object module contained segments specified as absolute. The object
module was created by another compiler, and was intended for use in ROM code. xph.absolute
segments are not specified by IBM C and C++ compilers and are not supported by the linker.
Action: Link without the object module, or with a replacement object module that
does not use absolute segments.
-
- LNK1110
- unsupported SEGDEF attributes; assuming Public, Use32
Explanation: The object module contains a group definition with attributes other
than 0xFF. The object module was probably created by another compiler. The group
definition is not acceptable to the linker.
Action: Link without the object module, or with a replacement object module that
does not use absolute segments.
-
- LNK1111
- module requires munch step -- try ICC option /Gk or ILINK /OLDCPP
Explanation: The module was created by a previous version of the compiler.
Action: If you invoke the linker with ICC, specify the compiler option /Gk. If you
invoke the linker directly, specify the linker option /OLDCPP. You can then link the old
object module.
-
- LNK1112
- invalid DLL used with OLD keyword in definitions file
Explanation: The DLL you wanted to maintain compatibility with is not valid.
Action: Make sure you specified the correct DLL. Retry when ready.
-
- LNK1113
- unresolved COMDEF; internal error
Explanation: ILINK encountered a COMDEF (record in .OBJ) in pass 2 that was not
defined in pass 1.
Action: Recompile or reassemble and try again. If that does not work, contact your
supplier.
-
- LNK1114
- unresolved COMDAT name: internal error
Explanation: ILINK found specified COMDAT in pass 2 that does not correspond to
COMDATs found in pass 1.
Action: Recompile or reassemble and try again. If that does not work, contact your
supplier.
-
- LNK1117
- unallocated COMDAT name; internal error
Explanation: The linker encountered COMDAT in pass 2 for which space was not
allocated during pass 1.
Action: Recompile or reassemble and try again. If that does not work, contact your
supplier.
-
- LNK1121
- name: group larger than 4G-1 bytes
Explanation: The group indicated is too large.
Action: Recompile or reassemble and try again. Remove segments from the group or
create additional executables if necessary.
-
- LNK1123
- name: segment defined both 16- and 32-bit
Explanation: The segment named was defined as both 16-bit and 32-bit.
Action: Create two segments (one for 16-bit, one for 32-bit), or make sure the
segment is defined one way and relink.
-
- LNK1126
- conflicting IOPL-parameter-words value
Explanation: The IOPL parameter words in the .DEF file does not exactly match those
in the corresponding EXPDEF object record.
Action: Make sure .DEF file coincides with that defined in .OBJ. Relink.
-
- LNK1127
- IOPL-parameter-words value is larger than
Explanation: The IOPL parameter words value in the .DEF file is too large.
Action: Reduce value and relink.
-
- LNK1128
- too many nested include files in module-definition file
Explanation: The .DEF file exceeded a nesting level.
Action: Combine some nestings into one .DEF file and try again.
-
- LNK1129
- missing or bad include file name
Explanation: ILINK could not find a file included by .DEF file.
Action: Make sure the file exists and can be located and that any path is specified
correctly. Try again.
-
- LNK1132
- conflicting subsystem encountered
Explanation: A conflicting subsystem is used in a COFF object
Action: Recompile COFF object
LNK1135
- unsupported operating system
Explanation: An unsupported operating system type was encountered
- LNK1146
- cannot resolve file name
-
- LNK1148
- OPTVFUNC not allowed
Explanation: linker option /OPTVFUNC is not allowed when linking a DLL
Note: /OPTVFUNC is not active in this version of IBM C and C++ Compilers.
-
- LNK1210
- out of memory for module reference table information
Explanation: The total size of the module reference table is greater than the
internal limit in ILINK.
Action: Reduce the size of the executable, consider using dynamic link libraries to
split the program into smaller modules.
-

Linker Error Messages