- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I am calling mkl_dimatcopy from C++, using vs2010 on vista. Compiles fine.
Then, when linking against static mkl libs I get an unresolved external symbol for _Mkl_Dimatcopy.
I am linking against:
mkl_intel_c.lib, mkl_intel_thread.lib mkl_core.lib mkl_solver.lib libiomp5md.lib (i am on debug conf), mkl_pgi_thread.lib, libguide.lib and libguide40.lib (btw what are the last three? - how these thread libs would interact collide w/ tbb?)
Thank you for your patience,
P-
I am calling mkl_dimatcopy from C++, using vs2010 on vista. Compiles fine.
Then, when linking against static mkl libs I get an unresolved external symbol for _Mkl_Dimatcopy.
I am linking against:
mkl_intel_c.lib, mkl_intel_thread.lib mkl_core.lib mkl_solver.lib libiomp5md.lib (i am on debug conf), mkl_pgi_thread.lib, libguide.lib and libguide40.lib (btw what are the last three? - how these thread libs would interact collide w/ tbb?)
Thank you for your patience,
P-
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you familiar with the link line advisor? You are using several conflicting libraries and that may be causing some conflicts. mkl_intel_thread.lib is mean to support the Intel OpenMP threading runtime, while mkl_pgi_thread.lib will support PGI's threading runtime. libguide.lib is the Intel static threading runtime while libguide40.lib is the static import lib for the threading runtime DLL. You'll need to pick and choose appropriately and the tool I mention above will help with that.
Todd
Todd
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