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

running caffe with cudnn #191

Closed
mmanco opened this issue Apr 4, 2016 · 6 comments
Closed

running caffe with cudnn #191

mmanco opened this issue Apr 4, 2016 · 6 comments
Labels

Comments

@mmanco
Copy link
Contributor

mmanco commented Apr 4, 2016

I applied a patch which will allow building caffe with USE_CUDNN. The patch resolved the compilation errors but now when running I get an exception java.lang.UnsatisfiedLinkError: /tmp/javacpp681349592249244/libjnicaffe.so: /tmp/javacpp681349592249244/libcaffe.so.1.0.0-rc3: undefined symbol: _ZN5caffe21CuDNNConvolutionLayerIfED1Ev

Any idea what can go wrong here ?

@saudet
Copy link
Member

saudet commented Apr 5, 2016

$ c++filt _ZN5caffe21CuDNNConvolutionLayerIfED1Ev
caffe::CuDNNConvolutionLayer<float>::~CuDNNConvolutionLayer()

Looks like Caffe doesn't export the destructor for that... Sounds like a bug in Caffe?

@mmanco
Copy link
Contributor Author

mmanco commented Apr 6, 2016

We are running equivalent code in cpp against same version of caffe which was compiled aside of javacpp-presets and we don't see any issue. We will try to debug caffe compilation process in javacpp-presets to see maybe some parts are missed during that phase.

@saudet
Copy link
Member

saudet commented Apr 6, 2016

You've made sure to apply explicitly "delete" on one of those objects in your C++ code and it works just fine? Strange... Maybe it's another problem that might arise if we have mismatched defines in the presets..

@mmanco
Copy link
Contributor Author

mmanco commented Apr 6, 2016

The issue resolved by deleting cppbuild dir under caffe preset. For some reason previous builds affected the results of new ones. Just wondering if mvn clean should delete the build working dirs ?

@saudet
Copy link
Member

saudet commented Apr 7, 2016

The previous build affecting the current build, I'd file that as a bug upstream.

As for "mvn clean" calling "bash cppbuild.sh clean", sounds like a good idea! Could you send a PR for that? :)

@mmanco
Copy link
Contributor Author

mmanco commented Apr 7, 2016

@saudet Will do that with pleasure. Actually moving cppbuild under target will do that automatically without the need to call "bash cppbuild.sh clean"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants