Re: [Boost-testing] Huang-WinXP-x64 - python - exec

From: David Abrahams (dave_at_[hidden])
Date: 2006-07-13 11:58:09

"Sean Huang" <huangsean_at_[hidden]> writes:

> ----- Original Message ----- 
> From: "David Abrahams" <dave_at_[hidden]>
> Newsgroups: gmane.comp.lib.boost.testing
> Sent: Wednesday, July 12, 2006 7:00 PM
> Subject: Huang-WinXP-x64 - python - exec
>
>
>>
>> http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/output/Huang-WinXP-x64-boost-bin-v2-libs-python-test-exec-test-msvc-8-0-debug-threading-multi_release.html
>>
>> seems to indicate that it's failing to find the PythonXX.dll (where XX
>> is your python version) in g:\Tools\python\libs.  It's either a tester
>> configuration error, or an error in the BBv2 python toolset file.
>> This should be easy for the tester to diagnose, but there's not much I
>> can do without more information.  Can you look into it, Sean?
>>
> Dave,
> OK. Here is what I found out. Those configurations that failed to link all 
> have external symbol references in the format of __imp__Py... (Please note 
> the double underscores after __imp) while those succeeded have only one 
> underscore after __imp. Python24.lib only exports __imp_Py* and that 
> explains the link errors. Unfortunately, I know very little about bjam and 
> do not know what could have caused the differences.

You don't have to know much about bjam; you only need to know how VC++
works.  Just go to 

  libs/python/test,

run 

  bjam -n -a msvc-8.0 exec

and the output will contain all the commands that would be issued to
build and run the test.  You can then look at each one to see if it
makes sense.

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