(oops sorry Andreas, the last reply went direct to you I think!). Hello Andreas, thanks for the speedy reply.
No sign of pycuda-helpers.hpp in site-packages/pycuda or site-packages/pycuda/gl (only .py and .pyc files): host47:examples ian$ ls /Library/Python/2.5/site-packages/pycuda/ __init__.py autoinit.pyc cumath.pyc driver.pyc gpuarray.py tools.py __init__.pyc compiler.py curandom.py elementwise.py gpuarray.pyc tools.pyc _driver.so compiler.pyc curandom.pyc elementwise.pyc reduction.py autoinit.py cumath.py driver.py gl reduction.pyc host47:examples ian$ ls /Library/Python/2.5/site-packages/pycuda/gl __init__.py __init__.pyc autoinit.py autoinit.pyc If I look in my local dev tree I see the .hpp: host47:pycuda ian$ pwd /Users/ian/Documents/pycudahead/pycuda host47:pycuda ian$ ls src/cuda/ pycuda-helpers.hpp Are there some files I can manually copy over to force it to work? I'm happy to help test new installers to iron out the problem but I'd love to take a step forwards (if I'm just missing a few copied files) and actually see it running locally. Cheers, Ian. 2010/1/7 Andreas Klöckner <[email protected]> > On Donnerstag 07 Januar 2010, Ian Ozsvald wrote: > > I'm having a devil of a time getting pyCUDA to work on my MacBook and I > > can't get past this error: > > host47:examples ian$ python demo.py > > Traceback (most recent call last): > > File "demo.py", line 22, in <module> > > """) > > File "/Library/Python/2.5/site-packages/pycuda/compiler.py", line 203, > in > > __init__ > > arch, code, cache_dir, include_dirs) > > File "/Library/Python/2.5/site-packages/pycuda/compiler.py", line 188, > in > > compile > > include_dirs = include_dirs + [_find_pycuda_include_path()] > > File "/Library/Python/2.5/site-packages/pycuda/compiler.py", line 149, > in > > _find_pycuda_include_path > > raise RuntimeError("could not find path to PyCUDA's C header files") > > RuntimeError: could not find path to PyCUDA's C header files > > > > Below I have version info and the full build process leading up to the > > error...Any pointers would be *hugely* appreciated. If someone could > > explain what's happening here and what pyCUDA is looking for, that might > > point me in the right direction. > > > > Am I missing something silly? I spent yesterday banging my head against > > the 'make' process until I found a spurious '=' in the > ./configuration.py > > arguments (entirely my fault), maybe I've missed something silly here > too? > > See if you can find pycuda-helpers.hpp under /Library/Python/2.5/site- > packages/ > somewhere, we may need to adapt _find_pycuda_include_path(). It's quite > interesting to see where all this stuff can end up... > > Andreas > -- Ian Ozsvald (Professional Screencaster) [email protected] http://ProCasts.co.uk/examples.html http://TheScreencastingHandbook.com http://IanOzsvald.com + http://ShowMeDo.com http://twitter.com/ianozsvald
_______________________________________________ PyCUDA mailing list [email protected] http://tiker.net/mailman/listinfo/pycuda_tiker.net
