Subject: [Boost-bugs] [Boost C++ Libraries] #9485: stdout and stderr not forwarded to respective channels
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-12-10 23:19:46
#9485: stdout and stderr not forwarded to respective channels
-------------------------------------+---------------------------
Reporter: mloskot | Owner: vladimir_prus
Type: Bugs | Status: new
Milestone: To Be Determined | Component: build
Version: Boost Development Trunk | Severity: Problem
Keywords: stderr,stdout |
-------------------------------------+---------------------------
Apparently, Boost.Build does not forward output sent out by commands it
executes to respective channels to which the output is originally sent by
executed commands.
Simple test on Linux seems to prove that:
{{{
$ cat Jamroot
exe testcpp : test.cpp ;
$ cat test.cpp
X main() {}
$ b2 1>/dev/null
$ b2 2>/dev/null
...found 7 targets...
...updating 2 targets...
gcc.compile.c++ bin/gcc-4.8.2/debug/test.o
test.cpp:1:1: error: âXâ does not name a type
X main() {}
^
"g++" -ftemplate-depth-128 -O0 -fno-inline -Wall -g -fPIC -c -o
"bin/gcc-4.8.2/debug/test.o" "test.cpp"
...failed gcc.compile.c++ bin/gcc-4.8.2/debug/test.o...
...skipped <pbin/gcc-4.8.2/debug>testcpp for lack of
<pbin/gcc-4.8.2/debug>test.o...
...failed updating 1 target...
...skipped 1 target...
$
}}}
I've observed the same channel merging in [https://github.com/mloskot/qt-
creator-plugin-boostbuild Boost.Build Plugin for Qt Creator] that I have
been developing.
I asked on IRC about it, and Volodya confirmed channels should not be
merged:
{{{
<volodya> mloskot: I think children stdout and stderr should be forwarded
to stdout and stderr respectively.
}}}
So, I think it is a bug.
-- Ticket URL: <https://svn.boost.org/trac/boost/ticket/9485> Boost C++ Libraries <http://www.boost.org/> Boost provides free peer-reviewed portable C++ source libraries.
This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:15 UTC