Linker Tools Messages

The following topics cover linker tools errors and warnings (LNKnnnn), which can be generated LINK, LIB, DUMPBIN, and EDITBIN:

• Linker Errors LNK1000 to LNK1149
• Linker Errors LNK1152 to LNK1189
• Linker Errors LNK1190 to LNK1581
• Linker Errors LNK2001 to LNK2014
• Linker Warnings LNK4001 to LNK4039
• Linker Warnings LNK4040 to LNK4069
• Linker Warnings LNK4070 to LNK4099
• Linker Warnings LNK4102 to LNK4549
• Linker Warnings LNK6001 to LNK6026
• Corrupt Object File Explanation

Corrupt Object File Explanation:

Sometimes the linker is unable to process your object files because they are corrupt. Besides the usual causes of corrupt files such as network problems or exposing a floppy disk to a magnetic field, sometimes the compiler writes an incorrect object file, which you should report to technical support.

After you have ruled out a hardware, operating system, or network problem as the cause of the corrupt object file, you should try the tips below because sometimes by changing compiler options and recompiling, the compiler will write a non-corrupt object file. Here are some things to try when recompiling:

• Turn off optimization with the /nooptimize (/Od, Disable) option.
• Use a different code generation option. See the /tune (/G, Optimize for Processor) options.
• Change the order of functions and global variables.

With Visual C++ mixed-language programs:

• Disable incremental compilation with the /Gi- (Enable Incremental Compilation) option.
• Disable minimal rebuild with the /Gm- (Enable Minimal Rebuild) option.
• Compile with the /Gy (Enable Function-Level Linking) option to package functions.