From: David Abrahams (dave_at_[hidden])
Date: 2007-11-02 16:05:23
on Fri Nov 02 2007, "Robert Ramey" <ramey-AT-rrsd.com> wrote:
> David Abrahams wrote:
>> on Fri Nov 02 2007, "Robert Ramey" <ramey-AT-rrsd.com> wrote:
>>> Well, that makes a lot of sense. But when I build/test with bjam
>>> the tail of bjam.log looks like:
>>> ====== BEGIN OUTPUT ======
>>> assertion "result.second" failed: file
>>> _type_info.cpp", line 75
>>> EXIT STATUS: 34304
>>> ====== END OUTPUT ======
>>> ...updated 32 targets...
>> This looks like a serious bug, assuming you weren't doing a parallel
>> build (in which case the **passed** message might belong to a
>> different test).
> I'm not using a parallel build.
>> Are you using the regular windows command shell to build with a cygwin
> However, my default shell is the MKS Korn shell.
Oh, forget it. That's unsupported. Use cmd, please.
> Given that
> no one else has reported this that might be an issue. I don't
> know how bjam works but I would have thought that it invoked
> the compiler directly rather than through the current shell.
No, it uses the shell, as you can clearly see in the error messages
for failed tests, that are all setting shell variables using
redirection, and chaining with && and ||.
> I can try the the normal DOS-like shell or the cygwin shell if you
> think that would make a difference.
If you use a "windows bjam" (built from the cmd shell) you need to run
it from inside cmd. If you use a "cygwin bjam" (built from cygwin
bash) you need to run it from inside cygwin bash. Those are the only
two options on windows, and Boost.Build doesn't support cygwin at all
anymore, so that may cease to work any day now.
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk