Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

MKL 11.2 Install Failure - Fortran Composer XE 2015 / VS 2010 Shell

Scott_Graham
Beginner
1,227 Views

I recently attempted to upgrade my Fortran compiler to the Fortran Composer XE 2015 edition released on 2/5/2015.  The Fortran upgrade appears to have gone OK. However, when installing the MKL libraries I get an error that the debugger extension requires Visual Studio 2012 or 2013, and the install window for the MKL libraries places a red X on the install of "Intel MKL core libraries for Intel (c) 64" and "Intel MKL core libraries for IA32".  Does the new version of MKL require Visual Studio 2012 or 2013?  Is there a work around to get this to work on my VS 2010 shell that came with the Intel Fortran compiler?

Thanks !

0 Kudos
7 Replies
Steven_L_Intel1
Employee
1,227 Views

The message about the debugger extension can be ignored unless you want to debug applications that run on Intel Xeon Phi. It is not an error.

No, MKL doesn't require VS2012 or VS2013. Why are you installing MKL separately? Fortran includes that. Maybe what you're seeing is that it's already installed?

0 Kudos
Scott_Graham
Beginner
1,227 Views

Hi Steve,

  Thanks much for the prompt reply.  On 2/6 I got update notifications for both MKL and Composer edition for windows 2015, so I downloaded both of them and attempted the installs.  When installing I unfortunately selected the option that discarded the earlier versions.  Given the separate update notification/file downloads, I didn’t realize that MKL was installed as part of Fortran.  However after attempting installing both  updates I get numerous link errors relating to finding various libraries ie.  “fatal error LNK1104: cannot open file ‘mkl_intel_lp64.lib’, or ‘libmmt.lib’.  I am also using the IMSL libs which I think sometimes causes a conflict with libcmt.lib.  I think I may have libcmt.lib on an ignore a specific lib in the linker   Any suggestions to sort things out are much appreciated !

Thanks – Scott

0 Kudos
Steven_L_Intel1
Employee
1,227 Views

Does the folder C:\Program Files (x86)\Intel\Composer XE 2015\mkl\lib\intel64 exist and have libraries in it? In VS2010, select Tools > Options > Intel Compilers and Tools > Visual Fortran > Compilers. Click the x64 tab and then the "..." button to the right of Libraries, Does the text that appears include the line "$(IFortInstallDir)mkl\lib\Intel64"?

What I suggest you do is uninstall MKL if you see it as a separate option in Programs and Features and then uninstall and reinstall Intel Parallel Studio XE 2015 Composer Edition. This may sort it all out.

If you are also using IMSL, please follow the instructions here. If you are seeing a libcmt conflict this may be due to specifying both static and DLL libraries in different parts of your build. You should make these the same - and if using IMSL, including 'link_fnl_shared.h' instead of 'link_fnl_static.h' would be best.

0 Kudos
Scott_Graham
Beginner
1,227 Views

Hi Steve - The second line down in the compiler options libs  is $(IFortInstallDir)mkl\lib\Intel64.    The earlier editions of Composer XE had the separate mkl directory, however the new one does not.  Sounds like an uninstall and a clean install is a good approach.

Regarding the libcmt conflict I have been specifying the include 'link_fnl_static.h' in the main program code.  I am not specifying DLL libraries elsewhere, however that may be the defaults used elsewhere.  

I'll try the re-install & used the 'link_fnl_shared.h' instead.  

Thanks again for terrific support !!!

Scott

0 Kudos
Steven_L_Intel1
Employee
1,227 Views

The default for new projects is DLL libraries so that may be part of your issue. Let me know what happens after the reinstall.

0 Kudos
Scott_Graham
Beginner
1,227 Views

Hi Steve,  The re-install seems to have done the trick.  However, I hadn't removed the VS shell prior to the new install, so the Options... lib directories search path still has the reference to the mkl directory.  Should I just delete this reference?

Thanks Again !

Scott

0 Kudos
Steven_L_Intel1
Employee
1,227 Views

The reference you quoted in reply 5 is what should be there. Removing the shell would not have made a difference. The problem was likely caused by the separate install, perhaps incomplete, of MKL, though it's supposed to be smart enough to deal with this.

0 Kudos
Reply