- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
We are using MKL -2019.0.117 version on both Windows and Linux.
On Windows 10_X64 with intel processor and VC15 compiler, we are facing an issue saying
Intel MKL FATAL Error: dynamic library mkl_vml_avx.dll is not convenient for this processor.
The same issue is not getting reproduced for AMD processors.
Please help us in solving this and please let us know are we missing any specific set of settings like environment variables using MKL for a specific processor.
Note: We are not using SDL link line, we are using the other way.
Thanks.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
>>Note: We are not using SDL link line, we are using the other way.
<< it seems you use some kind of dlopen method... Could you describe how do you link the application?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
we are linking the same way as link line advisor suggests like
mkl_intel_ilp64_dll.lib mkl_intel_thread_dll.lib mkl_core_dll.lib libiomp5md.lib.
If we are using VML/AVX related dlls manually by using a dlopen method or LoadLibrary, should we make any specific settings like enabling AVX instruction set, our processors are capable of AVX instruction set?
or
Are these VML/AVX related DLLs automatically loaded by any other dll at runtime by checking the processor type?
Please explain to us or provide some info on this processor dependent dlls.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
To be on 100% sure, you need to load all mkl dll when using a dlopen method….
Or you may try to load the only mkl_rt.dll and check if you will see the same problem.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page