http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/feed/ en-us > Example: nmake ia32 MKLROOT="c:\program files\intel\mkl\10.1.1.015\ia32\lib" value of MKLROOT environment variable should be reduced to "C:\Program Files\Intel\MKL\RR.r.y.xxx", where RR.r is the version number, y is the release-update number, and xxx is the package number, for example, "C:\Program Files\Intel\MKL\10.1.0.004", otherwise you will get compilation and linkage errors. ]]> http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-22151 Fri, 03 Apr 2009 04:16:09 -0700 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-22151 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-22424 Thu, 09 Apr 2009 21:09:30 -0700 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-22424 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-27668 Thu, 16 Jul 2009 06:32:43 -0700 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-27668 nmake ia32 MKLROOT="C:ProgrammeIntelMKL10.0.1.015" Microsoft (R) Program Maintenance Utility, Version 8.00.50727.42 Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten. Add path of the MKL libraries to the lib environment variable set lib=%MKLROOT%ia32lib;%lib% MKL entries for custom dll Workaround for pardiso Microsoft (R) 32-Bit C/C++-Optimierungscompiler Version 14.00.50727.42 für 80x86 Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten. _fseeki64.c Build MKL custom dll nmake mkl.dll MACHINE=IX86 MKL_LIB="mkl_intel_c_dll.lib mkl_intel_thread_dll.lib mkl_core_dll.lib" MSL Microsoft (R) Program Maintenance Utility, Version 8.00.50727.42 Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten. link /DLL /MACHINE:IX86 /def:user.def _fseeki64.obj mkl_intel_c_dll.lib mkl_intel_thread_dll.lib mkl_cor Microsoft (R) Incremental Linker Version 8.00.50727.42 Copyright (C) Microsoft Corporation. All rights reserved. Bibliothek "mkl.lib" und Objekt "mkl.exp" werden erstellt. mkl_intel_c_dll.lib(_pardiso.obj) : error LNK2019: Verweis auf nicht aufgelöstes externes Symbol "_mkl_solver_pa mkl.dll : fatal error LNK1120: 1 nicht aufgelöste externe Verweise. NMAKE : fatal error U1077: ""C:ProgrammeMicrosoft Visual Studio 8VCBINlink.EXE"": Rückgabe-Code "0x460" Stop. NMAKE : fatal error U1077: ""C:ProgrammeMicrosoft Visual Studio 8VCBINnmake.EXE"": Rückgabe-Code "0x2" Stop. ]]> http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-27669 Thu, 16 Jul 2009 06:33:46 -0700 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-27669 MKL_LIB="mkl_intel_c_dll.lib mkl_intel_thread_dll.lib mkl_core_dll.lib mkl_solver.lib" And replace OMP library: 99c99 < libiomp5md.lib $(MSLIB) /out:mkl.dll --- > libguide40.lib $(MSLIB) /out:mkl.dll It’s better also to run examples on the drive C: The security permission problem can be appeared otherwise: Run dgemm example <…skipped…> Unhandled Exception: System.Security.SecurityException: System.Security.Permissions.SecurityPermission at mkl.CBLAS.dgemm(Int32 Order, Int32 TransA, Int32 TransB, Int32 M, Int32 N, Int32 K, Double alpha, Double[] A, Int32 lda, Double[] B, Int32 ldb, Double beta, Double[] C, Int32 ldc) at test_dgemm.Main(String[] args) Best regards, -Vladimir ]]> http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-27810 Fri, 17 Jul 2009 05:00:17 -0700 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-27810 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-31486 Thu, 24 Sep 2009 09:04:25 -0700 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-31486 C transition, but such a behavior seems strange. Is it expected or have we gone wrong on something? Does C# constrain the use of unmanaged code to only one thread? Best Regards. ]]> http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-31852 Wed, 30 Sep 2009 03:24:50 -0700 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-31852 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-33805 Mon, 02 Nov 2009 03:18:29 -0800 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-33805 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-34516 Wed, 11 Nov 2009 14:26:25 -0800 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-34516 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-34517 Wed, 11 Nov 2009 14:28:06 -0800 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-34517 /tools/builder) and call it via P/Invoke. Thanks, Vladimir ]]> http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-34546 Thu, 12 Nov 2009 00:54:41 -0800 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-34546 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-34649 Fri, 13 Nov 2009 02:43:49 -0800 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-34649 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-34774 Mon, 16 Nov 2009 19:00:49 -0800 http://software.intel.com/en-us/articles/using-intel-mkl-in-your-c-program/#comment-34774