Specifications

Linker Tools Messages Page 3 of 32
the problem.
There may be a bad block on your disk. Although the operating system and disk hardware
should have detected such an error, you may want to run a disk checking program.
Linker Tools Error LNK1107
invalid or corrupt file: cannot read at location
The tool could not read the file. Recreate the file.
Linker Tools Error LNK1108
cannot write file at location
The tool could not write to the file. One of the following may be a cause:
There was not enough disk space to create the file.
The drive being written to was not available, possibly due to a network problem.
Linker Tools Error LNK1109
cannot remove file "filename"
LIB could not delete the given file. Before LIB writes the new version of a library, it removes the
existing library file. One of the following may be a cause:
The given file does not have the appropriate permissions.
The drive containing the file was not available, possibly due to a network problem.
Linker Tools Error LNK1110
cannot rename file "filename"
LIB could not rename the given file. When LIB builds a new version of a library, it creates a
temporary file, then renames the file. One of the following may be a cause:
The given file does not have the appropriate permissions.
The drive containing the file was not available, possibly due to a network problem.
Linker Tools Error LNK1111
invalid /BASE argument "argument"
The /BASE option was incorrectly specified. Either no argument was specified or argument is not a
number.
Linker Tools Error LNK1112
module machine type "type1" conflicts with target machine type "type2"
The object files specified as input were compiled for different machine types.
Linker Tools Error LNK1113
invalid machine type
The machine type specified in the object header is not valid. Probably the file is corrupt. Rebuild the
object. See Corrupt Object File for more information.
Linker Tools Error LNK1115
/MACHINE option required
LINK or LIB cannot determine the machine type for objects that are provided entirely from libraries.
Either specify the /MACHINE option with the appropriate machine type or specify at least one object