[Boost-testing] Disabling compiler warnings

Subject: [Boost-testing] Disabling compiler warnings
From: Ben Pope (benpope81_at_[hidden])
Date: 2015-04-21 10:49:02

Hi all,

Unused local typedefs generate a lot of noise (nearly half a million 
hits on my run, producing far more lines of noise), is it possible to 
disable them?

My user-config.jam has lines that look like this:
using clang : 3.7~msan~c14_libc++ : clang++-3.7 : <cxxflags>"-std=c++1y 
-stdlib=libc++ -fsanitize=memory -fPIC -Wno-unused-local-typedef" 
<linkflags>"-std=c++1y -stdlib=libc++ -fsanitize=memory -pie -lc++ 
-lc++abi -Wl,-rpath=/home/ben/developmeb2 
cxxflags=-Wno-unused-local-typedef 
--toolset=clang-3.7~msan~c14_libc++nt/llvm/trunk/build/release/projects/compiler-rt/lib/msan/libcxx_msan/lib" 
;

But if I run this:
~/development/boost/test/build/boost_root/libs/atomic/test$ b2 
--toolset=clang-3.7~msan~c14_libc++

I still get unused typedef warnings.

If I run this:
~/development/boost/test/build/boost_root/libs/atomic/test$ b2 
cxxflags=-Wno-unused-local-typedef --toolset=clang-3.7~msan~c14_libc++

The warnings are no more.

There is clearly some kind of ordering to the flags with the command 
line taking precedence over *something*, which takes precedence over the 
toolchain configuration.

But how do I get the warnings disabled when I call run.py?

Thanks,

Ben