[Boost-users] Error messages during configuration checks

Subject: [Boost-users] Error messages during configuration checks
From: Braden McDaniel (braden_at_[hidden])
Date: 2013-04-10 22:03:17

I'm seeing these error messages interspersed with the normal output of the Boost build's configuration checks:

> Performing configuration checks
>     - x86                      : yes
> 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
>     - has_icu builds           : no
> warning: Graph library does not contain MPI-based parallel components.
> note: to enable them, add "using mpi ;" to your user-config.jam
> has_iconv.cpp
> libs\locale\src\..\build\has_iconv.cpp(8) : fatal error C1083: Cannot open include file: 'iconv.h': No such file or directory
>     - iconv (libc)             : no
> has_iconv.cpp
> libs\locale\src\..\build\has_iconv.cpp(8) : fatal error C1083: Cannot open include file: 'iconv.h': No such file or directory
>     - iconv (separate)         : no
> has_icu_test.cpp
> libs\locale\src\..\build\has_icu_test.cpp(12) : fatal error C1083: Cannot open include file: 'unicode/uversion.h': No such file or directory
>     - icu                      : no
> has_icu_test.cpp
> libs\locale\src\..\build\has_icu_test.cpp(12) : fatal error C1083: Cannot open include file: 'unicode/uversion.h': No such file or directory
>     - icu (lib64)              : no
> has_gcc_visibility.cpp
> libs\math\config\has_gcc_visibility.cpp(7) : fatal error C1189: #error :  "This is a GCC specific test case".
>     - gcc visibility           : no
>     - long double support      : yes

I don't recall seeing these when building Boost previously (using the same compiler, Visual C++ 2008); though it's possible I'm misremembering and they're just sticking out more now.

What I have started doing differently is that I'm now calling b2 from a CMake script (via execute_process); but if that's what's triggering this, I don't understand how.

Has anyone here seen this before? How might these error messages be suppressed?

-- 
Braden McDaniel
braden_at_[hidden]