[Boost-build] [config] Boost.Build Configuration tests incorrectly showing up on the console

Subject: [Boost-build] [config] Boost.Build Configuration tests incorrectly showing up on the console
From: John Maddock (boost.regex_at_[hidden])
Date: 2010-12-14 11:51:42

Just a heads up that any configuration checks that are run now seem to have 
their error messages show up on the console instead of being silently 
directed to file:

common.mkdir ..\..\..\bin.v2
common.mkdir ..\..\..\bin.v2\libs
common.mkdir ..\..\..\bin.v2\libs\regex
common.mkdir ..\..\..\bin.v2\libs\regex\build
common.mkdir ..\..\..\bin.v2\libs\regex\build\msvc-10.0
common.mkdir ..\..\..\bin.v2\libs\regex\build\msvc-10.0\debug
common.mkdir 
..\..\..\bin.v2\libs\regex\build\msvc-10.0\debug\threading-multi
compile-c-c++ 
..\..\..\bin.v2\libs\regex\build\msvc-10.0\debug\threading-multi\has_icu_test.obj
has_icu_test.cpp
..\..\..\libs\regex\build\has_icu_test.cpp(12) : fatal error C1083: Cannot 
open include file: 'unicode/uversion.h': No such file or directory

    call "c:\Program Files\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" 
x86 >nul
cl /Zm800 -nologo 
@"..\..\..\bin.v2\libs\regex\build\msvc-10.0\debug\threading-multi\has_icu_test.obj.rsp"

...failed compile-c-c++ 
..\..\..\bin.v2\libs\regex\build\msvc-10.0\debug\threading-multi\has_icu_test.obj...
...skipped 
<p..\..\..\bin.v2\libs\regex\build\msvc-10.0\debug\threading-multi>has_icu.exe 
for lack of 
<p..\..\..\bin.v2\libs\regex\build\msvc-10.0\debug\threading-multi>has_icu_test.obj...
...failed updating 1 target...
...skipped 1 target...
...updated 7 targets...
...skipped 
<p..\..\..\bin.v2\libs\regex\build\msvc-10.0\debug\threading-multi>has_icu.pdb 
for lack of 
<p..\..\..\bin.v2\libs\regex\build\msvc-10.0\debug\threading-multi>has_icu_test.obj...
...skipped 1 target...
Performing configuration checks

    - has_icu builds           : no

Note that the problem seems to be restricted to when the directory structure 
for the config-tests is not present, once that has been created then 
subsequent runs do silence the output.

Regards, John.