Specifications

788 LINK Error Messages
Filename: LMAETAPA.DOC Project: MASM Environment and Tools
Template: MSGRIDA1.DOT Author: Nobody Last Saved By: Mike Eddy
Revision #: 136 Page: 788 of 104 Printed: 10/09/00 02:49 PM
L2005 fixup type unsupported at number in segment segment
A fixup type occurred that is not supported by LINK. This is probably a translator error.
Note which translator (compiler or assembler) produced the incorrect object module and
the circumstances in which it was produced. Please report this error to Microsoft
Corporation by following the instructions in the “Microsoft Support Services” section of
the introduction to this book.
L2010 too many fixups in LIDATA record
The number of far relocations (pointer- or base-type) in an LIDATA record exceeds the
limit imposed by LINK.
The cause is usually a DUP statement in an assembly-language program. The limit is
dynamic: a 1,024-byte buffer is shared by relocations and the contents of the LIDATA
record. There are 8 bytes per relocation.
Reduce the number of far relocations in the DUP statement.
L2011 identifier : NEAR/HUGE conflict
Conflicting NEAR and HUGE attributes were given for a communal variable. This error
can occur only with programs produced by the Microsoft FORTRAN optimizing
compiler or other compilers that support communal variables.
L2012 arrayname : array-element size mismatch
A far communal array was declared with two or more different array-element sizes (for
instance, an array was declared once as an array of characters and once as an array of
real numbers). This error occurs only with the Microsoft FORTRAN optimizing compiler
and any other compiler that supports far communal arrays.
L2013 LIDATA record too large
An LIDATA record contained more than 512 bytes. This is probably a translator error.
Note which translator (compiler or assembler) produced the incorrect object module and
the circumstances in which it was produced. Please report this error to Microsoft
Corporation by following the instructions in the “Microsoft Support Services” section of
the introduction to this book.
L2022 entry (alias internalname) : export undefined
The internal name of the given exported routine or data item is undefined.
L2023 entry (alias internalname) : export imported
The internal name of the given exported routine or data item conflicts with the internal
name of a previously imported routine or data item.