Thanks again, Andreas. I'm really looking forward to getting started with PyCUDA.
Unfortunately, I've already tried your suggested approach (updating nvcc.profile with NVVMIR_LIBRARY_DIR = /usr/local/cuda-6.5/nvvm/libdevice, which contains libdevice.compute_35.10.bc in my installation), but it did not solve the problem. When I asked NVIDIA about this directly (hoping not to bother you further), they told me I should never need to modify nvcc.profile under any circumstances, which wasn't very helpful. Is there some other line in nvcc.profile that I can modify so that nvcc will be able to find the appropriate libdevice library when called by PyCUDA's compiler script? e.g. perhaps I could append something to the INCLUDES or LIBRARIES variables? Is there an easy way for me to see which environment variables are available when PyCUDA's compiler.py code calls nvcc? This might help diagnose the problem. Thanks, -David > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725649 > > suggests that you may be able to tweak /etc/nvcc.profile. > > HTH, > Andreas >
_______________________________________________ PyCUDA mailing list [email protected] http://lists.tiker.net/listinfo/pycuda
