- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all,
I am sure someone has already posted this, but I cannot seem to find it. It appears that MKL has a similar issue that IPP once had with its dylibs on Mac OS X. The correct path is not in the library (see below). This causes issues on Mac OS X where it is not always possible (or quite awkward) to set the DYLD_LIBRARY_PATH environment variable (such as for a plugin).
It is not possible for a user to update this, but needs to be done on your end (use -install_name) during the build.
Thanks,
Robert Bell. (www.egi.com)
Below is a comparisson between MKL's libguide and IPP's:
---
MKL's libguide.dylib:
$ otool -L libguide.dylib
libguide.dylib:
libguide.dylib (compatibility version 4.0.0, current version 4.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.6)
---
IPP's libguide.dylib:
$ otool -L libguide.dylib
libguide.dylib:
/Library/Frameworks/Intel_IPP.framework/Versions/5.3/em64t/Libraries/libguide.dylib (compatibility version 4.0.0, current version 4.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.1.3)
Link Copied
5 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you Robert. I'll bring this up with the engineering team. -Todd
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Was there any update on it?
This seems to be an issue with the new Mac OS X 10.11, because the user is not longer allowed to export the DYLD_LIBRARY_PATH variable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Michele,
Thank you much for your notes.
Right, DYLD_LIBRARY_PATH “not allowed” in some cases ( with the new Mac OS 10.11. Please let us know if you run into the problem.
Any MKL/IPP/DAAL team are working for the problem, should be addressed in next release update 2.
Best Regards,
Ying
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
For me the problem occurs in the following cases:
- When I build a Python module that links to MKL.
- When I use CMake with its built-in testing framework. When I use the commander "make test" the OS cannot find the linked MKL library.
For the moment I worked around the problem by making symlinks from /usr/local/lib/libmkl_*.dylib to /opt/intel/mkl/lib/libmkl_*.dylib.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Michele,
Thanks for let us know and sharing the workaround. It looks fine.
Best Regards,
Ying.

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