On 07.04.2014 21:27, Steven Watanabe wrote:

AMDG

The fact the the gcc toolset automatically sets
the flavor to mingw has several unfortunate
consequences:
- MinGW does not interact well with non-mingw (such
   as cygwin or when running mingw as a cross compiler.),
   without extra work, because <toolset-gcc:flavor>mingw
   becomes the default.
- The Boost.Build tests are failing because of the
   failure to parse gcc-mingw-4.5.4 when the toolsets
   are not declared in user-config.jam.

I propose simply removing this behavior.

I searched the Boost tree and the only place I
could find that refers to <toolset-gcc:flavor>mingw
is common.format-name which uses mgw instead of gcc
as the toolset name.  This check can be changed to
use <target-os>windows instead.

Any objections?

No objections, this plan looks good to me.