id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
9485	stdout and stderr not forwarded to respective channels	Mateusz Loskot	Vladimir Prus	"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.
"	Bugs	new	To Be Determined	build	Boost Development Trunk	Problem		stderr,stdout