From: David Abrahams (dave_at_[hidden])
Date: 2005-06-13 18:41:56
"Andreas Huber" <ahd6974-spamgroupstrap_at_[hidden]> writes:
> 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
>> ...failed RmTemps
>> 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)
I meant what I wrote. Does it fail to work?
If so, just use the target called "test"
-- 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