About link errors

Linker Errors LNK1190 to LNK1581

Linker Tools Error LNK1190
invalid fixup found, type type
The object file has become corrupted. Recompile.

Linker Tools Error LNK1194
cannot delay-load dll name due to import of data symbol symbol name; relink without /DELAYLOAD:dll name
You cannot delay load a DLL if data is imported from it.

Linker Tools Error LNK1195
target machine "machine" requires "option"
Add the required option.

Linker Tools Error LNK1196
invalid or corrupt import object: unknown version
The import library has become corrupted. Rebuild the library.

Linker Tools Error LNK1197
invalid or corrupt import object: unknown type
The import library has become corrupted. Rebuild the library.

Linker Tools Error LNK1198
invalid or corrupt import object: unknown name type
The import library has become corrupted. Rebuild the library.

Linker Tools Error LNK1199
invalid or corrupt import object: non-zero reserved fields
The import library has become corrupted. Rebuild the library.

Linker Tools Error LNK1200
error reading program database "filename"
The given program database (PDB) could not be read, probably because it is corrupted. If filename is the PDB for an object file, recompile the object file; use the /debug:full and /pdbfile options. If filename is the PDB for the main output file and this error occurred during an incremental link, delete the PDB and relink.

Linker Tools Error LNK1201
error writing to program database "filename"; check for insufficient disk space
LINK could not write to the program database (PDB) for the output file. One of the following may be a cause:

• The file is corrupted. Delete filename and relink.
• There was not enough disk space to write to the file.
• The drive being written to was not available, possibly due to a network problem.

Linker Tools Error LNK1202
"filename" missing debugging information for referencing module
The given program database (PDB) for an object file was invalid. Recompile the object file; use CL's /Zi option.

Linker Tools Error LNK1203
"filename" missing current debugging information for referencing module
The given program database (PDB) for an object file was invalid. Recompile the object file; use CL's /Zi option.

Linker Tools Error LNK1204
"filename" compiled /Yc /Yu /Z7; cannot create PDB; recompile with /Zi
Multilayered program databases (PDBs) are not supported in combination with old-style debugging information. Recompile using CL's /Zi option.

Linker Tools Error LNK1206
cannot overwrite Visual C++ 1.0 PDB "filename"; delete and rebuild
This version of LINK cannot write to an existing program database (PDB) created using older versions of the visual development environment. Delete filename and rebuild.

Linker Tools Error LNK1207
incompatible PDB format in "filename"; delete and rebuild
This version of LINK cannot write to the existing program database (PDB). Delete filename and rebuild.

Linker Tools Error LNK1209
program database "filename" differs from previous link; relink or rebuild
The given program database (PDB) is invalid and possibly corrupt. Relink. If filename is also the PDB for an object file, recompile to recreate the PDB.

Linker Tools Error LNK1210
insufficient memory for incremental link; relink with /INCREMENTAL:NO
There was not enough virtual memory available for LINK to create the incremental status (.ILK) file.

Linker Tools Error LNK1211
precompiled type information not found; "filename" not linked or overwritten
The given object file, compiled with /Yc, either was not specified in the LINK command or was overwritten.

Linker Tools Error LNK1212
error opening program database; file is in use
The PDB is already in use by another application.

Linker Tools Error LNK1213
unexpected import object encountered
The import library has become corrupted. Rebuild the library.

Linker Tools Error LNK1221
a subsystem can't be inferred and must be defined
The linker does not have enough information to infer which subsystem you will target your application. To fix this error, use the /SUBSYSTEM option.

Linker Tools Error LNK1561
entry point must be defined
The symbol specified by the /ENTRY option is not defined.

Linker Tools Error LNK1581
corrupted object or old compiler (bad Pcode entry point)
Your object file contained a bad entry point. The object file is probably corrupt. See Corrupt Object File for more information.

[출처] Link Error 에 관한 모든것|작성자 듀얼릿트