Now that we're taking more advantage of PyCUDA's and CodePy's ability
to generate really precise special-case code... I'm finding that we
wind up with a lot of ambiguities about *which* generator should
handle a given special case. The right choice for a particular input
structure is
On Freitag 20 November 2009, James Bergstra wrote:
Now that we're taking more advantage of PyCUDA's and CodePy's ability
to generate really precise special-case code... I'm finding that we
wind up with a lot of ambiguities about *which* generator should
handle a given special case. The right
Hi, Andreas. Thank you for your email.
I did install boost in usr/common/usg/boost. (Though I don't
have root privileges, staff are allowed to install software
under /usr/common.)
The project-config.jam file has in it:
# Boost.Build Configuration
# Automatically generated by bootstrap.sh
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 (0x2b240c2ca000)
libpthread.so.0 = /lib64/libpthread.so.0 (0x2b240c4cd000)
libdl.so.2 = /lib64/libdl.so.2 (0x2b240c6e8000)
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
(0x2b259cac6000)
On Freitag 20 November 2009, Janet Jacobsen wrote:
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 =
Hi, Andreas. Last question, first: when I hit the reply
button, your email address shows up as li...@monster.tiker.net.
I don't have a libpython2.6.so.1.0 in my
/usr/common/usg/python/2.6.4/lib directory, only libpython2.6.a
I ran the vanilla configure/build sequence:
./configure
