|
Boost-Build : |
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2007-12-03 10:21:41
Martin Kortmann wrote:
> I have seen that stdout and stderr of started commands are
> piped into different pipes. These two pipes will be readed
> in the sequence stdout, stderr (function read_output).
> This results into an irritating effekt: When the started
> command outputs something to stdout, then an error message
> to stderr and finally smething other to stdout, then the
> error messages are printed after all stdout messages, the
> sequence of these messages are lost. Could this be changed?
Do you have a test case where this happens? I ask because we test for
that specific situation currently in one of the bjam tests. With default
options stdout and stderr are actually the same pipe, and hence the
output is merged in order. Or at least that's the intent.
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
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