[PyCUDA] trouble with pycuda-0.93.1rc2 - test_driver.py, etc.

[Janet Jacobsen]

Hi, Andreas.  I ran

ldd /usr/common/usg/python/2.6.4/lib/python2.6/site-packages
/pycuda-0.93.1rc2-py2.6-linux-x86_64.egg/pycuda/_driver.so

and got
>     libboost_python.so.1.40.0 => 
> /usr/common/usg/boost/1_40_0/pool/lib/libboost_python.so.1.40.0 
> (0x00002b259cac6000)
>     libboost_thread.so.1.40.0 => 
> /usr/common/usg/boost/1_40_0/pool/lib/libboost_thread.so.1.40.0 
> (0x00002b259cd15000)
>     libcuda.so.1 => /usr/lib64/libcuda.so.1 (0x00002b259cf43000)
>     libstdc++.so.6 => /usr/common/usg/gcc/4.4.2/lib64/libstdc++.so.6 
> (0x00002b259d3df000)
>     libm.so.6 => /lib64/libm.so.6 (0x00002b259d6eb000)
>     libgcc_s.so.1 => /usr/common/usg/gcc/4.4.2/lib64/libgcc_s.so.1 
> (0x00002b259d96e000)
>     libpthread.so.0 => /lib64/libpthread.so.0 (0x00002b259db85000)
>     libc.so.6 => /lib64/libc.so.6 (0x00002b259dda0000)
>     libutil.so.1 => /lib64/libutil.so.1 (0x00002b259e0f6000)
>     libdl.so.2 => /lib64/libdl.so.2 (0x00002b259e2fa000)
>     librt.so.1 => /lib64/librt.so.1 (0x00002b259e4fe000)
>     libz.so.1 => /usr/lib64/libz.so.1 (0x00002b259e707000)
>     /lib64/ld-linux-x86-64.so.2 (0x000000316ec00000)
Does this help?

Neither /usr/include/python2.4 nor /usr/include is not part of my
PATH, so it would not seem that I am picking up the headers for
the default version of python.

Thanks,
Janet

P.S. Sorry if this should be off-list, but email sent to
lists at monster.tiker.net is returned to me.


Andreas Klöckner wrote:
> On Freitag 20 November 2009, Janet Jacobsen wrote:
>  
>> Hi, Andreas.  Here's what I get
>>
>>    
>>> % ldd /usr/common/usg/boost/1_40_0/pool/lib/libboost_python.so.1.40.0
>>>     libutil.so.1 => /lib64/libutil.so.1 (0x00002b240c2ca000)
>>>     libpthread.so.0 => /lib64/libpthread.so.0 (0x00002b240c4cd000)
>>>     libdl.so.2 => /lib64/libdl.so.2 (0x00002b240c6e8000)
>>>     librt.so.1 => /lib64/librt.so.1 (0x00002b240c8ed000)
>>>     libstdc++.so.6 => /usr/common/usg/gcc/4.4.2/lib64/libstdc++.so.6
>>> (0x00002b240caf6000)
>>>     libm.so.6 => /lib64/libm.so.6 (0x00002b240ce02000)
>>>     libgcc_s.so.1 => /usr/common/usg/gcc/4.4.2/lib64/libgcc_s.so.1
>>> (0x00002b240d086000)
>>>     libc.so.6 => /lib64/libc.so.6 (0x00002b240d29c000)
>>>     /lib64/ld-linux-x86-64.so.2 (0x000000316ec00000)
>>>       
>
> Turns out you're not missing anything--my libboost_python ldd output 
> looks exactly the same.
>
> Try running this here:
>
> ldd 
> /usr/common/usg/python/2.6.4/lib/python2.6/site-packages/pycuda-0.93.1rc2- 
>
> py2.6-linux-x86_64.egg/pycuda/
>
> and see if this brings up incriminating evidence of mixed versions. 
> Another possibility: You may have two sets of Python headers available 
> on your include path.
>
> HTH,
> Andreas
>