|
Boost : |
From: David Abrahams (dave_at_[hidden])
Date: 2005-05-15 17:32:46
"Victor A. Wagner Jr." <vawjr_at_[hidden]> writes:
> At 03:23 2005-05-15, David Abrahams wrote:
>>Douglas Gregor <doug.gregor_at_[hidden]> writes:
>>
>> > parameter (vc-7_1, borland-5_6_4, cw-8_3, msvc-stlport, vc7, msvc,
>>
>>Hopefully most of these are fixed now.
>>
>> > A few failures:
>> >
>> > python
>> > (vc-8_0
>> > gcc-3_3-darwin
>> > dmc-stlport
>>
>>These are all configuration errors. The testers should check their
>>configuration variables. Unfortunately I don't know how to see the
>>commands they used to invoke bjam or their environment variables
>
> PYTHON_ROOT=C:\Python24
> PYTHON_VERSION=2.4
>
> and as I commented previously, I cannot run args.py
> C:\Projects\boost\libs\python\test>python args.py
> running...
> **********************************************************************
> File "args.py", line 5, in __main__
> Failed example:
> from args_ext import *
> Exception raised:
> Traceback (most recent call last):
> File "C:\Python24\lib\doctest.py", line 1243, in __run
> compileflags, 1) in test.globs
> File "<doctest __main__[0]>", line 1, in ?
> from args_ext import *
> ImportError: No module named args_ext
>
> and on and on and on for many of the lines bounded by the """ ..... """
> If I remove what appear to be comments, it runs fine
Not a big surprise. Those aren't comments; those are the test cases
;-)
""" ... """
is just one way of writing strings in Python. Strings on the first
line of a function body become documentation, but this string is not
that.
The problem is that one of the DLL dependencies of the .pyd file
(really a dynamically loaded DLL) that gets built is not in the PATH.
For VC8 there's a horrible problem finding MSVC80P.DLL. See
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=9805 for more
information. I managed to get things to build by tracking down the
file and doing the build explicitly and doing
set PATH=c:/windows/WinSxS/x86_Microsoft.VC80.DebugCRT_1fc8b3b9a1e18e3b_8.0.50215.4652_x-ww_a12cf373/;%PATH%
before firing up bjam. Of course, it will probably be in some other
subdirectory of C:\Windows\WinSxS on your machine.
HTH,
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk