Boost logo

Boost-Build :

Subject: [Boost-build] Debug Python extension build doesn't select debug Python
From: John Reid (j.reid_at_[hidden])
Date: 2011-03-16 09:16:37


My debug Python extension builds do not seem to select the correct
python I have built with debugging on.

This is my user-config.jam:

using python ;
using python : : /home/john/local/python-dbg/bin/python2.7
         :
         :
         : <python-debugging>on
         ;

I go to $BOOST_ROOT/libs/python/example and do
bjam -q -j3 debug -d+2

I get a bunch of compilation lines like:

gcc.compile.c++ bin/gcc-4.4.3/debug/python-debugging-on/getting_started1.o

     "g++" -ftemplate-depth-128 -O0 -fno-inline -Wall -g -fPIC
-DBOOST_DEBUG_PYTHON -I"../../.." -I"/usr/include/python2.6" -c -o
"bin/gcc-4.4.3/debug/python-debugging-on/getting_started1.o"
"getting_started1.cpp"

where /usr/include/python2.6 is included, not the headers for my python
2.7 debug build. I think this used to work, I have recently updated
boost to the latest svn. Can anyone verify if this has stopped working
for them also?

Thanks,
John.


Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk