From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-09-09 05:56:14
> On Wednesday 08 September 2004 16:49, Vladimir Prus wrote:
> > Hmm... the 'ndebug' failure is most strange -- it never caused
> > problems before. Could you diagnose it:
> > 1. Run
> > python ndebug.py msvc-7.1 --preserve
> > 2. Change to "failed_test" directory
> > 3. Remove the "bin" directory
> > 4. Run "bjam -n".
> I can't run bjam in "failed_test" directory because it complains about
> no toolset's being configured. How can I get bjam to
> use ../test-config.jam ?
The simplest way is to
copy ../test-config.jam project-root.jam
since project-root.jam is empty for this test case.
> > The idea is that all compiles should be done with NDEBUG defined.
> > I'm also suprised with this:
> > custom_generator : FAILED
> > Failure, but no error messages at all. I've modified test_all.py a
> > bit, could you try again?
> Attached, python abort.
I've modified the tester to be more robust. It used to crash when we check
content of a file which does not exist. I think I know why the test failed --
it tried to define type 'RC' which is already defined by 'msvc.jam'. I've
simplified the test and changed the type name, so it should be working now.
Could you rerun the tests when you get the changes?
> > As for railsys failure, it seems to be related to the lack of
> > declspec(dllimport). No wonder, since the test was never run on
> > Windows before. I've corrected that.
> No, this is not the reason because we're linking statically.
> I'll take some time and debug this.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk