-
Notifications
You must be signed in to change notification settings - Fork 6.8k
MKLDNN header missing in recent mxnet nightly static builds #18120
Comments
I doubt it's caused by the fix in #16857. We have lost the mkldnn header folder since then. For example, in https://repo.mxnet.io/dist/python/mkl/mxnet_mkl-1.6.0b20191205-py2.py3-none-manylinux1_x86_64.whl. |
I think @mseth10 will fix it as part of his work on fixing CD |
The problem seems to persist on the latest nightly builds. mxnet_cu101-2.0.0b20200506-py2.py3-none-manylinux2014_x86_64.whl |
mxnet-cu100==2.0.0b20200509 seems to work:
|
It doesn't work for me. Is there anything to run or install other than pip3 install --pre mxnet-cu102 -f https://dist.mxnet.io/python/cu102 ? |
I can't find the mkldnn folder in the release wheel's either. @eric-haibin-lin where did you get the build from? |
Actually I cannot find it now after i uninstalling mxnet and reinstall https://repo.mxnet.io/dist/python/cu100/mxnet_cu100-2.0.0b20200509-py2.py3-none-manylinux2014_x86_64.whl . Perhaps I didn't remove/cleanup the previous mxnet version correctly previously. |
I looked at the CD pipeline and the mkldnn headers are correctly present at the time of building the wheel. The issue really is that only runs if the variant is named I'll open a PR to fix the setup.py script. |
Only the following files are in the mkldnn folder |
No. It should have the following files:
|
The root cause of this issue is that there are a lot of non-standard hard-coded paths in various places of the installation script. Instead of continuing to maintain and hotpatch these, I suggest to just use the standard process and declare the files that need to be included as cmake Then |
Since mkldnn is turned on by default in Feb, the headers should be included, too
@TaoLv
The text was updated successfully, but these errors were encountered: