Hello:

Debian GNU/Linux amd64 wheezy, intel i7-3930K and two GTX-680, runs without problems on installation of "build-essential"
"nvidia-kernel-dkms" and "nvidia-xconfig". I could also run
successfully binary CUDA-enabled computational codes, adding libcudart.so.4 aside the binary.

Now, in order to include special plugins, I am trying to compile the CUDA-enabled computational codes from source. The plugins were correctly patched, multicore correctly compiled, whereas the final "make" awaits to see a non-existing "/usr/local/encap/cuda-4.0/include".

My question is related to the above Debian-way of getting the nvidia driver. What I fear in going now to nvidia-cuda web, is a conflict with the above. I posed the question to Debian, so far getting no help. On the web, I got submerged by Ubuntu posts, a common situation that Debian users are suffering. Having set Ubuntu as spam does not relieve much.

To progress a little, I have now installed "nvidia-cuda-dev" and "libnvidia-compiler", whereby the nvidia compiler, nvcc, is now available at /usr/bin/nvcc.


Now,

francesco@....:~$ dpkg -l | grep nvidia
ii glx-alternative-nvidia 0.2.2
amd64 allows the selection of NVIDIA as GLX provider
ii libgl1-nvidia-alternatives 304.64-4
amd64 transition libGL.so* diversions to
glx-alternative-nvidia
ii libgl1-nvidia-glx:amd64 304.48-1
amd64 NVIDIA binary OpenGL libraries
ii libglx-nvidia-alternatives 304.64-4
amd64 transition libgl.so diversions to
glx-alternative-nvidia
ii libnvidia-compiler:amd64 304.64-4
amd64 NVIDIA runtime compiler library
ii libnvidia-ml1:amd64 304.48-1
amd64 NVIDIA management library (NVML) runtime library
ii nvidia-alternative 304.48-1
amd64 allows the selection of NVIDIA as GLX provider
ii nvidia-cuda-dev 4.2.9-2
amd64 NVIDIA CUDA development files
ii nvidia-cuda-doc 4.2.9-2
all NVIDIA CUDA and OpenCL documentation
ii nvidia-cuda-gdb 4.2.9-2
amd64 NVIDIA CUDA GDB
ii nvidia-cuda-toolkit 4.2.9-2
amd64 NVIDIA CUDA toolkit
ii nvidia-glx 304.48-1
amd64 NVIDIA metapackage
ii nvidia-installer-cleanup 20120630+3
amd64 Cleanup after driver installation with the
nvidia-installer
ii nvidia-kernel-common 20120630+3
amd64 NVIDIA binary kernel module support files
ii nvidia-kernel-dkms 304.48-1
amd64 NVIDIA binary kernel module DKMS source
ii nvidia-libopencl1:amd64 304.64-4
amd64 NVIDIA OpenCL library
ii nvidia-opencl-dev 4.2.9-2
amd64 NVIDIA OpenCL development files
ii nvidia-settings 304.64-1
amd64 Tool for configuring the NVIDIA graphics driver
ii nvidia-smi 304.48-1
amd64 NVIDIA System Management Interface
ii nvidia-support 20120630+3
amd64 NVIDIA binary graphics driver support files
ii nvidia-vdpau-driver:amd64 304.48-1
amd64 NVIDIA vdpau driver
ii nvidia-visual-profiler 4.2.9-2
amd64 NVIDIA Visual Profiler
ii nvidia-xconfig 304.48-1
amd64 X configuration tool for non-free NVIDIA drivers
ii xserver-xorg-video-nvidia 304.48-1
amd64 NVIDIA binary Xorg driver
francesco@gig64:~$


Ho to get a NON-CONFLICTING /usr/local//encap/cuda-4.0/include, or other location, to be nindicated by "--cuda-prefix..." in the
configuration of the code? As far as I know, it should be available from the cuda SDK directory structure.

Thanks a lot
chiendarret

With the above packages,

/usr/include/cuda_untime.h
/usr/include/cuda.h

etc for cuda-related headers.

Question?

is now

--cuda-prefix /usr/inclde

appropriate? (The compiler was looking for /usr/local/encap/cuda4.0/include)

Thanks
chiendarret