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
import option ;
import feature ;
# Compiler configuration. This definition will be used unless
# you already have defined some toolsets in your user-config.jam
# file.
if ! gcc in [ feature.values <toolset> ]
{
using gcc : : /usr/common/usg/gcc/4.4.2/bin/gcc ;
}
project : default-build <toolset>gcc ;
# Python configuration
using python : 2.6 : /usr/common/usg/python/2.6.4 ;
# List of --with-<library> and --without-<library>
# options. If left empty, all libraries will be built.
# Options specified on the command line completely
# override this variable.
libraries = ;
# These settings are equivivalent to corresponding command-line
# options.
option.set prefix : /usr/common/usg/boost/1_40_0/pool ;
option.set exec-prefix : /usr/common/usg/boost/1_40_0/pool ;
option.set libdir : /usr/common/usg/boost/1_40_0/pool/lib ;
option.set includedir : /usr/common/usg/boost/1_40_0/pool/include ;
and Python 2.6.4 is the version that I built.
I did a Google search on PyUnicodeUCS4_FromEncodedObject
and got a bunch of hits, so it looks like I should try to
re-compile Python with "unicode support(UCS4)".
Janet
Andreas Klöckner wrote:
Hi Janet,
On Donnerstag 19 November 2009, Janet Jacobsen wrote:
/usr/common/usg/boost/1_40_0/pool/lib/libboost_python.so.1.40.0:
undefined symbol: PyUnicodeUCS4_FromEncodedObject
This looks like the Python against which your boost is linked is different
from the one you're running against. It looks like you're using a system-wide
Boost install (/usr/...)--this would necessarily be linked against a
systemwide Python.
HTH,
Andreas
_______________________________________________
PyCUDA mailing list
[email protected]
http://tiker.net/mailman/listinfo/pycuda_tiker.net
