the sm_30 kernel is still supported, but the build process has issues loading the cuda dlls required for building it., if i had to guess i’d say you have cuda 9.2 installed? downgrade to 9.1 and you should be good to go again!
It should not have tried to use cuew to build with cuda 10, can be a couple of things, outdated master code, i added support for cuda 10 a couple of weeks ago, if you haven’t pulled since then you might miss the code needed.
second option is the WITH_CYCLES_CUBIN_COMPILER is set to ON, check your cmakecache.txt file to validate.
This all being said, cuda10 is broken for sm_30 it makes broken render kernels, and things will look wonky as soon as glass shaders come into play (which is one of the reasons we still ship with 9.1)
it’s not a problem on the blender side, it’s a cuda bug, it’s been dragging on since cuda 9.2 which came out in may sooo… it doesn’t seem like nvidia is in a rush to fix it.
Btw. Would it matter to me /cuda kernel 3.0-gtx760 + Blender/ if I switch back from CUDA 10 to 9.1 anyhow ?
I mean: would I loose any efficiency and/or features with my graphics ?
There were some problems with installing 9.1 afaik…
I noticed that while I can use CUDA 10 to compile on Windows (which renders without visual problems on a 1080ti), it runs slower than when I use CUDA 9.1.
I don’t know if this is true under Linux as well, but at the moment it looks like there’s nothing to be gained from a CUDA version later than 9.1.
We resolved the compiler hostage situation quite a while ago, there’s a cmake option WITH_CYCLES_CUBIN_COMPILER if you turn it on, it’ll use nvrtc to build the kernels, relieving you from being forced into a compiler version nvcc approves of.