- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Using Visual Studio 2008, C++
Trying an "example" to test matrix inversion:
Have pointed linkerto the libraries suggested in the user manual for Math Kernel Library
(mkl_intel_lp64.lib, mkl_intel_thread.lib, mkl_core.lib, libiomp5md.lib)
with help, got a good link.
run time problem .. can't load libiomp5md.dll
Trying an "example" to test matrix inversion:
info = LAPACKE_zgesv( LAPACK_ROW_MAJOR, n, nrhs, a, lda, ipiv, b, ldb );
Seeking a static link.Have pointed linkerto the libraries suggested in the user manual for Math Kernel Library
(mkl_intel_lp64.lib, mkl_intel_thread.lib, mkl_core.lib, libiomp5md.lib)
with help, got a good link.
run time problem .. can't load libiomp5md.dll
Do not know how to get the software to pick up this dll at run time.
Help! Stuck again. New user blues.
Paul Margosian
コピーされたリンク
3 返答(返信)
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
The folder with the required .dll must appear in PATH environment variable, if you're running from command line.
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
a couple of notes:
for the version of MKL bundled with Intel Composer package,all threading libraries ( libiomp5*.libs ) were moved from \ia32\lib to the \lib\ia32 directory.
So, if You have "run time problem .. can't load libiomp5md.dll",
then you have to add the compiler's and mkl's dll directory to the your system's paths.
Namely, for the Intel Composer XE 2011, it would be (for 32 bit case):
<..\ComposerXE-2011\redist\ia32\mkl\> and <..\Intel\ComposerXE-2011\redist\ia32\compiler\>
The same should be noted regarding 64-bit binaries.
--Gennady
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Gennady: Thanks,
You've pretty much got it.
I found an example in some old code that uses lots of dll's.An approach thatworked:
* define a "workingDirectory" (a convenience)
* put copies of needed dll's into it.
* for Visual Studio, under "Configuration properties -> Debugging" .. put in the path to the "working directory".
Just another setup thing .. hard to remember. This one was generic and not special for MKL(aside fromfinding the correct dll's).
Paul Margosian
You've pretty much got it.
I found an example in some old code that uses lots of dll's.An approach thatworked:
* define a "workingDirectory" (a convenience)
* put copies of needed dll's into it.
* for Visual Studio, under "Configuration properties -> Debugging" .. put in the path to the "working directory".
Just another setup thing .. hard to remember. This one was generic and not special for MKL(aside fromfinding the correct dll's).
Paul Margosian