-
Notifications
You must be signed in to change notification settings - Fork 86
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
Please allow to use the external mkl-dnn installed as a package #33
Comments
iDeep is fixed on specific MKL-DNN verions and rely it's own API set. If there is any discrepancy between them, things will go wrong. It's possible to detach iDeep building from MKL-DNN, it's head only library, technically it doesn't require "building". So what is your building environment? Can you elaborate it? |
My environment is building FreeBSD packages. ideep currently installs its own version of mkl-dnn. Any other packages that might depend on the |
OK, I'll have a check see if it is solvable. |
@yurivict iDeep brings it's own MKL-DNN which install alongside within python directories, not /usr/local/lib. Other packages that depend on mkl-dnn port won't see the internal one. When dynamic linking I guess one of them will took the place and why would be a conflict? If you determined to use installed mkl-dnn, you could make mkl-dnn install more includes from its external directory, then it'll solve include file problem. |
Here is the list of installed files:
It's not along the python files. |
OK, I'm asking what is your porting strategy. iDeep is a numpy extension enable MKL-DNN acceleration which used inside Chainer, which requires python setup process. However there were head only files could also provide a easier interface for MKL-DNN. Do you want both part? or just C++ API. |
mkl-dnn packages exist on many systems: https://repology.org/project/mkl-dnn/versions
The text was updated successfully, but these errors were encountered: