Re: [Boost-build] order of include directories in python extension

Subject: Re: [Boost-build] order of include directories in python extension
From: John Reid (j.reid_at_[hidden])
Date: 2011-02-22 09:51:05

On 22/02/11 14:32, John Reid wrote:
>
> On 21/02/11 19:08, Gevorg Voskanyan wrote:
>> John Reid wrote:
>>
>>>> Try removing<use>/boost/python//boost_python to see if it helps. If you
>> need
>>>> boost_python's other usage requirements (if any), consider
>>>> specifying them
>>>> manually for pyicl_module.
>>>
>>> So I removed<use>/boost/python//boost_python and it didn't compile. Is
>>> there a straightforward way to determine the usage requirements of
>>> /boost/python//boost_python at build-time?
>>
>> I'm almost sure there is a way, just not sure if it's straightforward.
>> No idea
>> what would be the recommended way, but using generate-dependencies
>> rule from
>> targets.jam in an indirect conditional requirements rule would be
>> something I'd
>> try first.
>>
>> Then again you could try applying these usage requirements manually:
>> <link>static:<define>BOOST_PYTHON_STATIC_LIB
>> <python-debugging>on:<define>BOOST_DEBUG_PYTHON
>> , but yes, that might not be the best solution in the long run.
>>
> Thanks. This worked although I had to hard-code the include paths to the
> python installation as well.
>
Sorry I spoke too soon. It is not working. Compiling is fine. At runtime 
I get:

ImportError: 
/home/john/Dev/MyProjects/PyICL/bin/gcc-4.4.3/debug/_pyicl_dynamic.so: 
undefined symbol: _Py_RefTotal

I imagine this is something to do with getting the boost.python usage 
requirements wrong. Does anyone have a better solution to this problem 
than hard-coding all the usage requirements?