• mkl_dss.f77
• mkl_pardiso.f77
• mkl_vml.f77
• mkl_vsl.f77
• mkl_rci.fi

and linking their application with the Intel MKL stdcall (or CVF default) library “mkl_intel_s” can get the following linking error:

"Unresolved external symbols”.

Resolution Status : 

This is a known issue that will be fixed in a future release. To resolve the issue please use the following workaround:

• Use the corresponding f90 headers instead of the f77 headers
• Switch to the PGI* F90 compiler if you use PGI* F77

[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]

Below each error is described in details:

0: no error

-1: Input inconsistency

• Incorrect stage number for PARDISO was called.
• Incorrect PARDISO calling sequence, e.g. run stage > 1 without initialization results in error reporting.
• Incorrect number of matrices to be solved was set (PARDISO can be used for solving several matrices with the same sparsity structure at once, taking into account that their maximum number was defined previously. Setting the number of matrices to be solved outside the range of 1≤ … ≤maxfct results in error).
• PARDISO checks the parameters at each stage for consistency with the parameters at the previous stages. Every disagreement results in error reporting.

-2: not enough memory

This error value is returned in the case of any problem with memory allocation inside PARDISO.

PARDISO messages:

"*** Error in PARDISO memory allocation: [STRUCTURE NAME], size to allocate: %d bytes"

"total memory wanted here: %d kbyte"

"symbolic (max): %d symbolic (permanent): %d"

"real(including 1 factor): %d"

It describes the issue that arises on allocation of STRUCTURE_NAME inside PARDISO. A additional information about current memory usages is also printed.

-3: reordering problem

Returned for any problem on a reordering stage (phase 11)

PARDISO messages:

"*** error PARDISO: reordering, symbolic factorization"

-4: zero pivot, numerical factorization or iterative refinement problem

Let us start with a citation of the Intel MKL manual:

Using phase =33 results in an error message (error =4, should be -4 * ) if the stopping criteria for the Krylow-Subspace iteration cannot be reached.

If phase= 23, then the factors L, U are recomputed for the matrix A and the error flag error=0 in case of a successful factorization. If phase =33, then error = -4 signals the failure

If the solver detects a zero or negative pivot for these matrix types, the factorization is stopped, PARDISO returns immediately with an error (error = -4) and iparm(30) contains the number of the equation where the first zero or negative pivot is detected.

The error returned in the case of any problem at the factorization stage (phase 22) or at the iterative refinement stage of solution.

PARDISO messages:

"*** Error in PARDISO: cgs error iparam(20) %d" – prints iparm(20) – see CG / CGS diagnostics in the Intel MKL manual

"*** error PARDISO: iterative refinement"

" contraction rate is greater than 0.9, interrupt" – rate of contraction is too small

"*** error PARDISO: iterative refinement"

" exceeds max. iteration number %d" - prints abs(iparm(8))

"*** Error in PARDISO: internal error, insufficient memory factorization" – looks like a problem at the factorization stage except for pivoting issues (see errors below)

"*** Error in PARDISO: zero or negative pivot, A is not SPD-matrix" – original matrix (almost) not SPD one (probably due to computer arithmetic inaccuracies)

"*** Error in PARDISO: zero pivot" – the same as above but for other matrix types

-5: unclassified (internal) error

This error value is not used currently and is reserved for the future use.

-6: preordering failed (matrix types 11, 13 only)

This error value is returned in the case of any problem at the stage of preparation for reordering (in matching algorithm).

PARDISO messages:

"*** Error in PARDISO: preordering failed after %d neqns out of %d"

"structure singular or input/parameter problem (matrix type 11,13)"

Looks like the message provides no meaningful information.

-7: diagonal matrix problem

PARDISO prints no messages.

-8: 32-bit integer overflow problem

This error value is returned on 32-bit architecture for big matrices when indices become greater than the maximal integer value on this platform.

PARDISO messages:

"*** error PARDISO: reordering, symbolic factorization"

-9: not enough memory for OOC

Let us start with a citation of the Intel MKL manual:

Note that if iparm(60) is equal to 1 or 2, and the total peak memory needed for strong local arrays is more than MKL_PARDISO_OOC_MAX_CORE_SIZE, the program stops with error -9. In this case, increase of MKL_PARDISO_OOC_MAX_CORE_SIZE is recommended.

