Boost logo

Boost-Build :

From: David Abrahams (dave_at_[hidden])
Date: 2003-02-27 10:45:47

David Abrahams <dave_at_[hidden]> writes:

> OK, patched... :(
> cd c:/boost/tools/build/test/
> python msvc-6.5
> File bin/msvc-6.5/debug/a.obj not touched as expected
> Added files : []
> Removed files : []
> Modified files: ['bin/msvc-6.5/debug/a.exe', 'bin/msvc-6.5/debug/a.exp', 'bin/msvc-6.5/debug/a.lib', 'bin/msvc-6.5/debug/a.obj', 'bin/msvc-6.5/debug/b.exe', 'bin/msvc-6.5/debug/b.obj', 'bin/msvc-6.5/debug/main-target-c/c.exe']
> Touched files : ['bin/msvc-6.5/debug/a.pdb', 'bin/msvc-6.5/debug/a.rsp', 'bin/msvc-6.5/debug/b.pdb', 'bin/msvc-6.5/debug/b.rsp', 'bin/msvc-6.5/debug/main-target-c/c.pdb']
> FAILED test of c:\boost\tools\build\test\..\jam_src\bin.ntx86\bjam -sBOOST_BUILD_PATH=c:\boost\tools\build\test\..\new;c:\boost\tools\build\test -d0 --quiet msvc-6.5
> at line 288 of (fail_test)
> from line 351 of (expect_touch)
> from line 22 of
> Compilation exited abnormally with code 1 at Thu Feb 27 10:34:29

BTW, for debugging this situation it would be very helpful to be able
to run the test from beginning to end with -d+2, so you can see the
full sequence of events. I realize this creates extra output which
might cause the test to fail, so maybe an option which forces all
tests of stdout to pass is needed.

Dave Abrahams
Boost Consulting

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at