- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I have installed the version 11.0.069 of Intel Fortran compiler and the version 10.1.0.015 of the MKL library.
I am building my Fortran application without neither compilation nor linking error messages the following way:
ifort ci.f90 -o ci.x *.o -lmkl_lapack -lmkl_ia32 -lguide -lmkl_intel_thread -lmkl_core -lpthread
The final task of this calculation is the diagonalization of a symmetric matrix by using the subroutine DSYEVD from lapack and I am getting the following running time message: MKL FATAL ERROR on load the function dll_cpu_version
Please, I will appreciate any help/advice on that.
Thanks and regards,
Alain Delado.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Alain,
you probably need tocheck the LD_LIBRARY_PATH environment variable that shoud contain the path to MKL binaries.
You may try different link line as well which is more direct:
ifort ci.f90 -o ci.x *.o -lmkl_intel -Wl,--start-group -lmkl_intel_thread -lmkl_core -Wl,--end-group -lguide -lpthread
Michael.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Michael,
Thank you very much for your help, now it is working perfect. I appreciate it.
Best regards,
Alain.
Hello Alain,
you probably need to check the LD_LIBRARY_PATH environment variable that shoud contain the path to MKL binaries.
You may try different link line as well which is more direct:
ifort ci.f90 -o ci.x *.o -lmkl_intel -Wl,--start-group -lmkl_intel_thread -lmkl_core -Wl,--end-group -lguide -lpthread
Michael.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
for windows:
MKLROOT=C:AppsIntelMKL10.1
and for Linux:
The same for MacOS
--Gennady
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
and for Linux:
The same for MacOS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You haven't given us an idea which file you can't find. Show us the command you enter and the error message.
In the 11.x combined compiler and MKL distributions, the environment variable scripts are in the top level /bin directory, and they set LD_LIBRARY_PATH for all installed components.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ning.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You haven't given us an idea which file you can't find. Show us the command you enter and the error message.
In the 11.x combined compiler and MKL distributions, the environment variable scripts are in the top level /bin directory, and they set LD_LIBRARY_PATH for all installed components.
MKL FATAL ERROR on load the function dll_cpu_version
rank 0 in job 8 node1_43986 caused collective abort of all ranks
exit status of rank 0: return code 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
for linking with em64 libraries you have to use another linking libs versus ia32.
as an example, see below how to do static linking customers code with Lapack functionality on system based on Intel 64 architecture:
ifort -w test.f ${MKLP}/libmkl_intel_lp64.a -Wl,--start-group ${MKLP}/libmkl_intel_thread.a ${MKLP}/libmkl_core.a -Wl,--end-group -L${MKLP}
-iomp5 -lpthread -o test.out
--Gennady
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
for linking with em64 libraries you have to use another linking libs versus ia32.
as an example, see below how to do static linking customers code with Lapack functionality on system based on Intel 64 architecture:
ifort -w test.f ${MKLP}/libmkl_intel_lp64.a -Wl,--start-group ${MKLP}/libmkl_intel_thread.a ${MKLP}/libmkl_core.a -Wl,--end-group -L${MKLP}
-iomp5 -lpthread -o test.out
--Gennady
Thankyou very much.
Best regards,
Ning.

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