A LNK2005 error occurs when the CRT library and MFC libraries are linked in the wrong order in Visual C++ (148652)


The information in this article applies to:

  • Microsoft Visual C++ 4.0
  • Microsoft Visual C++ 4.1
  • Microsoft Visual C++, 32-bit Enterprise Edition 5.0
  • Microsoft Visual C++, 32-bit Enterprise Edition 6.0
  • Microsoft Visual C++, 32-bit Professional Edition 5.0
  • Microsoft Visual C++, 32-bit Professional Edition 6.0
  • Microsoft Visual C++, 32-bit Learning Edition 6.0
  • Microsoft Visual C++ .NET (2002)
  • Microsoft Visual C++ .NET (2003)
This article was previously published under Q148652

SYMPTOMS

When the C Run-Time (CRT) library and Microsoft Foundation Class (MFC) libraries are linked in the wrong order, you may receive one of the following LNK2005 errors:
nafxcwd.lib(afxmem.obj) : error LNK2005:
"void * __cdecl operator new(unsigned int)"(??2@YAPAXI@Z) already
defined in LIBCMTD.lib(new.obj)
nafxcwd.lib(afxmem.obj) : error LNK2005:
"void __cdecl operator delete(void *)"(??3@YAXPAX@Z) already defined
in LIBCMTD.lib(dbgnew.obj)
nafxcwd.lib(afxmem.obj) : error LNK2005:
"void * __cdecl operator new(unsigned int,int,char const *,int)"
(??2@YAPAXIHPBDH@Z) already defined in LIBCMTD.lib(dbgnew.obj)
mfcs40d.lib(dllmodul.obj): error LNK2005: _DllMain@12 already defined in
MSVCRTD.LIB (dllmain.obj)
mfcs42d.lib(dllmodul.obj): error LNK2005: _DllMain@12 already defined in
msvcrtd.lib(dllmain.obj)

CAUSE

The CRT libraries use weak external linkage for the new, delete, and DllMain functions. The MFC libraries also contain new, delete, and DllMain functions. These functions require the MFC libraries to be linked before the CRT library is linked.

RESOLUTION

There are two ways to resolve this problem. The first solution involves forcing the linker to link the libraries in the correct order. The second solution allows you to find the module that is causing the problem and to correct it.

Note The following steps are based on Visual C++ 6.0.

Solution One: Force Linker to Link Libraries in Correct Order

  1. On the Project menu, click Settings.
  2. In the Settings For view of the Project Settings dialog box, click to select the project configuration that is getting the link errors.
  3. On the Link tab, click to select Input in the Category combo box.
  4. In the Ignore libraries box, insert the library names (for example, Nafxcwd.lib;Libcmtd.lib).

    Note The linker command-line equivalent in /NOD:<library name>.
  5. In the Object/library modules box, insert the library names. You must make sure that these are listed in order and as the first two libraries in the line (for example, Nafxcwd.lib Libcmtd.lib).
To set this option in Visual C++ .NET, read the "Setting Visual C++ Project Properties" online help topic.

Solution Two: Locate and Correct the Problem Module

To view the current library link order, follow these steps:
  1. On the Project menu, click Settings.
  2. In the Settings For view of the Project Settings dialog box, click to select the project configuration that is getting the link errors.
  3. On the Link tab, type /verbose:lib in the Project Options box.
  4. Rebuild your project. The libraries will be listed in the output window during the linking process.

STATUS

This behavior is by design.

MORE INFORMATION

When you use the MFC libraries, you must make sure that they are linked before the CRT library is linked. You can do this by making sure that every file in your project includes Msdev\Mfc\Include\Afx.h first, either directly (#include <Afx.h>) or indirectly (#include <Stdafx.h>). The Afx.h include file forces the correct order of the libraries, by using the #pragma comment (lib,"<libname>") directive.

If the source file has a .c extension, or the file has a .cpp extension but does not use MFC, you can create and include a small header file (Forcelib.h) at the top of the module. This new header makes sure that thelibrary search order is correct.

Visual C++ does not contain this header file. To create this file, follow these steps:
  1. Open Msdev\Mfc\Include\Afx.h.
  2. Select the lines between #ifndef _AFX_NOFORCE_LIBS and #endif //!_AFX_NOFORCE_LIBS.
  3. Copy the selection to the Windows Clipboard.
  4. Create a new text file.
  5. Paste the contents of the Clipboard into this new file.
  6. Save the file as Msdev\Mfc\Include\Forcelib.h.

Steps to Reproduce the Problem in Visual C++ .NET

  1. Start Microsoft Visual Studio .NET.
  2. On the File menu, point to New, and then click Project.
  3. Click Visual C++ Projects under Project Types, and then click MFC Application under Templates.
  4. In the Name text box, type Q148652.
  5. In the Location text box, type C:\Test, and then click OK.
  6. In the MFC Application Wizard dialog box, click Application Type.
  7. Click Dialog based under Application type, and then click Use MFC in a static library under Use of MFC.
  8. Click Finish.
  9. In Solution Explorer, under Source Files select all the three .cpp files.
  10. Right-click the three selected files, and then click Remove.
  11. Right-click Source files, point to Add, and then click Add New Item.
  12. Click C++ files under Templates. In the Name text box, type Aa. Click Open.
  13. Paste the following code in the Aa.cpp file: 
    int test(){new int; return 1;}
  14. Right-click Source Files, point to Add, and then click Add Existing Item.
  15. Select the following files:
    • Q148652.cpp
    • Q148652Dlg.cpp
    • stdafx.cpp
  16. Click Open.
  17. The files that you selected in step 15 appear under Source Files.
  18. Select all four .cpp files under Source Files.
  19. Right-click the four .cpp files that you selected, and then click Properties.
  20. Expand Configuration Properties, and then expand C/C++.
  21. Click Precompiled Headers.
  22. Set the Create/Use Precompiled Header property to Not Using Precompiled Headers. Click OK.
  23. On the Build menu, click Rebuild Solution.
Modification Type:MinorLast Reviewed:1/23/2006
Keywords:kbtshoot kbArtTypeINF kberrmsg kbprb KB148652 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.