Introduction:

The Intel® Math Kernel Library (Intel® MKL) is designed to run on multiple processors and operating systems. It is also compatible with several compilers and third party libraries, and provides different interfaces to the functionality. To support these different environments, tools, and interfaces Intel MKL provides mutliple libraries from which to choose.

To see what libraries are recommended for a particular use case, specify the parameters in the drop down lists below.

Note: For applications running on IA-32 with the Windows* operating system it is possible to use mkl_intel_s.lib instead of mkl_intel_c.lib (or mkl_intel_s_dll.lib instead of mkl_intel_c_dll.lib). This interface is compatible with the Compaq* Visual Fortran calling convention.

Note: For applications calling Fortan 95 Interface library for BLAS an LAPCK: mkl_blas95.lib mkl_blas95_lp64.lib mkl_lapack95.lib and so on. Please add them manually. For example,  the link line is like:
mkl_lapack95.lib mkl_intel_c.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib

Note: if the option "-Qopenmp or -openmp" are not recognized by the compiler, please use libiomp5md.lib or -liomp5 instead.

Find more information on linking in the Intel® MKL User's Guide

Comments (6)

June 2, 2009 3:29 PM PDT Wayne Wilson

It would also help if this tool was more general with respect to using both the Intel IPP and MKL library routines in the same program. I have not been able to find in the Intel IPP and/or MKL documents guidance in what libraries should be loaded and in what order. It was only after considerable trial and error that I was able to get the right libraries and sequence of loading for one possible configuration of hardware and software that was not usable in another configuration

June 18, 2009 3:57 PM PDT nooj Total Points: 300 Status Points: 250 Green Belt

This is a great idea! Morplzkthx! Could you make it do something like: choose os/compiler/etc choose a desired function (SSYEVD, say) see a compile/link line Because one of my systems got upgraded to MKL 10.3 (I think I am saying this right), and the fortran lapack prototype include files changed names: old new mkl_lapack.f90 lapack.f90 mkl_lapack_protos.f90 lapack_interfaces.f90 mkl77_lapack.mod f77_lapack.mod mkl77_lapack1.mod f77_lapack1.mod

July 7, 2009 9:28 AM PDT michel.devel@univ-fcomte.fr Total Points: 5 Registered User

Great idea !!! Maybe you could add a version for the intel compilers and libraries if link line sometimes changes between versions

September 9, 2009 7:53 AM PDT Tianxing Wang

Great! It helps me much!

October 21, 2009 1:18 PM PDT Mark Borgerding

My company delivers versions of code that has to build and work with multiple versions of intel compilers and MKL. This has proven to be a real pain. This webpage will help make it easier. Thanks. What would be better than a webpage is a link line that doesn't change from version to version. Or at least a script that could could be scripted to make the link line for any recent version. pkgconfig would be a good way to go for future versions. e.g. libmkl_ia32.a was removed in version 11.1 so now there is yet another special case we have to code around.

November 1, 2009 3:54 PM PST heinz Total Points: 180 Status Points: 130 Green Belt

some more feedback: a very helpful tool, I linked it as « Reply #11 on: 03 May 2009, 06:37:49 pm » to the developer forum at Lunatics Thanks for using it. I voted:*****

Trackbacks (0)

Leave a comment