On Sat, Apr 13, 2013 at 10:44 AM, Steven Watanabe
AMDG
Anything listed in test_all.py should work.
I'll try again tonight. But do you have any idea for what I should look
for when something isn't working? I know I can run normal python
On 04/13/2013 07:23 AM, Christian Henning wrote: programs.
So it has to do something with the test cases..
So I run test_all.py. Here is the stdout:
and here is the stderr:
It's somewhat funny that zlib.py is the only test passing. Does that maybe ring a bell?
Unfortunately, test_all.py doesn't show the actual errors. The tests appear to be passing for the Windows test runners: http://www.boost.org/development/tests/trunk/developer/build.html Can you try core_language.py? It's the most basic test. If it fails, I wouldn't expect anything to work.
According to the output the error happens testcmd.py at line 409. I added some debug code: sys.stdout.write( "CHH: " + str( cmd ) + "\n") sys.stdout.write( "CHH: " + chdir + "\n") sys.stdout.write( "CHH: " + str( universal_newlines ) + "\n") and the output is: c:\boost\tools\build\v2\test>python core_language.py CHH: ['c:\\boost\\tools\\build\\v2\\test\\..\\engine\\bin.ntx86\\bjam', '-sBOOST _BUILD_PATH="c:\\boost\\tools\\build\\v2\\test/.."', '-d0', '--quiet', '-ftest.j am', '--test-config="c:\\boost\\tools\\build\\v2\\test\\test-config.jam"', '--ig nore-toolset-requirements'] CHH: c:\users\chhenn~1\appdata\local\temp\tmpnz6dv4 CHH: True Does that look reasonable?