- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am compiling a set of codes through the Intel Composer XE 2011 Update 3 on Microsoft Visual Studio 2008 shell.
In the Debug configuration, the codes were compiled and linked successfully. But there is a warning message of
warning LNK4098: defaultlib libcmt.lib conflict with use of other libs; use /NODEFAULTLIB:library
Many static libraries were linked to the main program of ELCD. Attached are ten BuildLog.htm files for all the components associated with ELCD I built.
If I use /NODEFAULTLIB:library, there would be a lot of other linker errors. Should I ignore that message of use /NODEFAULTLIB:library? What could have caused that warning message?
Wen
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This particular message is almost always bad advice. Better is to maske sure that all code in the application is using the same set of libraries. For you, I recommend going to the Fortran > Libraries property page and set the "Use debug libraries" property to No. You will still be able to debug your Fortran code. Of course, you'll want to do a Release build once you have debugged your code.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am using Microsoft Visual Studio 2008 shell.
On the Fortran > Libraries property page, I dont see "Use debug libraries".
I see the flowing six lines
Runtime Library, set to Debug Multithreaded (/libs:static /threads /dbglib).
Use Common Windows Libraries, set tp No.
Use Portlib Library, set tp No.
Use Intel Math Kernel Library, set tp No.
Disable Default Library Search Rules, set tp No.
Disable OBJCOMMENT Library Names in O . . ., set tp No.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In the selection for "Runtime Library", choose "Multithreaded" instead of "Debug Multithreaded".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, you were right. I still had one library compiled with Debug Multithreaded. The problem was solved after I had that Debug Multithreaded changed to Multithreaded. Thank you, Steve.
I am puzzled. How come I had never had this problem before (even for the same program of slightly different version)? Should I have Debug Multithreaded replaced by Multithreaded for all future compilation tasks in the Debug configuration?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page