Format of Error Messages

There are three types of LINK386 error messages:

• Fatal errors cause LINK386 to stop running. They have the following format: location : fatal error L1xxx : message text
  
  Nonfatal errors indicate problems in the executable file. LINK386 produces the executable file and sets the error bit in the header for the OS/2 environment. This means that the executable file cannot be run from OS/2. Nonfatal error messages have the following format:

  location : error L2xxx : message text

  
  Warnings indicate possible problems in the executable file. LINK386 produces the executable file, but does not set the error bit in the header for the OS/2 environment. Warnings have the following format:

  location : warning L4xxx : message text

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

  myfile.def(3): fatal error L1030: 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
  

  Error Message Descriptions

  Fatal Error Messages (part 1) 1001 - 1049
  Fatal Error Messages (part 2) 1050 - 1098
  Fatal Error Messages (part 3) 1100 - 1130
  Nonfatal Error Messages 2000 - 2063
  Warning Error Messages 4000 - 4094

  ---

  [Back] [Next]