MinGW version 'mingw-x.y.z' requested but 'g++-mingw-x.y.z' not found and version 'x.y.z' of default 'g++' does not match

[Jim Bell <jim@…>]

MinGW's version may be prefixed with 'g++-', and failing to match this variation causes many tests to fail.

.../trunk/boost/tools/build/v2/tools\gcc.jam:106: in gcc.init from module gcc
error: toolset gcc initialization:
error: version 'mingw-4.3.3' requested but 'g++-mingw-4.3.3' not found
   and version '4.3.3' of default 'g++' does not match

[Jim Bell <jim@…>]

mingw g++ -dumpversion returns '4.3.3', but the version string passed into the rule has the 'mingw-' prefix attached, to it fails to match '4.3.3'.

g++ -dumpmachine returns 'mingw32'

[Vladimir Prus]

Jim, I don't understand what's going on here. This error message should be only emitted if you have

using gcc : mingw-4.3.3 ;

in user-config.jam, without any command. Is that the case? If so, why are you specifying a version at all?

[Jim Bell <jim@…>]

It's acting as though that were the case, but my ./tools_bb/user-config.jam has only this un-commented:

using gcc ;

It must be inserting the mingw somewhere, but I couldn't figure out where. Could we patch my test to try to trace it?

[Jim Bell <jim@…>]

Notice, too, the command-line ​here:

---

"['bjam', '-sBOOST_BUILD_PATH="F:\\tmp\\boost-MinGW-32\\trunk\\boost\\tools\\build\\v2\\test/.."', '-d0', '--quiet', 'toolset=gcc-mingw-4.3.3', '--test-config="F:\\tmp\\boost-MinGW-32\\trunk\\boost\\tools\\build\\v2\\test\\test-config.jam"', '--ignore-toolset-requirements']" returned 1

---

It's passing in gcc-mingw-4.3.3 which doesn't exactly match anything on the error message on line 106.

I'm submitting a patch for build-system.jam that filters out the '-mingw' explicitly. You might not like it, but it does get past line 106.

[Jim Bell <jim@…>]

I'm more and more convinced that this patch is the real fix.

One mystery solved: the regression test passes the toolset into test_all.py on the command-line, as such:

---

"C:\Software\Open\Python\python.exe" test_all.py --default-bjam --xml gcc-mingw-4.4.0 1>F:\boost\MinGW-32\trunk\results\boost-build-gcc-mingw-4.4.0\test_log.xml

---

Called without a toolset, it defaults to just "gcc" and works fine. This solves ​http://lists.boost.org/Archives/boost/2010/12/173676.php.