This error value is returned when amount of memory available for PARDISO (defined by MKL_PARDISO_OOC_MAX_CORE_SIZE, by default 2000 Mb) is not enough to solve the current matrix. The issue can be resolved by increasing the value for available memory.

-10: problems with opening OOC temporary files

This error value is returned when PARDISO can’t create / open temporary files for storing OOC arrays, e.g. in the case of wrong permissions or when files were removed or blocked or not released after the previous steps.

-11: read/write problems with the OOC data file

This error value is returned when some problems appear in the process of working with files, e.g. in the case of no space left on device or problems with read / write operations because of algorithm issues.

* - the documentation error. Will be fixed in the version 10.3 Update3.

** - available memory means the RAM system's memory which is available at the moment of starting the calculations.

Symptoms

When building with Intel® Math Kernel Library for Windows* version 10.0 using the xilink linker from the command line or within the Microsoft Visual Studio* IDE, the following error messages may occur:

Severe: **Internal compiler error: internal abort** Please report this error along with the circumstances in which it occurred in a Software Problem Report. Note: File and line given may not be explicit cause of this error.
Link: error error_during_IPO_compilation: problem during multi-file optimization compilation (code 3)
Link: error error_during_IPO_compilation: problem during multi-file optimization compilation (code 3) or(0): internal error: backend signals
xilink: error error_during_IPO_compilation: problem during multi-file optimization compilation (code 4)
xilink: error error_during_IPO_compilation: problem during multi-file optimization compilation (code 4)

When using the Intel® C++ Compiler for Windows*, these errors have occurred when the /Qipo compiler option is used with the xilink linker from the command line.

When using the Intel® Visual Fortran Compiler for Windows*, these errors have occurred when building within the Visual Studio IDE, which uses the xlink linker.

Solution

Intel® Math Kernel Library for Windows version 10.0 introduced new library naming conventions, with "dummy lib" references to the older Intel® MKL libraries and were given for backward compatibility. However, there is a format problem with the Intel MKL "dummy libs" files that is causing problems for the Intel xilink tool. Correct the problem by modifying link information for the command line or the Visual Studio link information to specify the new names of the 10.0 Intel MKL libraries.

The dummy or compatibility libraries have been removed from Intel® MKL 10.2 or later versions, and if you using one of the latest versions, this error will not occur.

Linking from the Command Line

When link errors occur, correct the problem by replacing references to the Intel MKL dummy libraries on the link command with explicit references to the libraries listed in the dummy libraries. See the explicit Intel MKL library references listed below.

Linking from within Microsoft Visual Studio

In the Visual Studio IDE, replace the references to the dummy libraries in Project » Configuration Properties » Linker &» Input » Additional Dependencies. See the explicit Intel MKL library references listed below.

For IA-32 Compilers

Intel MKL dummy library Replace with explicit Intel MKL library references mkl_c_dll.lib mkl_intel_c_dll.lib mkl_intel_thread_dll.lib mkl_core_dll.lib mkl_s_dll.lib mkl_intel_s_dll.lib mkl_intel_thread_dll.lib mkl_core_dll.lib mkl_c.lib mkl_intel_c.lib mkl_intel_thread.lib mkl_core.lib mkl_s.lib mkl_intel_s.lib mkl_intel_thread.lib mkl_core.lib mkl_scalapack_dll.lib mkl_scalapack_core_dll.lib mkl_scalapack.lib mkl_scalapack_core.lib mkl_cdft_dll.lib mkl_cdft_core_dll.lib mkl_cdft.lib mkl_cdft_core.lib

For Intel® 64 Compilers

Intel MKL dummy library Replace with explicit Intel MKL library references mkl_dll.lib mkl_intel_lp64_dll.lib mkl_intel_thread_dll.lib mkl_core_dll.lib mkl_em64t.lib mkl_intel_lp64.lib mkl_intel_thread.lib mkl_core.lib.lib mkl_scalapack_dll.lib mkl_scalapack_lp64_dll.lib mkl_scalapack.lib mkl_scalapack_lp64.lib mkl_solver.lib mkl_solver_lp64.lib mkl_cdft_dll.lib mkl_cdft_core_dll.lib mkl_cdft.lib mkl_cdft_core.lib

For IA-64 [Intel® Itanium®] Compilers

