Re: [Boost-build] [V2] Testing Tru64 toolset

From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-02-13 06:01:26

On Monday 13 February 2006 13:08, Markus Schöpflin wrote:
> Vladimir Prus wrote:
> > On Friday 10 February 2006 19:14, Markus Schöpflin wrote:
> >> I started with the BBV2 regression tests as outlined in
> >> TestingNewToolset and I got a number of failures. Is this to be
> >> expected? If no, should I send you the log file of the test?
> >
> > Yes, please. Some of the tests are pretty contrived, so their failures
> > might not affect Boost at all. But we can't be sure until we look at the
> > failures.
>
> Attached is the log file of the regression tests.

Thanks.

Some of those failures are spurious and caused by warning message from a 
linker we did not expect. I've fixed that. I think I've also fixed the 
failures of the 'prebuilt' test. Can you run the testsuite again?

There are some failures that are not obvious for me. Those are:

  generators_test
  use_requirements
  library_order

Can you for each of those tests do this:

   ./test_name.py tru64 --preserve
   cd failed_test
   bjam --v2 tru64 -d2 > log 2>&1

and send me the log files? For 'use_requirements' test, I see this:

  Warning version mismatch for shared library libc.so
  a depends on version  and librt.so depends on version osf.1
  Warning version mismatch for shared library libc.so
  a depends on version  and libm.so depends on version osf.1
  Warning version mismatch for shared library libc.so
  a depends on version  and libcxxma.so depends on version osf.1
  Warning version mismatch for shared library libc.so
  a depends on version  and libexc.so depends on version osf.1
  Unresolved:
  exit
  __exc_add_pc_range_table
  __exc_remove_pc_range_table
  __exc_add_gp_range
  __exc_remove_gp_range

I'll look into log file for any suspicious things, but the test does not do 
anything fancy. Any ideas what the warning is trying to say to me?

- Volodya