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

linker warnings with MKL

Witold_Wolski
Beginner
1,059 Views

Platform Win XP, VS 2008.

The project settings are:

Additional Library Dependencies: "$(MKLROOT)lib";"$(IPPROOT)stublib";

Additional Dependencies mkl_intel_c_dll.lib mkl_sequential_dll.lib mkl_core_dll.lib ippcore.lib ipps.lib

They are specified according the MKL and IPP user guide. Still we are getting the following linker warnings...

mkl_core_dll.lib(libimalloc.dll) : warning LNK4006: __NULL_IMPORT_DESCRIPTOR already defined in mkl_sequential_dll.lib(mkl_sequential.dll); second definition ignored

ippcore.lib(ippcore-6.0.dll) : warning LNK4006: __NULL_IMPORT_DESCRIPTOR already defined in mkl_sequential_dll.lib(mkl_sequential.dll); second definition ignored

ipps.lib(ipps-6.0.dll) : warning LNK4006: __NULL_IMPORT_DESCRIPTOR already defined in mkl_sequential_dll.lib(mkl_sequential.dll); second definition ignored

What is the problem?

0 Kudos
3 Replies
TimP
Honored Contributor III
1,059 Views
I suspect the warning (not necessarily a problem) may be due to linking shared MKL libraries together with static IPP libraries.
0 Kudos
Witold_Wolski
Beginner
1,059 Views

The Ipp librariesippcore.lib ipps.lib in$(IPPROOT)stublib are AFAIK the dynamic version.

When linking against both Static MKL and Static IPP (what I would prefer to do)I was getting X*1e4 (!!!!) linker warnings.

I was not able to find any documentation regarding using MKL and IPP in parallel.

0 Kudos
TimP
Honored Contributor III
1,059 Views
The chance of an answer may be greater on the MKL or IPP forum.
0 Kudos
Reply