From: David Abrahams (dave_at_[hidden])
Date: 2005-05-26 22:35:28
Brian Ravnsgaard Riis <brian_at_[hidden]> writes:
> FWIW, attached is the output for "bjam -d+4".
Well, there's a lot of output missing; you didn't show where the spawn
errors show up. Can you grab *all* the output? If you're redirecting
into a file, add 2>&1 to the end of the command line so stderr goes
in, too. Though I have to say, it looks a little weird that I'm not
even seeing stuff that looks like
Which, AFAK, is supposed to go to stdout. Are you sure you exactly
did "bjam -d+4"? Also, why not make it "bjam -d+2 -d+4"; I could use
the extra output.
Oh, wait... I think I found the bug.
Well, it's definitely *a* bug. We'll see if it's *the* bug. I just
checked in a fix.
Don't bother with the output for now. When Rene checks in his fixes
that allow bjam to be rebuilt again, do a CVS update, rebuild bjam,
and try again please.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
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