On Dec 8, 2008, at 6:12 AM, Amir wrote:
I've been unable to build pycuda for the same reason, boost-python
being linked
to the wrong python. But I am unable to get around it. The desired
python is the
Enthought EPD:
boost_1_37_0 amir$ ./configure
--with-python=/Library/Frameworks/Python.framework/Versions/Current/
bin/python
--with-python-root=/Library/Frameworks/Python.framework/Versions/
4.0.30002
--with-python-version=2.5
boost_1_37_0 amir$ cat user-config.jam
# Boost.Build Configuration
# Automatically generated by Boost configure
# Compiler configuration
using darwin ;
# Python configuration
using python : 2.5 : /Library/Frameworks/Python.framework/Versions/
4.0.30002 ;
http://www.boost.org/doc/libs/1_37_0/libs/python/doc/building.html
tells me that
boost deduces the correct include/lib path from the specified version
(2.5) and or command prefix (.../Versions/4.0.30002).
In your configure command you specify both. You could try dropping the
python-version directive from your configure path. Or manually edit
user-config.jam and remove '2.5' from the version spot.
Hope that helps and if that doesn't i think your better off on the
boost mailing list.
Cheers,
Nicholas
_______________________________________________
PyCuda mailing list
[email protected]
http://tiker.net/mailman/listinfo/pycuda_tiker.net
