-
Notifications
You must be signed in to change notification settings - Fork 146
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
Import Error When run convnet.py #17
Comments
Hey, I got the same error. |
I get the same error, have any of you solved it? |
@kashif, any ideas? |
Finally, I use the "Makefile", "build.sh" and "common-gcc-cuda-4.0.mk" from |
@jasonustc can you let me know which version of CUDA and linux distro you are using so I can debug this? thanks! |
My version of CUDA is V6.0.1 and linux destro is ubuntu 14.10, |
@jasonustc great and just using the normal cmake via apt I guess? ok firing up my ubuntu box 🐧 |
Yeah, I just install cmake using the apt-get way... |
@jasonustc sorry ignore my previous comment... can you do the following on your Cmake compiled
and send me the output? |
@jasonustc ok I think i can reproduce the problem... can you add the following line into your main ...
MESSAGE( STATUS "BLAS_LIBRARIES: " ${BLAS_LIBRARIES})
... and then |
@kashif the output of BLAS_LIBRARIES is:
|
@kashif I run
|
Hi guys, I am having the same problem, but I am running openSUSE 12.2 and CUDA 5. and these are the outputs I get:
hope this is of some use. thanks. |
ok so investigating it further it seems the @jasonustc can you make sure since you have One solution might be to have our own |
@jasonustc @windpls @heavyd93 another solution, as stated in the README, is to set the library location explicitly, e.g.:
|
I tried the given CMakeLists.txt and built the _covnet.so successfully, but When I tried to run "python convnet.py ..." . An error arose: Import Error: undefined symbol: cblas_sgemm. It seems that "import("_convnet.so") " in convnet.py can not find the definition of cblas_sgemm. Even after I export the path of "libbblas.so" to "LD_LIBRARY_PATH" , the error still exists. What should I do to solve this problem?
Thanks.
The text was updated successfully, but these errors were encountered: