Opened 12 years ago

Last modified 12 years ago

#4976 new Bugs

boost-jam 3.1.18 + mingw-w64

Reported by: Jarrod Chesney <jarrod.chesney@…> Owned by: Vladimir Prus
Milestone: To Be Determined Component: build
Version: Boost.Jam 3.1.18 Severity: Showstopper
Keywords: build.bat gcc Cc:

Description

my boost-jam 3.1.18 doesn't work with mingw-w64 gcc where my boost-jam 3.1.17 does (using "build.bat gcc")

Error is : C:\devenv\src\boost-jam\3.1.18>build.bat gcc ### ### "Could not find a suitable toolset." ### ### You can specify the toolset as the argument, i.e.: ### .\build.bat msvc ### ### Toolsets supported by this script are: borland, como, gcc, gcc-nocygwin, ### intel-win32, metrowerks, mingw, msvc, vc7, vc8, vc9, vc10 ### ### ### "Could not find a suitable toolset." ###

To reproduce: Download a mingw-w64 toolchain from mingw-w64 at sourceforge. http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/sezero_4.5_20101002/mingw-w32-bin_i686-mingw_20101002_4.5_sezero.zip/download extract somewhere, Add the bin directory in the download to your path change to the boost-jam 3.1.18 src directory execute "build.bat gcc"

To see expected result, use boost-jam 3.1.17 instead.

Change History (3)

comment:1 by Vladimir Prus, 12 years ago

I recall this being discussed on IRC, and the conclusion was that either w64 package, or this specific package of mingw, fails to install gcc or g++, or something like that. Am I wrong?

comment:2 by Jarrod.Chesney@…, 12 years ago

I'm not sure if your wrong about that or not but that isn't the cause of this bug.

I know that mingw-w64 is setup because i changed to my 3.1.17 source and the build.bat command succeeded. And of course I confirmed this by hand as well

comment:3 by René Rivera, 12 years ago

Component: bjambuild
Owner: changed from René Rivera to Vladimir Prus
Note: See TracTickets for help on using tickets.