- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks
Rich
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I know it's annoying if you have to search the libraries to find out where dependencies are satisfied; perhaps constructive suggestions would lead to improved documentation.
The documentation recommends against the static libraries, for a variety of reasons, some of which ought to be fixed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It's true that we appreciate feedback on our documentation. It sounds like we need to remove mention of libmkl_lapack.a from the documentation. I'll make a note of it.
As pointed out, the libraries were rearranged withMKL 10.0. To try to smooth the transition we tried whereever possible to provide linker scripts or "dummy" libraries that load default libraries (the newly named ones) so that users could possibly link to version 10.0 without changing their build scripts. It seems that the LAPACK library was one such compatibility lib that for one reason or another could not be implemented.
As for chasing down dependencies, the "Selecting Libraries to Link" section of chapter 5 in the user guide might be helpful. Let us know how we can improve this too.
Todd
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

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