From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-07-11 14:27:43
The message that "everything built successfully" on the second bjam run
means that everything you asked it to build that was out-of-date rebuilt
That's true. The .test file wasn't out-of-date, since the last build failed
and you hadn't given it any reason to rebuild. If a failure to build the
.obj file left the test file out-of-date, the test would be re-run every
time you tried to build whether or not you'd changed anything.
That, and the fact that it tries to build the test file even when the .obj
failed to build is an artifact of the fact that the dependency of the test
is marked NOCARE (see testing.jam). It has to build the .test file the
first time, because Beman wants an artifact of the test left behind.
----- Original Message -----
From: "Gennadiy Rozental" <rogeeff_at_[hidden]>
Sent: Thursday, July 11, 2002 3:03 PM
Subject: [boost] Re: Re: strange behavior in testing.jam
> > Nope.
> > How do you know it passed?
> > Can you post the output generated by bjam?
> Hi I found out the reason why my test was failing to compile. But! bjam
> beahvior still strange Here what I was getting after first build:
> ----^ Why is that?
> ***************** failed above test: concept_check_test
> ...failed updating 1 target...
> ...updated 6 targets...
> Without any changes I running the same command again. bjam just says that
> everything is build successfully (that was confused me). While in fact
> nothing is built at all yet.
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk