You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The install instructions for CUDNN have you add its directory to DYLD_LIBRARY_PATH. Unfortunately, El Capitan changed how that environment variable works: certain executables (maybe everything in /bin?) don't inherit DYLD_* anymore. It has to do with System Integrity Protection, apparently. Unfortunately, since the th command is a #!/bin/sh script, th doesn't inherit the library path and you get
libcudnn (R4) not found in library path.
Please install CuDNN from https://developer.nvidia.com/cuDNN
Then make sure files named as libcudnn.so.4 or libcudnn.4.dylib are placed in your library load path (for example /usr/local/lib , or manually add a path to LD_LIBRARY_PATH)
I hacked around this temporarily by setting the DYLD_LIBRARY_PATH inside~/torch/install/bin/th, but of course that's fragile. It would be great if somehow cudnn.torch could link directly against a CUDNN library so we wouldn't have to patch the linker to find it.
A workaround I haven't tried might be to put cudnn in ~/lib or /usr/local/lib, since those are on the library path by default.
ugh! this has been a horrible move from Apple. I had to deal with some of these after-effects recently.
We'll think of a robust solution against this, like allowing the user to specify the path to the lib at runtime as an option. And thanks for the heads-up.
The install instructions for CUDNN have you add its directory to DYLD_LIBRARY_PATH. Unfortunately, El Capitan changed how that environment variable works: certain executables (maybe everything in /bin?) don't inherit DYLD_* anymore. It has to do with System Integrity Protection, apparently. Unfortunately, since the
th
command is a#!/bin/sh
script,th
doesn't inherit the library path and you getI hacked around this temporarily by setting the DYLD_LIBRARY_PATH inside
~/torch/install/bin/th
, but of course that's fragile. It would be great if somehow cudnn.torch could link directly against a CUDNN library so we wouldn't have to patch the linker to find it.A workaround I haven't tried might be to put cudnn in ~/lib or /usr/local/lib, since those are on the library path by default.
Edit: some additional info from other projects: oracle/node-oracledb#231
The text was updated successfully, but these errors were encountered: