Linker Tools Error LNK1152
cannot resolve one or more undecorated symbols
This error is preceded by one warning LNK4022 for each undecorated symbol that could not be
resolved and by at least two warnings LNK4006 for the duplicate symbols found for the undecorated
symbol.
Linker Tools Error LNK1153
/VXD command-line option required
You attempted to build a virtual device driver without the /VXD option. Relink with the /VXD
option.
Linker Tools Error LNK1154
specified import library filename matches exports file "filename"
The filename specified with LINK /IMPORT or with LIB /DEF /OUT conflicted with the filename
given by LINK or LIB to the exports file, which is formed from the base name of the main output
file and the extension .EXP.
Linker Tools Error LNK1155
special symbol "symbol" already defined
The given symbol is reserved for use by LINK.
Linker Tools Error LNK1156
.sbss section not supported
An object file contained an .sbss section.
Linker Tools Error LNK1157
fixup overflow; offset of target symbol "symbol" greater than +-8MB
The VXD is too large, or the sections are not arranged properly.
Linker Tools Error LNK1158
cannot run "filename"
The given executable file called by LINK is not in the directory that contains LINK and is
not in a directory specified in the PATH environment variable.
Linker Tools Error LNK1159
no output file specified
No name was specified for the main output file (executable file or DLL).
LINK derives the default name of the output file from the base name of the first object file. If
no object files are specified, and if the /OUT option is not used, this error occurs.
Linker Tools Error LNK1160
library with zero objects not allowed
An attempt was made to remove an object from a library that contained only that object. The object
was not removed.
Linker Tools Error LNK1161
invalid export specification
Either the /EXPORT option or the EXPORTS module-definition statement incorrectly specified an
export. A possible cause is a typing error.
Linker Tools Error LNK1162
expected aux symbol for comdat section number
The linker expected to find an auxiliary symbol table for the indicated COMDAT but could not. The
object file is probably corrupt.
See Corrupt Object File for more information.
Linker Tools Error LNK1163
invalid selection for comdat section number
The byte in the object file indicating the type of COMDAT section is invalid. The object file is
probably corrupt. See Corrupt Object File for more information.
Linker Tools Error LNK1164
section section alignment (number) greater than /ALIGN value
The alignment size for the given section in the object file exceeds the value specified with
the /ALIGN option. The /ALIGN value must be a power of 2 and must equal or exceed the section
alignment given in the object file. Either recompile with a smaller section alignment or increase
the /ALIGN value.
Linker Tools Error LNK1165
link failed because of fixup errors
The build failed due to fixup errors.
The /FORCE or /FORCE:UNRESOLVED option overrides this error.
Linker Tools Error LNK1166
cannot adjust code at offset=offset, va=value
LINK was unable to pad the code as required. Certain instructions are not allowed to cross page
boundaries on some processors. LINK attempts to add pads to correct this situation. In this case,
LINK could not work around the problem.
Linker Tools Error LNK1167
file contains relocs but header has no machine type
A converted COFF object did not have a machine type specified in its header.
One cause of this error is omitting a machine type when converting a .RES file in a separate step
before linking.
Linker Tools Error LNK1168
cannot open filename for writing
The given file does not have write permission.
Linker Tools Error LNK1169
one or more multiply defined symbols found
The build failed due to multiple definitions of one or more symbols. This error is preceded by
error LNK2005. The /FORCE or /FORCE:MULTIPLE option overrides this error.
Linker Tools Error LNK1170
line in command file contains limit or more characters
The length of a line in a command file must be less than the given limit.
Linker Tools Error LNK1171
unable to load filename
The given DLL was unavailable. The possible locations for the DLL are the current directory, the
system directory, the Windows directory, and the directories specified in the PATH environment
variable.
Linker Tools Error LNK1172
more than one object with the name "object" found; rename object(s) or
relink /PDB:NONE
A library contained two or more objects with the same name. Do one of the following:
Linker Tools Error LNK1173
unable to find entrypoint function in filename
The given function does not exist in the given DLL.
Linker Tools Error LNK1174
unable to /REBASE filename; not a valid Win32 image
The format of the given file was invalid.
Linker Tools Error LNK1175
failed to /REBASE filename
The rebase operation failed on the given file.
Linker Tools Error LNK1177
TOC size limit exceeded
The linker was unable to create a TOC (Table of Contents) in your image file. The limit is 2048
entries in the TOC.
Linker Tools Error LNK1178
missing MODEND record; file is invalid or corrupt
The linker tool tried to convert an OMF object module to COFF format but could not find an
expected MODEND (module end) record in the OMF object. The OMF object module is corrupt and needs
to be recreated or recopied.
See Corrupt Object File for more information.
Linker Tools Error LNK1179
invalid or corrupt file: duplicate comdat comdat
An object module contained two or more COMDATs with the same name.
One possible cause is if you use the Visual C++ /H option with the Visual C++ /Gy option.
The /H option limits the length of external names, and the /Gy option packages functions
in COMDATs.
Linker Tools Error LNK1180
insufficient disk space to complete link
The linker tool was unable to complete a file operation since the operating system reported that
the disk is full. Free up space on your local and network drives (if you are writing files there).
Linker Tools Error LNK1181
cannot open input file "filename"
The linker tool could not find "filename" because it does not exist or the
path was not found.
Linker Tools Error LNK1182
cannot have more than 64K exports
You have reached the linker's limit of 65,536 exports.
Linker Tools Error LNK1183
invalid or corrupt file: extended relocation count number less than 65535
The COFF object file is corrupt since it contains an extended relocation count that is less than
0xFFFF. See Corrupt Object File for more information.
Linker Tools Error LNK1184
invalid section name "section" specified in option or directive "option"
You gave the linker an invalid section name in option. Invalid section names contain "$"
or blanks.
Linker Tools Error LNK1185
invalid section name "section" specified
You gave the linker an invalid section name in a .DEF file. Invalid section names contain "$" or
blanks.
Linker Tools Error LNK1186
invalid or corrupt COFF object; reloc to undefined static symbol "symbol"
Your COFF object module is corrupt since it contains a relocation entry for an undefined static
symbol. See Corrupt Object File for more information.
Linker Tools Error LNK1187
Corrupt object - unmatched name relocation; ignored
Your object file contains bad relocation information. Recopy or recreate the object file.
See Corrupt Object File for more information.
Linker Tools Error LNK1188
BADFIXUPSECTION:: invalid fixup target "symbol"; possible zero length section
This message is issued only for VxD links when the target of a relocation does not have a section.
With LINK386 (an older version), an OMF GROUP record (generated by a MASM GROUP directive) may
have been used to combine the zero length section with another non-zero length section. COFF
format does not support the GROUP directive and zero-length sections. When LINK automatically
converts this type of OMF objects to COFF, this error may occur.
Linker Tools Error LNK1189
LIBTOOMANYMEMBERS:: library limit of number objects exceeded
The limit of 65535 objects or members in a library has been exceeded.