### Linker Error Messages

There are three types of ILINK error messages:

- Fatal errors cause the linker (ILINK) to stop running. They have the following format: location : fatal error LNK1 xxx : message text
- Nonfatal errors indicate problems in the executable file. ILINK produces the executable file and sets the error bit in the header for the operating system environment. This means that the executable file cannot be run from that operating system. Nonfatal error messages have the following format:
  location : error LNK2 xxx : message text
- Warnings indicate possible problems in the executable file. ILINK produces the executable file, but does not set the error bit in the header for the operating system environment. Warnings have the following format:
  location : warning LNK4 xxx : message text

In all these messages, location is the input file associated with the error, or it is ILINK itself if there is no input file. The message text is the actual text message that ILINK generates. When the input file is a module definition file, the line number is included , as in this example:

    myfile.def(3): fatal error LNK1030: missing internal name

When the input file is an object file or library file and has a module name, the module name is enclosed in parentheses, as in the following examples:

    SLIBCE.LIB(_file)

    MAIN.OBJ(main.c)

    TEXT.OBJ

Fatal Error Messages 1001 - 1049
Fatal Error Messages 1050 - 1099
Fatal Error Messages (Part 3) 1100 - 1210
Nonfatal Error Messages 2000 - 2065
Warning Error Messages 4000 - 4117