For starters, what version is your default 'python' - just run 'python' to see - is it 2.5 or 2.6?

Make sure you installed boost with that version of Python. I suspect the fact that you have 2 versions of Python on your system is causing problems (it certainly has for me in the past and still occasionally does). Be aware of the existence of both:
/Library/Frameworks/...  and /System/Library/Frameworks/...

-Randy


On Jun 12, 2009, at 8:55 AM, Massimo Ilario wrote:

Hi,

I removed those 2 (left them blank). Re-installed but I still see the same issue.
I noticed couple of interesting things.

I get 2 different errors whether I run the test as sudo or not:

$ python test_driver.py
Traceback (most recent call last):
  File "test_driver.py", line 3, in <module>
    import pycuda.autoinit
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/ python2.5/site-packages/pycuda-0.92-py2.5-macosx-10.3-i386.egg/ pycuda/autoinit.py", line 1, in <module>
    import pycuda.gpuarray as gpuarray
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/ python2.5/site-packages/pycuda-0.92-py2.5-macosx-10.3-i386.egg/ pycuda/gpuarray.py", line 3, in <module>
    import pycuda.elementwise as elementwise
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/ python2.5/site-packages/pycuda-0.92-py2.5-macosx-10.3-i386.egg/ pycuda/elementwise.py", line 1, in <module>
    import pycuda.driver as drv
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/ python2.5/site-packages/pycuda-0.92-py2.5-macosx-10.3-i386.egg/ pycuda/driver.py", line 1, in <module>
    from _driver import *
ImportError: dlopen(/Library/Frameworks/Python.framework/Versions/ 2.5/lib/python2.5/site-packages/pycuda-0.92-py2.5-macosx-10.3- i386.egg/pycuda/_driver.so, 2): Symbol not found: __ZNK5boost6python7objects21py_function_impl_base9max_arityEv Referenced from: /Library/Frameworks/Python.framework/Versions/2.5/ lib/python2.5/site-packages/pycuda-0.92-py2.5-macosx-10.3-i386.egg/ pycuda/_driver.so
  Expected in: dynamic lookup

$ sudo python test_driver.py

Traceback (most recent call last):
  File "test_driver.py", line 3, in <module>
    import pycuda.autoinit
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/ python2.5/site-packages/pycuda-0.92-py2.5-macosx-10.3-i386.egg/ pycuda/autoinit.py", line 1, in <module>
    import pycuda.gpuarray as gpuarray
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/ python2.5/site-packages/pycuda-0.92-py2.5-macosx-10.3-i386.egg/ pycuda/gpuarray.py", line 3, in <module>
    import pycuda.elementwise as elementwise
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/ python2.5/site-packages/pycuda-0.92-py2.5-macosx-10.3-i386.egg/ pycuda/elementwise.py", line 1, in <module>
    import pycuda.driver as drv
File "/Library/Frameworks/Python.framework/Versions/2.5/lib/ python2.5/site-packages/pycuda-0.92-py2.5-macosx-10.3-i386.egg/ pycuda/driver.py", line 1, in <module>
    from _driver import *
ImportError: dlopen(/Library/Frameworks/
Python.framework/Versions/2.5/lib/python2.5/site-packages/ pycuda-0.92-py2.5-macosx-10.3-i386.egg/pycuda/_driver.so, 2): Library not loaded: @rpath/libcuda.dylib

Referenced from: /Library/Frameworks/Python.framework/Versions/2.5/ lib/python2.5/site-packages/pycuda-0.92-py2.5-macosx-10.3-i386.egg/ pycuda/_driver.so
  Reason: image not found

Also I noticed in the boost library dir that there are 2 gcc versions:
libboost_python-xgcc40-mt-1_39.a
libboost_python-xgcc40-mt-1_39.dylib
libboost_python-xgcc40-mt.a
libboost_python-xgcc40-mt.dylib

In the siteconfig.py I used the 1_39 one. I guess I could try to use the other one. I also have 2 version of Python 2.5 and 2.6. However, the current one is 2.5 which is the only that worked with Numpy.

Also my $DYLD_LIBRARY_PATH has:
/usr/local/cuda/lib:/usr/local/lib:

Thanks,
Massimo


On Fri, Jun 12, 2009 at 7:45 AM, Randy Heiland <heil...@indiana.edu> wrote:
I leave those blank and things work fine for me (OSX 10.5).

-Randy

On Jun 12, 2009, at 8:27 AM, Andreas Klöckner wrote:

Hi Massimo,

I'm mostly clueless about Macs, but I did notice that you built PyCUDA for the
32-bit ABI. Maybe Boost got built against the 64-bit one?


CXXFLAGS = ['-arch','i386']
LDFLAGS = ['-arch','i386']

(Btw, my suspicion is that these shouldn't be needed because PyCUDA (or rather distutils) automatically picks up all the switches that were used to build
Python, anyway.)

On Linux, similar issues are often caused by clashes with system- wide Boost
libraries.

:-? Anyone from the Mac crowd have an idea?

Andreas

<signature.asc><ATT00001.txt>


_______________________________________________
PyCuda mailing list
PyCuda@tiker.net
http://tiker.net/mailman/listinfo/pycuda_tiker.net

<ATT00001.txt>

_______________________________________________
PyCuda mailing list
PyCuda@tiker.net
http://tiker.net/mailman/listinfo/pycuda_tiker.net

Reply via email to