David Abrahams wrote:
Okay, I'm officially confused. This segment from your original output indicates that the build system is trying (and failing) to delete the RunFailTest executable:
---- del /f/q "..\..\..\bin\boost\libs\statechart\test\RunFailTest.test\mingw\debug\RunFailTest.exe"
...failed RmTemps ..\..\..\bin\boost\libs\statechart\test\RunFailTest.test\mingw\debug\RunFailTest.run... ----
The only reason that should fail is if the executable is missing. Now if I look at the new output, I can trace the steps from creation of that executable up until we try to execute the del command. It clearly gets created and executed, and there's no attempt to delete it before this one.
Very strange indeed. At first I suspected that the virus scanner is interfering but the results are exactly the same if it is disabled. The executable does disappear after execution, BTW.
So if you do
bjam -a -otest.bat -sTOOLS=mingw RunFailTest.run
can you then execute all the commands in test.bat? Does the "del" command work?
I assume you mean bjam -a -otest.bat -sTOOLS=mingw RunFailTest (note the missing .run) When I do that the del command does not end up in the test.bat file, see attached. I used the following command line to make test.bat: bjam "-sTOOLS=mingw" "-sMINGW_ROOT_DIRECTORY=C:\ProgramFiles\MinGW3.2.0" -a -otest.bat RunFailTest I'll try the same stuff tomorrow on my laptop... Thanks, -- Andreas Huber When replying by private email, please remove the words spam and trap from the address shown in the header.