- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If I install the MKL using nmake plat=win32e lib and build for the Intel 64 architecture I get the following linker errors:
error LNK2019: unresolved external symbol DGESVD referenced in function DGESVD_MKL95
etc
Has anyone had any experience with this process or this form of error message?
Thanks
George
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's really linking problem.
According to the MKL 10.1User Guide, Linking Applications / Linking Examples
For IA32 architecture:
Static linking of user's code myprog.f, Fortran 95 LAPACK interface, and parallel Intel MKL supporting cdecl interface:
ifort myprog.f mkl_lapack95.lib mkl_intel_c.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib
For Intel 64 architecture:
Static linking of user's code myprog.f, Fortran 95 LAPACK interface, and parallel Intel MKL supporting LP64 interface:
ifort myprog.f mkl_lapack95.lib mkl_intel_lp64.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib
Thanks,
Vladimir
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What MKL version are you using?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's really linking problem.
According to the MKL 10.1User Guide, Linking Applications / Linking Examples
For IA32 architecture:
Static linking of user's code myprog.f, Fortran 95 LAPACK interface, and parallel Intel MKL supporting cdecl interface:
ifort myprog.f mkl_lapack95.lib mkl_intel_c.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib
For Intel 64 architecture:
Static linking of user's code myprog.f, Fortran 95 LAPACK interface, and parallel Intel MKL supporting LP64 interface:
ifort myprog.f mkl_lapack95.lib mkl_intel_lp64.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib
Thanks,
Vladimir
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's really linking problem.
According to the MKL 10.1User Guide, Linking Applications / Linking Examples
For IA32 architecture:
Static linking of user's code myprog.f, Fortran 95 LAPACK interface, and parallel Intel MKL supporting cdecl interface:
ifort myprog.f mkl_lapack95.lib mkl_intel_c.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib
For Intel 64 architecture:
Static linking of user's code myprog.f, Fortran 95 LAPACK interface, and parallel Intel MKL supporting LP64 interface:
ifort myprog.f mkl_lapack95.lib mkl_intel_lp64.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib
Thanks,
Vladimir
Vladimir
Thanks for that - the libiomp5md.lib file and a couple of other files were not required for linking for IA-32 and I missed that
Regards
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page