Re: [Boost-build] v2 Python toolset doesn't faithfully reproduce v1

From: David Abrahams (dave_at_[hidden])
Date: 2006-07-13 12:05:20

Vladimir Prus <ghost_at_[hidden]> writes:

> On Thursday 13 July 2006 18:09, David Abrahams wrote:
>> Vladimir Prus <ghost_at_[hidden]> writes:
>> > We've being though this before, and you basically agreed that this
>> > comment is not accurate. Please see the attached message. This topic then
>> > died.
>>
>> Do we need it to un-die, or do you think all the problems are
>> resolved?
>
> I think we need it to un-die. The two current issues are:
>
> 1. I've modified Boost.Python tests Jamfile.v2 to have <threading>multi. I 
> think that fixes the errors, but is not a clean solution. I'd prefer direct 
> linking to pthread.

Why?  For example, do you believe the other options that
<threading>multi might add are inappropriate, and if so, why do you
think that?

> 2. I noticed that in V2 Boost.Python links to Python library. 

Too vague to understand.

* Windows, Unix, both...?

* You mean the boost_python.so/dll links to libpython.a/pythonXX.lib?

> This sounds potentially problematic, I'm not sure if Python
> interpreter will completely hide all symbols from Python shared lib.

Sorry, you lost me completely here.  Whose symbols?  How would a
Python interpreter hide symbols?

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com