Boost C++ Libraries: Ticket #5680: bootstrap Boost.Build fails with MinGW 20110530: missing sys/wait.h, sys/resource.h, ar.h

severity changed; keywords set

thekyria@… — Tue, 13 Dec 2011 12:45:49 GMT

keywords mingw bjam bootstrap build added
severity Showstopper → Problem

Replying to Alex Millian Hankins <lx_boost@…>:

$ cd boost_1_46_1/tools/build/v2
$ sh bootstrap.sh

As of boost_1_48_0, should instead be (msys):

$ bootstrap.sh mingw

Or (cmd):

> bootstrap.bat mingw

Which would produce the bjam.exe (and b2.exe) you need.

See also: #6143

valentin.perrelle@… — Tue, 06 Mar 2012 17:41:17 GMT

The given solution doesn't work as intended in 1.49. Need to use the --with-toolset option, and substitute gcc by mingw in the produces bjam configuration file :

./bootstrap.sh --with-toolset=mingw
sed -e s/gcc/mingw/ project-config.jam > project-config.jam

Tue, 18 Feb 2014 14:20:35 GMT

It still doesn't work in 1.55.

When bootstrap.sh is run without toolset specified, it first guesses toolset as mingw, but then

  case $guessed_toolset in
[...]
    mingw )
    TOOLSET=gcc
    ;;

so $guessed_toolset is set to mingw but TOOLSET is set to gcc instead, and bootstrap fails while compiling BJAM_SOURCES. Specifying --with-toolset=mingw avoids this substitution, but in jam file gcc must be used.

Here is a patch that makes it work.

bootstrap.sh

-              old
+              new
 if test "x$TOOLSET" = x; then
   guessed_toolset=`$my_dir/tools/build/v2/engine/build.sh --guess-toolset`
   case $guessed_toolset in
     acc | darwin | gcc | como | mipspro | pathscale | pgi | qcc | vacpp )
+    acc | darwin | gcc | como | mipspro | pathscale | pgi | qcc | vacpp | mingw )
     TOOLSET=$guessed_toolset
     ;;
 …
     TOOLSET=intel
     ;;
-    mingw )
-    TOOLSET=gcc
-    ;;
     sun* )
     TOOLSET=sun
     ;;
 …
   mv "project-config.jam" "project-config.jam.$counter"
 fi
+if test "$TOOLSET" = mingw; then
+  TOOLSET=gcc
+fi
 # Generate user-config.jam
 echo "Generating Boost.Build configuration in project-config.jam..."
 cat > project-config.jam <<EOF

anonymous — Sun, 19 Apr 2015 19:41:16 GMT

Seems to be still a problem in 1.58. With the help of your workaround I was able to build under Windows 7 and MinGW.

anonymous — Sun, 19 Apr 2015 20:40:33 GMT

Replying to anonymous:

Seems to be still a problem in 1.58. With the help of your workaround I was able to build under Windows 7 and MinGW.

The sed replacement should go the other way around, though. This is what I used:

sed -i 's/\bmingw\b/gcc/' project-config.jam