On Mittwoch 29 April 2009, Brent Pedersen wrote: > i dont have _internal.so maybe that's the prob, i have this:
Ah, sorry. _driver.so is correct. My bad. > > $ ldd > /usr/lib/python2.5/site-packages/pycuda-0.92-py2.5-linux-x86_64.egg/pycuda/ >_driver.so linux-vdso.so.1 => (0x00007fffdc3fe000) > libboost_python-gcc42-mt-1_34_1-py26.so.1.34.1 => > /usr/lib/libboost_python-gcc42-mt-1_34_1-py26.so.1.34.1 > (0x00007ff8d3e4e000) > libcuda.so.1 => /usr/lib/libcuda.so.1 (0x00007ff8d39ad000) > libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007ff8d369f000) > libm.so.6 => /lib/libm.so.6 (0x00007ff8d341a000) > libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007ff8d3202000) > libpthread.so.0 => /lib/libpthread.so.0 (0x00007ff8d2fe5000) > libc.so.6 => /lib/libc.so.6 (0x00007ff8d2c73000) > libutil.so.1 => /lib/libutil.so.1 (0x00007ff8d2a70000) > libdl.so.2 => /lib/libdl.so.2 (0x00007ff8d286b000) > librt.so.1 => /lib/librt.so.1 (0x00007ff8d2663000) > libz.so.1 => /lib/libz.so.1 (0x00007ff8d244b000) > /lib64/ld-linux-x86-64.so.2 (0x00007ff8d4367000) Here we go. Your Boost.Python library is compiled (and linked!) against Python 2.6 (see how it says py2.6?). It apparently doesn't like being used within a Python 2.5 interpreter. I'm honestly surprised you just got a spurious error-- it could've easily been a segfault. Andreas
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ PyCuda mailing list [email protected] http://tiker.net/mailman/listinfo/pycuda_tiker.net
