Note that there are some explanatory texts on larger screens.

plurals
  1. POCUDA on Fedora compilation failure
    primarykey
    data
    text
    <p>After looking at installing CUDA 5.0 on my new Fedora19 system, I found that CUDA 5.5 was a better candidate, as it came in an rpm format. I followed the directions for installation found <a href="http://developer.download.nvidia.com/compute/cuda/repos/howto_install_cuda_rpm_packages.txt" rel="nofollow">here</a>, and everything was going great until I attempt to compile the samples. First off, it installs the samples to /usr/local/cuda/samples, and I had to make sure that my LD_LIBRARY_PATH included /usr/local/cuda/lib (not just the 5.5 version), but then I get the following two errors when I attempt to run the 'make all' command.</p> <pre><code>../../common/inc/exception.h: In constructor ‘Exception&lt;Std_Exception&gt;::Exception()’: ../../common/inc/exception.h:129:94: warning: delegating constructors only available with -std=c++11 or -std=gnu++11 [enabled by default] Exception&lt;Std_Exception&gt;::Exception() : </code></pre> <p>I thought that C++11 was the default version? And then when I get to trying to compile the matrixMulDrv, I get the following error that really makes no sense:</p> <pre><code>/usr/local/cuda-5.5/bin/nvcc -ccbin g++ -m64 -o matrixMulDrv matrixMulDrv.o -L/usr/lib64/nvidia -lcuda /bin/ld: cannot find -lcuda collect2: error: ld returned 1 exit status </code></pre> <p>I was wondering if anybody else had any problems of this nature. I had moved to 5.5 so that I could use the current gcc compilers (4.8.1). When I look in /usr/lib64/nvidia, I see all of the files I supposedly need, including libcuda.so.1. Has anybody else seen this?</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload