Skip to content
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

Intel MKL FATAL ERROR: Cannot load libmkl_mc3.so or libmkl_def.so. #738

Closed
lesteve opened this issue Apr 7, 2016 · 1 comment
Closed

Comments

@lesteve
Copy link

lesteve commented Apr 7, 2016

Seems very closely related to #698.

Way to reproduce it:

conda create -n mkl -y python numpy scipy
. activate mkl
python /tmp/test.py

where test.py is:

import numpy as np
from scipy import linalg

y = np.ones(2)
nrm2, = linalg.get_blas_funcs(['nrm2'], [y])
nrm2(y)

Output:

Fetching package metadata: ....
Solving package specifications: .........

Package plan for installation in environment /volatile/le243287/miniconda3/envs/mkl:

The following NEW packages will be INSTALLED:

    libgfortran: 3.0-0             
    mkl:         11.3.1-0          
    numpy:       1.11.0-py35_0     
    openssl:     1.0.2g-0          
    pip:         8.1.1-py35_1      
    python:      3.5.1-0           
    readline:    6.2-2             
    scipy:       0.17.0-np111py35_2
    setuptools:  20.6.7-py35_0     
    sqlite:      3.9.2-0           
    tk:          8.5.18-0          
    wheel:       0.29.0-py35_0     
    xz:          5.0.5-1           
    zlib:        1.2.8-0           

Linking packages ...
[      COMPLETE      ]|#########################################################################################################| 100%
#
# To activate this environment, use:
# $ source activate mkl
#
# To deactivate this environment, use:
# $ source deactivate
#
discarding /volatile/le243287/miniconda3/bin from PATH
prepending /volatile/le243287/miniconda3/envs/mkl/bin to PATH
Intel MKL FATAL ERROR: Cannot load libmkl_mc3.so or libmkl_def.so.

@lesteve
Copy link
Author

lesteve commented Apr 7, 2016

Hmmm by the time I created this issue, the problem disappeared somehow. Oh well, sorry for the noise !

@lesteve lesteve closed this as completed Apr 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant