KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q34502: /NOE Option for Redefinition Error L2044

Article: Q34502
Product(s): See article
Version(s): 3.x 5.x | 5.10
Operating System(s): MS-DOS | OS/2
Keyword(s): ENDUSER | | mspl13_basic
Last Modified: 13-OCT-1988

The /NOEXTDICTIONARY switch tells the linker NOT to take advantage of
additional information recorded in Extended Dictionary in the library
file. This additional information describes which module in the library
calls any other module from the same library, saving linker number
of passes through the library file to pick up all required modules.

If you have a call in your code to the library function FOO and FOO
calls another function BAR from the same library, then at processing
time of FOO, the linker will pull out BAR. This process occurs because
the extended dictionary has a link between FOO and BAR.

Linking without /NOE causes the following error if you want to pull
FOO in from the library but you want to provide its own BAR:

L2044 BAR : symbol multiply defined, use /NOE

This error resulted from the linker pulling FOO and BAR from the
same library, then later it sees BAR coming from user .OBJ file.

Using /NOE in this case prevents the linker from pulling out
BAR from the library, so your BAR routine is used instead.

If you have genuine symbol redefinition, then when linking with /NOE
you will see the following error:

L2025 BAR : symbol defined more than once

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Copyright Microsoft Corporation 1986-2002.