-
Notifications
You must be signed in to change notification settings - Fork 64
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
Go get fails with Cuda Toolkit 6.5 installed #37
Comments
Yeah older versions are a pain. No clue how to support them |
@chewxy, thank you for fast response. As I can understand, 8.0 is the oldest toolkit supported, right? |
In an ideal world, we'd want to support as many versions of CUDA as possible. In reality there are constraints. This library started with CUDA 5, it'd be nice to support CUDA 5... but for now I only have the bandwidth to support 8+ |
@chewxy I meet the same problem,i installed CUDA9.2 .but when i run go get -u gorgonia.org/cu, gorgonia.org/cugo\src\gorgonia.org\cu\addressing.go:3:11: fatal error: cuda.h: No such file or directory |
@cobnst Have you added the CUDA include directory to your C_INCLUDE_PATH? |
@cfgt yes |
@cobnst you also need to add a variable for C_INCLUDE_PATH pointing at C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.2\include |
@cfgt thanks a lot ,but there's another error |
@cobnst hm, I'm not sure - maybe try adding C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.2\lib\x64 to LIBRARY_PATH or LD_LIBRARY_PATH |
@cfgt lol it work! thks! |
@cfgt hi do you have some example for kernel func? |
Unfortunately, I don't have any I can share at the moment. |
Hi, im having the same issue:
I have installed CUDA 9.2, all environments are set (cuda bin, libnvvp= and lib/x64 are in PATH) even all other variables in this issue i already set (LIBRARY_PATH, LD_LIBRARY_PATH, C_INCLUDE_PATH). Any idea what is wrong? EDIT:
|
I assume this is on Linux? Have you installed cuDNN? |
I tried install cuDNN. Currently i am getting only these errors:
Is it compatible with CUDA 9.2? EDIT: Its on Windows 7 |
@lupo112 Sorry, got busy at work. Hm, maybe let's go through a few steps - it should be compatible with CUDA 9.2 - I can't confirm however, since I'm using CUDA 10 on my machine at the moment. What version of Go do you have installed? |
Yes, im having installed v6.5, v7.5, v8.0, v9.0 and v9.2. |
It generally looks correct - I don't see any CUDA specific issues - the only major difference between your environment and mine is that I can see if that you are using MinGW directly instead via MSYS2 - so the only thing left I would try would be to installing MSYS2 and installing the mingw toolchain package in it (replace your MinGW in your path) and see if that might resolve the problem. |
No change, again the same problem:
|
Darn - can you check if you have any references to cuda_v7.h or cudnn_v7.h in your src/gorgonia.org/cu directory? Also, can you check that you have cudnn.h and cuda.h in C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v9.2\include? |
In directory In Any idea why they not exist in |
My current guess is that it must have something to do with your environment - it appears to be picking up a <cuda.h> which doesn't have the correct definitions for some reason. Can you try making a generic C file with the following lines:
Then, run |
I tried different setting of variable C_INCLUDE_PATH even simplify the path to use the
But the result is still the same:
|
Hm, still completely mysterious what in your environment is causing this. There may be clues in Maybe try And as a last resort, I guess cloning the source code manually into your go directory and let's see if we can actually build anything. |
I already tried everything and im hopeless now. Here is the output of
And here is the output of
After downloading the repo (master or v0.8.0) i get after
Any idea? |
Yeah, it's really bizarre - I can't come anywhere close to reproducing your error.
|
Hi! I have Cuda Toolkit 6.5 and Cuda Toolkit 8.0 installed on different machines. The package works well with 8.0, but fails with 6.5.
Error stack:
The text was updated successfully, but these errors were encountered: