### Fatal Linker Error Messages 1001 - 1049

LNK1001
  option option is ambiguous
  Explanation: A unique option name does not appear after the option indicator (/).
  Example: The command

          ILINK /N main;

  produces this error because ILINK cannot tell which of the various options beginning with the letter N is intended.
  Action: Retry using the correct minimum option abbreviation.

LNK1002
  unrecognized option option is ignored
  Explanation: The option specified is not valid for ILINK.
  Action: Specify a valid option or remove the unrecognized option and relink.
LNK1004
  option : invalid numeric value
  Explanation: An incorrect value appeared for one of the ILINK options. This might be because a character string has been entered for an option that requires a numeric value or because the proper numeric prefix (for example, 0x for hexadecimal) was not used for a numeric value.
  Action: Retry with a numeric value.
LNK1005
  option : invalid version number
  Explanation: Invalid arguments were specified for the /VERSION option. The correct syntax is /VERSION:major[ .minor] where major and minor should be integers in the range 0-65535
  Action: Retry with proper numeric values.
LNK1006
  option : invalid stack size
  Explanation: The size you specified for the stack in the /STACK option of the link command is more than 65,535 bytes.
  Action: Retry with a stack size of less than or equal to 65,535 bytes.
LNK1008
  option : segment limit set too high
  Explanation: The specified limit on the /SEGMENTS option is greater than 16 375.
  Action: Retry with a limit in the range 1 to 16 375.
LNK1009
  Invalid character in command line or response file
  Explanation: The character is not valid.
  Action: Remove the invalid character and retry. If you specified a plus (+) sign to separate file names, you need to change the plus to a space or tab character, or link with /NOFREE to use the older LINK386-compatible syntax.
LNK1010
  Error reading resource file filename1
  Explanation: An I/O error occurred while reading the resource file filename1.
  Action: Make sure the I/O devices are ready. The resource file may be damaged. If so, recreate the resource file.
LNK1012
  Invalid version string.
LNK1014
  Execute attribute removed from the DATA option
  Explanation: The execute attribute is not valid for the DATA option.
  Action: Remove the execute attribute from the DATA option.
LNK1015
  Execute attribute required for the CODE option
  Explanation: The execute attribute is required for the CODE option.
  Action: Add the execute attribute to the CODE option.
LNK1016
  Removed write attribute for executable seqment name1
  Explanation: An executable segment cannot also be writable.
  Action: Remove the write attribute for executable seqment name1.
LNK1020
  no object modules specified
  Explanation: You did not specify any object file names to the linker.
  Action: Restart ILINK, including at least one object file name.
LNK1021
  cannot nest response files
  Explanation: A response file has been named within another response file. You have used @filename within the response file. The @ symbol is reserved by ILINK to signify a response file name.
  Action: Edit the response file to remove the nested response file.
LNK1022
  response line too long
  Explanation: A line in an automatic response file is longer than 256 characters.
  Action: Edit the line to make it shorter than 256 characters. Response files can contain more than one line.
LNK1023
  terminated by user
  Explanation: You pressed Ctrl+C or Ctrl+Break.
  Action: Your action has terminated ILINK. Restart if necessary.
LNK1025
  multiple output files specified
  Explanation: You can only specify one output file.
  Action: Remove all but one specification and retry.
LNK1027
  Output file name /OUT:filename1 does not match output file name /OUT:filename2
  Explanation: /OUT was specified more than once, and the names specified are conflicting. It could be a combination of command line and response file input.
  Action: Ensure the output file name is the same wherever specified.
LNK1028
  unmatched quote
  Explanation: There was an unmatched quote passed to the linker. When quotes are used, for example in an option parameter, there must always be opening and closing quotes.
  Action: Add the matching (closing) quote and retry.
LNK1029
  File name on directive /OUT:filename1 does not match output file name /OUT:filename2
  Explanation: /OUT was specified on the command line or in a response file, and also imbedded in a .exp file. The names are conflicting.
  Action: If you want to specify the name in an export definition file, do not specify /OUT on the command line. Otherwise, if you're linking an .exp file you may want to recreate that file using ILIB, and specifying the name of the output file in the name section in the module definition file.
LNK1030
  missing internal name
  Explanation: You have not specified an internal name for an import in the module definition file.
  Action: Edit the module definition file, giving an internal name so that ILINK can identify references to the import.
LNK1031
  module description redefined
  Explanation: You have used the DESCRIPTION keyword for a module in the module definition file more than once.
  Action: Edit the module definition file, deleting the extra descriptions.
LNK1032
  module name redefined
  Explanation: You have defined a module name more than once with the NAME or LIBRARY keyword in the module definition file.
  Action: Edit the module definition file, checking the module name definitions.
LNK1033
  input line too long; number characters allowed
  Explanation: The input line contains more than number characters.
  Action: Retry the command with fewer characters on the input line.
LNK1034
  syntax error
  Explanation: There was a syntax error in your module definition file.
  Action: Consult the help on Using Module Definition Files.
LNK1040
  too many exported entries
  Explanation: You have tried to export more than 65535 names.
  Action: Retry with fewer names, creating an additional executable module if necessary.
LNK1043
  line too long in memory map file
  Explanation: A line in the memory map file you specified for the /BASE option is too long.
  Action: Make line shorter.
LNK1045
  too many TYPDEF records
  Explanation: An object module contains more than 255 TYPDEF records. These records describe communal variables. This error can only appear with programs produced by compilers that support communal variables.
  Action: Reduce the number of TYPDEF records, breaking the module into smaller parts, if necessary.
LNK1049
  too many segments
  Explanation: The program has more than the maximum number of segments. The /SEGMENTS option specifies the maximum allowed number; the maximum is 16375.
  Action: Restart ILINK using the /SEGMENTS option with an appropriate number of segments.

Linker Error Messages