PRB: LINK Error L2022: Export Undefined (96186)
The information in this article applies to:
- Microsoft Windows Software Development Kit (SDK) 3.0
- Microsoft Windows Software Development Kit (SDK) 3.1
This article was previously published under Q96186 SYMPTOMS
When an application is processed by the Microsoft Segmented-Executable
Linker, the error message L2022 "export undefined" is generated.
Two possible causes of this error, and the corresponding steps to resolve
the problem, follow.
CAUSECAUSE 1
The name of a function that is used in the application is not
properly listed in the EXPORTS statement in the module definition
(DEF) file.
CAUSE 2
Unprintable characters appear at the end of the EXPORTS statement
in the module definition (DEF) file.
RESOLUTIONRESOLUTION 1
Determine the correct spelling of the label and correct the source
file or the DEF file. For example, the names of functions called
with the PASCAL calling convention are implicitly converted to
uppercase letters. In functions exported with the CDECL calling
convention, the case of the function name is preserved, and an
underscore (_) is added to the function name as a prefix.
RESOLUTION 2
Modify the DEF file to remove the unwanted characters. Also make
sure that the DEF file is saved from the text editor or word
processor as plain text.
MORE INFORMATION
The linker /INFORMATION option provides additional information about
the linking process to assist in tracking and correcting errors.
| Modification Type: | Major | Last Reviewed: | 10/30/2003 |
|---|
| Keywords: | kb16bitonly KB96186 |
|---|
|