Boost logo

Boost-Build :

Subject: [Boost-build] Not able to use <toolset>gcc-4.6.2-mingw32 any more
From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2014-05-06 08:39:57

I already brought this issue up in thread "Changed behaviour of custom

Unfortunately I was not able to solve it so far. The problem is that if
I require this toolset on the b2 cmd line, just nothing happens, i.e.
no build.
The config.log reads:
Executing raw command directly
Command string for CreateProcessA(): '-ftemplate-depth-128 -O0
-fno-inline -Wall -g -m32 -DBOOST_ALL_NO_LIB=1 -I"." -c -o
CreateProcessA() Windows API failed: 2 - Das System kann die angegebene
Datei nicht finden.

To me this reads as if the compiler is not found, altough
--debug-configuration clearly shows:
notice: will use 'C:/subsys/win32/mingw-4.6.2/bin/g++.exe' for gcc,
condition <toolset>gcc-4.6.2-mingw32
notice: using gcc libraries :: <toolset>gcc-4.6.2-mingw32 ::
C:/subsys/win32/mingw-4.6.2//bin C:/subsys/win32/mingw-4.6.2//lib
C:/subsys/win32/mingw-4.6.2//lib32 C:/subsys/win32/mingw-4.6.2//lib64
notice: using gcc archiver :: <toolset>gcc-4.6.2-mingw32 ::
notice: using gcc ranlib :: <toolset>gcc-4.6.2-mingw32 ::
notice: using rc compiler :: <toolset>gcc-4.6.2-mingw32 ::

What could I look for next? Any hints appreciated!

What puzzles me most is that the 4.6.3 compiler is listed under "primary
test compilers" for the 1.55 version of boost. (can the 4.6.2 difference
really be the cause?)


Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at