Intel MKL dummy library Replace with explicit Intel MKL library references mkl_dll.lib mkl_intel_lp64_dll.lib mkl_intel_thread_dll.lib mkl_core_dll.lib mkl_ipf.lib mkl_intel_lp64.lib mkl_intel_thread.lib mkl_core.lib mkl_scalapack_dll.lib mkl_scalapack_lp64_dll.lib mkl_scalapack.lib mkl_scalapack_lp64.lib mkl_solver.lib mkl_solver_lp64.lib mkl_cdft_dll.lib mkl_cdft_core_dll.lib mkl_cdft.lib mkl_cdft_core.lib

Dummy library removed and recommended solution:
As the claim in Compatibility libraries (also known as dummy libraries) no more available,  since MKL 10.2, we remove the dummy libraries completely. You are strongly encouraged to link Intel MKL library with layered mode.  

Please refer to Intel® Math Kernel Library Link Line Advisor 

or the map table in For easily migrating from Intel® MKL 9.x to 10.x

For some users who may still want to use one library instead of the "complex" combination of layered libraries, you may create the "dummy" library manually.

Intel® MKL for Linux

For example, you had one library libmkl.so from earlier version which worked and you hope keep use the name in your link line or makefile, you can create a "dummy" library manually,

For example, you are using intel compiler, threading mode, lp64 interface, create the dummy library by command

$ vi libmkl.so

add the below text in the fake file

GROUP (-lmkl_intel_lp64 -lmkl_intel_thread -lmkl_core)

Keep it into the MKL library directory.

If you had used static library -lmkl_em64t,    

   $ vi libmkl_em64.a

Add the text

GROUP (libmkl_intel_lp64.a libmkl_intel_thread.a libmkl_core.a)

Keep it into the mkl library directory.

Intel® MKL for windows

In case of Windows you may create c file with the following code:

// dynamic library link

#pragma comment(lib, "mkl_intel_c_dll")
#pragma comment(lib, "mkl_intel_thread_dll")
#pragma comment(lib, "mkl_core_dll")
#pragma comment(lib, "libiomp5md")

 // static library link
//#pragma comment(lib, "mkl_intel_c")
//#pragma comment(lib, "mkl_intel_thread")
//#pragma comment(lib, "mkl_core")
//#pragma comment(lib, "libiomp5md")

void dummy_func_somethingrandom_1234217846()

{ return; }

Compiling this code with any compiler and making lib out of it:

>cl -c mkl_ia32.c

>lib mkl_ia32.obj

The fake function is essential, since in some cases Microsoft Visual Stuio linker can report an error while linking library without any functions in it.

TroubleShooting regarding dummy library: 

1. Problem with Linking Applications to Intel MKL 10.0 for Linux* Dummy Shared Librares
2. Errors linking Intel® compilers with Intel® MKL 10.x
3. "MKL FATAL ERROR: Cannot load neither xxxx" with Intel MKL 10.x
4. If you are link mkl library pure layaered library by configure as below

./configure --mkl_lib='/opt/intel/mkl/10.2.x.0xx/lib/em64t/libmkl_intel_lp64.a
/opt/intel/mkl/10.2.x.0xx/lib/em64t/libmkl_sequential.a
/opt/intel/mkl/10.2.x.0xx/lib/em64t/libmkl_core.a'

Please note the mark '  ' are required.

or vice versa message
This can cause performance degradation.

Cause:

Both libiomp5md.dll and libguide40.dll are Intel OpenMP Runtime library. The libiomp5md.dll is new Intel OpenMP* Compatibility library while the libguide40.dll is legacy OpenMP library. Since Intel® MKL 10.1.0.018 and Intel® Compiler 11.x and later,  the default OpenMP runtime library for Intel MKL has been changed from libguide to libiomp.  Please see <http://software.intel.com/en-us/articles/openmp-support-change/>
 
The error is caused by multiple OpenMP libraries were linked in same application. For example, you have two mkl versions MKL 10 and MKL 10.2.1 are linked in same appliation. The error arises because of the duplicate initialization of OpenMP Runtime library from MKL 10 which link libguide40 and MKL 10.2.1 which use libiomp5md .

Please note, the libguide40.dll sometimes were linked implicitly, e.g. by third-party library, custom dll or by dummy library mkl_c.lib in previous MKL version.

Solution:

Please remove one of them and keep only one OpenMP runtime library.

We recommend using and distributing libiomp5md.dll (located in the \bin directory), as libguide40 will be obsolete.

For the third-party library or custom dll which have used the libguide40.dll from pervious  MKL version, in order to avoid such kind of issue, we strongly recommend rebuild your library with libiomp5md.dll.