Nicholas Piël <[EMAIL PROTECTED]> writes: > > 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 >
Thanks Nicholas. I tried a variety of settings but none worked. I manually had to hide the system python framework to build boost properly, and then unhid it. There may be a bug in boost.bjam that is causing the problem, but not sure why it hasn't stopped others: http://groups.google.com/group/boost-list/browse_thread/thread/c2e5b4885e984c8a/83fcd54ce8bbd2af?lnk=gst&q=python+framework#83fcd54ce8bbd2af pycuda built and tested fine afterwards. _______________________________________________ PyCuda mailing list [email protected] http://tiker.net/mailman/listinfo/pycuda_tiker.net
