Re: [boost] Linux regression test results

2002-12-30 Thread Toon Knapen
On Sunday 22 December 2002 20:09, David Abrahams wrote:
 Alkis Evlogimenos [EMAIL PROTECTED] writes:
 For those running regression tests (and most Boost.Build users), I
 really recommend setting ALL_LOCATE_TARGET so that the products of
 your build all go into a single directory tree that's not tangled into
 your source tree.  It makes it much easier, among other things, to
 blow away the old built files.

But AFAIK Beman's post-processing tools don't like that an alternative 
destination is set for the derived objects via ALL_LOCATE_TARGET (unless that 
has changed now too ?)

toon
___
Unsubscribe  other changes: http://lists.boost.org/mailman/listinfo.cgi/boost



Re: [boost] Linux regression test results

2002-12-28 Thread John Maddock

 That's all correct, AFAIK. Exactly what is failing? Did you first delete
 all the bin directories?

If you look at the html table it's pretty obvious: there is no library name
associated with each test, which makes the table more or less impossible to
follow...

John Maddock
http://ourworld.compuserve.com/homepages/john_maddock/index.htm


___
Unsubscribe  other changes: http://lists.boost.org/mailman/listinfo.cgi/boost



Re: [boost] Linux regression test results

2002-12-22 Thread David Abrahams
John Maddock [EMAIL PROTECTED] writes:

 The current Linux regression test results appear to be going a little wrong,
 any idea what's up?

Specifics?

-- 
   David Abrahams
   [EMAIL PROTECTED] * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution

___
Unsubscribe  other changes: http://lists.boost.org/mailman/listinfo.cgi/boost



Re: [boost] Linux regression test results

2002-12-22 Thread Alkis Evlogimenos
On Sunday 22 December 2002 03:51 am, John Maddock wrote:
 The current Linux regression test results appear to be going a little
 wrong, any idea what's up?

I followed the instructions for the merge of the test-sane branch in trunk. I 
recompiled bjam and the regression tools, and pass --dump-tests to bjam when 
running the test suite (should I pass it when I build the libraries too?).

-- 

Alkis

___
Unsubscribe  other changes: http://lists.boost.org/mailman/listinfo.cgi/boost



Re: [boost] Linux regression test results

2002-12-22 Thread David Abrahams
Alkis Evlogimenos [EMAIL PROTECTED] writes:

 On Sunday 22 December 2002 03:51 am, John Maddock wrote:
 The current Linux regression test results appear to be going a little
 wrong, any idea what's up?

 I followed the instructions for the merge of the test-sane branch in
 trunk. 

There should be no special instructions for this, since Beman has
already made the merge.  Just update on the main trunk.

 I recompiled bjam and the regression tools, and pass --dump-tests to
 bjam when running the test suite (should I pass it when I build the
 libraries too?).

That's not neccessary --dump-tests just prints information about the
source files used in all declared tests to stdout.  It's also not
neccessary to separately build the libraries, since they'll be built
automatically as part of the testing procedure.

-- 
   David Abrahams
   [EMAIL PROTECTED] * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution

___
Unsubscribe  other changes: http://lists.boost.org/mailman/listinfo.cgi/boost



Re: [boost] Linux regression test results

2002-12-22 Thread Beman Dawes
At 02:30 PM 12/22/2002, David Abrahams wrote:

Alkis Evlogimenos [EMAIL PROTECTED] writes:

 On Sunday 22 December 2002 03:51 am, John Maddock wrote:
 The current Linux regression test results appear to be going a little
 wrong, any idea what's up?

 I followed the instructions for the merge of the test-sane branch in
 trunk.

There should be no special instructions for this, since Beman has
already made the merge.  Just update on the main trunk.

 I recompiled bjam and the regression tools, and pass --dump-tests to
 bjam when running the test suite (should I pass it when I build the
 libraries too?).

That's not neccessary --dump-tests just prints information about the
source files used in all declared tests to stdout.  It's also not
neccessary to separately build the libraries, since they'll be built
automatically as part of the testing procedure.

That's all correct, AFAIK. Exactly what is failing? Did you first delete 
all the bin directories?

--Beman


___
Unsubscribe  other changes: http://lists.boost.org/mailman/listinfo.cgi/boost