New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation clarification for installing MKL on Mac OS X #31

Closed
JulioBarros opened this Issue Sep 12, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@JulioBarros

JulioBarros commented Sep 12, 2017

I stumbled around trying to install MKL and figured out setting DYLD_LIBRARY_PATH on MAC OS X doesn’t work as one might expect anymore because because of system integrity protection (SIP) http://osxdaily.com/2015/10/05/disable-rootless-system-integrity-protection-mac-os-x/

I instead created links from the MKL libs to an existing allowed directory and that seems to work. For example:
ln -s /opt/intel/lib* /usr/local/lib
ln -s /opt/intel/mkl/lib/* /usr/local/lib

This is mentioned the docs (thanks!) but wanted to point out that it may be necessary if you don't want to relax the SIP settings and I thought clearer/stronger suggestion would alert people that this is an option. Thanks again.

@blueberry

This comment has been minimized.

Show comment
Hide comment
@blueberry

blueberry Sep 13, 2017

Member

Added to the docs. Thanks.

Member

blueberry commented Sep 13, 2017

Added to the docs. Thanks.

@blueberry blueberry closed this Sep 13, 2017

@quangquach

This comment has been minimized.

Show comment
Hide comment
@quangquach

quangquach Sep 22, 2017

@JulioBarros Thanks, I think there is a typo in the first command which should have the forward slash / before *

ln -s /opt/intel/lib/* /usr/local/lib
ln -s /opt/intel/mkl/lib/* /usr/local/lib 

quangquach commented Sep 22, 2017

@JulioBarros Thanks, I think there is a typo in the first command which should have the forward slash / before *

ln -s /opt/intel/lib/* /usr/local/lib
ln -s /opt/intel/mkl/lib/* /usr/local/lib 
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment