Boost logo

Boost-Build :

Subject: Re: [Boost-build] Not able to use <toolset>gcc-4.6.2-mingw32 any more
From: Vladimir Prus (ghost_at_[hidden])
Date: 2014-05-14 07:17:45


On 05/06/2014 04:39 PM, Roland Schwarz wrote:
> I already brought this issue up in thread "Changed behaviour of custom generators?"
>
> 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
> "bin.v2\libs\context\config\19050ee0efdd8192e4e25eb06989ff04\arm.o" "C:\Users\RS\OpenSource\boost\boost_1_55_0\libs\context\config\arm.cpp"'
> 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 :: C:/subsys/win32/mingw-4.6.2/bin/ar.exe
> notice: using gcc ranlib :: <toolset>gcc-4.6.2-mingw32 :: c:\subsys\win32\mingw-4.6.2\mingw32\bin\ranlib.exe
> notice: using rc compiler :: <toolset>gcc-4.6.2-mingw32 :: C:/subsys/win32/mingw-4.6.2/bin/windres.exe
> =====
>
> 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?)

Could you provide your user-config.jam?

Thanks,
Volodya


Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk