- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a mixed language (C++ and Fortran) 32bit project in VS2005 with Intel 10 and MKL 10 versions. I am calling pardiso from Fortran. I am using /iface:cvf. However, when linking I get
mkl_intel_s.lib(_pardiso_std.obj) : error LNK2019: unresolved external symbol _mkl_solver_pardiso referenced in function _PARDISO@64
Thank you!
1 Solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Gennady Fedorov (Intel)
No, mkl_solver_s.lib contains pardiso symbols:
reading docs (ver. 10.1)
In MKL 10.1 Gold, the DSS/PARDISO* solver functionality was excluded from mkl_solver*.lib libraries and integrated into the Intel MKL layered structure. So, to use DSS/PARDISO, it is no longer necessary to link with mkl_solver*.lib, but the former link line is still working.
I understand that new application(s) should actually link to mkl_core. Right?
A.
Link Copied
5 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Gennady Fedorov (Intel)
No, mkl_solver_s.lib contains pardiso symbols:
reading docs (ver. 10.1)
In MKL 10.1 Gold, the DSS/PARDISO* solver functionality was excluded from mkl_solver*.lib libraries and integrated into the Intel MKL layered structure. So, to use DSS/PARDISO, it is no longer necessary to link with mkl_solver*.lib, but the former link line is still working.
I understand that new application(s) should actually link to mkl_core. Right?
A.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, mkl_core.lib must be used always for linking application with MKL.
For linking sparce solvers functionality you dont need to link these routines without mkl_solver.lib
For example:
for Intel Fortran Compiler:
mkl_intel_c.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib
and for Compaq Visual Fortran* (CVF) compiler:
mkl_intel_s.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib
--Gennady
For linking sparce solvers functionality you dont need to link these routines without mkl_solver.lib
For example:
for Intel Fortran Compiler:
mkl_intel_c.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib
and for Compaq Visual Fortran* (CVF) compiler:
mkl_intel_s.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib
--Gennady
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Gennady Fedorov (Intel)
Yes, mkl_core.lib must be used always for linking application with MKL.
For linking sparce solvers functionality you dont need to link these routines without mkl_solver.lib
For example:
for Intel Fortran Compiler:
mkl_intel_c.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib
and for Compaq Visual Fortran* (CVF) compiler:
mkl_intel_s.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib
--Gennady
For linking sparce solvers functionality you dont need to link these routines without mkl_solver.lib
For example:
for Intel Fortran Compiler:
mkl_intel_c.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib
and for Compaq Visual Fortran* (CVF) compiler:
mkl_intel_s.lib mkl_intel_thread.lib mkl_core.lib libiomp5md.lib
--Gennady
In your For example section above, if I am using the VC2005 C++ linker and not the Intel Fortran one (because I am using a VS2005 mixed C++/Fortran project), which set should I be using please? One of the above or something different?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - tgarratt@reactiondesign.com
In your For example section above, if I am using the VC2005 C++ linker and not the Intel Fortran one (because I am using a VS2005 mixed C++/Fortran project), which set should I be using please? One of the above or something different?
Adding mkl_solver.lib solved my problem. I am using MKL 10.0.025.
As a general comment to Intel, I find the MKL documentation, especially on the topic of which libraries to include, not very clear at all - the whole section could do with a re-write.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If you have a more precise sets recommendations, suggestions about improving documentation, Id recommend you submit the issue against MKL to Premier support( https://premier.intel.com/ )
--Gennady
--Gennady

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