diff options
author | Vijay Vasudevan <vrv@google.com> | 2016-06-30 11:13:11 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2016-06-30 11:13:11 -0700 |
commit | 1cebec3782fa5cbcd6dd42cadefe2d5c156837ee (patch) | |
tree | 374e99043432131d9c81288ce94b01bdcfd21fcc /ISSUE_TEMPLATE.md | |
parent | db90885e9f27b1e069dd689ddd2dd3b743ed1cb7 (diff) |
Resolve the libcudnn library to its SONAME, when possible, (#3091)
and build the binary with that SONAME, which is supposed to be
ABI-compatible.
When we build our pip packages, we will now build with precisely
the version of the SONAME that we intend to support with the
binary packages. This is the solution recommended by @3XX0.
Tested by installing cudnn 5.1.3 RC and seeing that the source code
modifications show the use of version "5" (the SONAME version
pointed to by libcudnn.so symlink).
In addition, installing the pip package shows:
>>> import tensorflow as tf
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcublas.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcudnn.so.5 locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcufft.so locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcuda.so.1 locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcurand.so locally
Diffstat (limited to 'ISSUE_TEMPLATE.md')
0 files changed, 0 insertions, 0 deletions