Closed GoogleCodeExporter closed 9 years ago
setup.py does not make any assumptions about where it should find
libcuda.dylib. You
may symlink /usr/local/cuda/lib/libcuda.dylib to /usr/lib/libcuda.dylib like
this:
ln -s /usr/local/cuda/lib/libcuda.dylib /usr/lib/libcuda.dylib
Original comment by lukas.l...@gmail.com
on 25 Aug 2009 at 6:55
Thanks, that did it
Original comment by trobr...@gmail.com
on 25 Aug 2009 at 2:37
Running into a new problem, when I try to build the cpyrit module I get this:
running build
running build_ext
Compiling CUDA module using nvcc 2.3, V0.2.1221...
ptxas info : Compiling entry function 'cuda_pmk_kernel'
ptxas info : Used 42 registers, 8+16 bytes smem, 12 bytes cmem[1]
Building modules...
building 'cpyrit._cpyrit_cuda' extension
creating build
creating build/temp.macosx-10.5-i386-2.5
gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd
-fno-common
-dynamic -DNDEBUG -g -Os -Wall -Wstrict-prototypes -DMACOSX -I/usr/include/ffi
-DENABLE_DTRACE -arch i386 -arch ppc -pipe -I/usr/local/cuda/include
-I/System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 -c
_cpyrit_cuda.c -o build/temp.macosx-10.5-i386-2.5/_cpyrit_cuda.o
-DVERSION="0.2.5-dev
(svn r169)"
creating build/lib.macosx-10.5-i386-2.5
creating build/lib.macosx-10.5-i386-2.5/cpyrit
gcc -Wl,-F. -bundle -undefined dynamic_lookup -arch i386 -arch ppc
build/temp.macosx-10.5-i386-2.5/_cpyrit_cuda.o -lssl -lcuda -lz -o
build/lib.macosx-10.5-i386-2.5/cpyrit/_cpyrit_cuda.so
ld warning: in /usr/lib/libcuda.dylib, missing required architecture ppc in file
Original comment by trobr...@gmail.com
on 25 Aug 2009 at 2:49
The warning can be ignored
Original comment by lukas.l...@gmail.com
on 25 Aug 2009 at 2:54
I tried that and installed the module, then ran pyrit list_cores and it only
listed
my CPU cores, no GPU cores
Original comment by trobr...@gmail.com
on 25 Aug 2009 at 3:23
Also after installing the module I tried this from the Troubleshooting guide:
Traes-MacBook:cpyrit_cuda trobrock$ python -c 'from _cpyrit import _cpyrit_cuda'
Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: cannot import name _cpyrit_cuda
Original comment by trobr...@gmail.com
on 25 Aug 2009 at 3:26
_cpyrit_cuda is part of the package 'cpyrit' so it should read
python -c 'from cpyrit import _cpyrit_cuda'
Original comment by lukas.l...@gmail.com
on 25 Aug 2009 at 3:48
Now getting this:
Traes-MacBook:~ trobrock$ python -c 'from cpyrit import _cpyrit_cuda'
Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: CUDA seems to be unavailable or no device reported.
Guess this would be an issue with my CUDA install on my MacBook correct?
Original comment by trobr...@gmail.com
on 25 Aug 2009 at 6:29
yes it is. Try compiling & running the examples from the SDK
Original comment by lukas.l...@gmail.com
on 25 Aug 2009 at 7:09
Instead of the symlink for libcuda.dylib, you can also pass a search path to
the build script:
stewreo$ LDFLAGS=-L/usr/local/cuda/lib python setup.py build
Original comment by stew...@gmail.com
on 17 Dec 2009 at 12:49
Original issue reported on code.google.com by
trobr...@gmail.com
on 25 Aug 2009 at 4:34Attachments: