Re: Fw: [boost] Boost.Build problem?

From: bill_kempf (williamkempf_at_[hidden])
Date: 2002-08-22 09:21:28

--- In jamboost_at_y..., "David Abrahams" <dave_at_b...> wrote:
> From: "bill_kempf" <williamkempf_at_h...>
> 
> > > You're right. "clean" is failing to remove some of the testing
> > residue
> > > files. I just fixed that, I think.
> >
> > I just did a cvs update and still see the same results. Did you
> > check the fix in?
> 
> Yes.
> 
> cvs log tools/build/testing.jam

OK, the log does indicate you checked this in twice with comments 
that you've added more files to clean. Here's the results I'm 
seeing, however:

C:\home\boost\libs\thread\test>bjam clean
...found 1 target...
...updating 1 target...
Clean clean
Clean clean
Clean clean
Clean clean
Clean clean
Clean clean
Clean clean
Clean clean
...updated 1 target...

C:\home\boost\libs\thread\test>dir bin /s
Volume in drive C has no label.
Volume Serial Number is 80E5-65E9

Directory of C:\home\boost\libs\thread\test\bin

08/21/2002 03:06 PM <DIR> .
08/21/2002 03:06 PM <DIR> ..
08/21/2002 03:06 PM <DIR> test_base.test
0 File(s) 0 bytes

Directory of C:\home\boost\libs\thread\test\bin\test_base.test

08/21/2002 03:06 PM <DIR> .
08/21/2002 03:06 PM <DIR> ..
08/21/2002 03:06 PM <DIR> vc7
0 File(s) 0 bytes

Directory of C:\home\boost\libs\thread\test\bin\test_base.test\vc7

08/21/2002 03:06 PM <DIR> .
08/21/2002 03:06 PM <DIR> ..
08/21/2002 03:06 PM <DIR> debug
08/21/2002 03:06 PM <DIR> release
0 File(s) 0 bytes

Directory of C:\home\boost\libs\thread\test\bin\test_base.test\vc7
\debug

08/21/2002 03:06 PM <DIR> .
08/21/2002 03:06 PM <DIR> ..
08/21/2002 03:06 PM <DIR> runtime-link-dynamic
08/21/2002 03:06 PM <DIR> runtime-link-static
0 File(s) 0 bytes

Directory of C:\home\boost\libs\thread\test\bin\test_base.test\vc7
\debug\runtim
e-link-dynamic

08/21/2002 03:06 PM <DIR> .
08/21/2002 03:06 PM <DIR> ..
08/22/2002 08:56 AM <DIR> threading-multi
0 File(s) 0 bytes

Directory of C:\home\boost\libs\thread\test\bin\test_base.test\vc7
\debug\runtim
e-link-dynamic\threading-multi

08/22/2002 08:56 AM <DIR> .
08/22/2002 08:56 AM <DIR> ..
08/21/2002 05:34 PM 612,560 test_base.ilk
08/21/2002 05:34 PM 51 test_base.output
08/21/2002 05:34 PM 51 test_base.run
3 File(s) 612,662 bytes

Directory of C:\home\boost\libs\thread\test\bin\test_base.test\vc7
\debug\runtim
e-link-static

08/21/2002 03:06 PM <DIR> .
08/21/2002 03:06 PM <DIR> ..
08/22/2002 08:56 AM <DIR> threading-multi
0 File(s) 0 bytes

Directory of C:\home\boost\libs\thread\test\bin\test_base.test\vc7
\debug\runtim
e-link-static\threading-multi

08/22/2002 08:56 AM <DIR> .
08/22/2002 08:56 AM <DIR> ..
08/21/2002 05:34 PM 1,752,020 test_base.ilk
08/21/2002 05:34 PM 51 test_base.output
08/21/2002 05:34 PM 51 test_base.run
3 File(s) 1,752,122 bytes

Directory of C:\home\boost\libs\thread\test\bin\test_base.test\vc7
\release

08/21/2002 03:06 PM <DIR> .
08/21/2002 03:06 PM <DIR> ..
08/21/2002 03:06 PM <DIR> runtime-link-dynamic
08/21/2002 03:06 PM <DIR> runtime-link-static
0 File(s) 0 bytes

Directory of C:\home\boost\libs\thread\test\bin\test_base.test\vc7
\release\runt
ime-link-dynamic

08/21/2002 03:06 PM <DIR> .
08/21/2002 03:06 PM <DIR> ..
08/22/2002 08:56 AM <DIR> threading-multi
0 File(s) 0 bytes

Directory of C:\home\boost\libs\thread\test\bin\test_base.test\vc7
\release\runt
ime-link-dynamic\threading-multi

08/22/2002 08:56 AM <DIR> .
08/22/2002 08:56 AM <DIR> ..
08/21/2002 05:35 PM 51 test_base.output
08/21/2002 05:35 PM 51 test_base.run
2 File(s) 102 bytes

Directory of C:\home\boost\libs\thread\test\bin\test_base.test\vc7
\release\runt
ime-link-static

08/21/2002 03:06 PM <DIR> .
08/21/2002 03:06 PM <DIR> ..
08/22/2002 08:56 AM <DIR> threading-multi
0 File(s) 0 bytes

Directory of C:\home\boost\libs\thread\test\bin\test_base.test\vc7
\release\runt
ime-link-static\threading-multi

08/22/2002 08:56 AM <DIR> .
08/22/2002 08:56 AM <DIR> ..
08/21/2002 05:35 PM 51 test_base.output
08/21/2002 05:35 PM 51 test_base.run
2 File(s) 102 bytes

Total Files Listed:
10 File(s) 2,364,988 bytes
38 Dir(s) 19,558,844,928 bytes free

I haven't attempted to diagnose why yet.

> > Any chance these are in the plans for V2? Please? ;)
> 
> Relatively speaking, they're so easy that they're not worth 
planning for.
> You could even do them for v1 without too much trouble.

Well, I'm sure you could, but I'm still not very familiar with the 
Jam language ;).

> > OK, that makes sense.
> 
> It still makes no sense to me why only one test is being built.

I'll agree with that, though I may have some more info to help. See 
below.

> > But does this mean there's no way to specify
> > only certain tests be added/run from the command line? For
> > instance, let's say I just want to run test_condition.cpp.
> 
> bjam -sTOOLS=... test_condition

That helps to figure out what may be going on. Here's what I see 
when I try that.

bjam -sTOOLS=vc7 clean
bjam -sTOOLS=vc7 test_thread
Build output you'd expect, though the target is test_base.test
bjam -sTOOLS=vc7 test_condition
C:\home\boost\libs\thread\test>bjam -sTOOLS=vc7 test_condition
...found 556 targets...
...using 4 temp targets...
...updating 4 targets...
...using <libs!thread!test\test_base.test\vc7\debug\runtime-link-
static\threadin
g-multi>test_base.run...
succeeded-test-file ..\..\..\libs\thread\test\bin\test_base.test\vc7
\debug\runti
me-link-static\threading-multi\test_base.test
...using <libs!thread!test\test_base.test\vc7\debug\runtime-link-
dynamic\threadi
ng-multi>test_base.run...
succeeded-test-file ..\..\..\libs\thread\test\bin\test_base.test\vc7
\debug\runti
me-link-dynamic\threading-multi\test_base.test
...using <libs!thread!test\test_base.test\vc7\release\runtime-link-
static\thread
ing-multi>test_base.run...
succeeded-test-file ..\..\..\libs\thread\test\bin\test_base.test\vc7
\release\run
time-link-static\threading-multi\test_base.test
...using <libs!thread!test\test_base.test\vc7\release\runtime-link-
dynamic\threa
ding-multi>test_base.run...
succeeded-test-file ..\..\..\libs\thread\test\bin\test_base.test\vc7
\release\run
time-link-dynamic\threading-multi\test_base.test
...updated 4 targets...

Note that it uses the exact same output directory (i.e. 
test_base.test) and thus nothing happens.

> However, there's clearly a bug somewhere in the interaction of the 
test
> tools with the <template> feature. The issue is that declare-local-
target
> is supposed to return the list of the target files for the target 
it
> builds. However it appears to be returning results of the form
> (<some-grist>test_base.test)*, where test_base is the name of a 
template.

Yes, that does appear to be the case.

I'm surprised that you and I are seeing different results though. 
You did indicate that all the tests run for you?

Bill Kempf