Bootstraping on Windows using MinGW hangs

[Björn Pollex <bjoern.pollex@…>]

I have Boost 1.47 and 1.48 downloaded. I execute the following command in the root of version 1.47:

bootstrap.bat mingw

And get this output:

Building Boost.Build engine

Bootstrapping is done. To build, run:

    .\b2

To adjust configuration, edit 'project-config.jam'.
Further information:

    - Command line help:
    .\b2 --help

    - Getting started guide:
    http://boost.org/more/getting_started/windows.html

    - Boost.Build documentation:
    http://www.boost.org/boost-build2/doc/html/index.html

All is well. Running the same command in the root directory of 1.48 results in the script hanging. It does write output to bootstrap.log, the following lines repeated endlessly:

###
### "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
###

A diff shows no differences between bootstrap.bat and build.bat of either version.

[thekyria@…]

Build log

[thekyria@…]

Replying to Björn Pollex <bjoern.pollex@…>:

Running the same command in the root directory of 1.48 results in the script hanging. It does write output to bootstrap.log, the following lines repeated endlessly:

In boost_1_48_0 the following works ok with me (compiling with MSVC):

C:\boost\boost_1_48_0>b2 install --build-type=complete

If you want to compile using gcc, e.g. mingw as you mention, then you should include 'toolset=gcc' in your b2 command. The following works ok compiling thread lib:

C:\boost\boost_1_48_0>b2 --build-dir=C:\boost-build --with-thread --build-type=complete toolset=gcc

However, trying to compile everything still fails:

C:\boost\boost_1_48_0>b2 --build-dir=C:\boost-build --build-type=complete toolse
t=gcc stage

See attachment for output; maybe I should start a new ticket for that.

[p.jackson@…]

I'm having a similar problem to Björn but only on Windows XP.

I noticed that the line endings for this file changed in the 1.48 release: tools\build\v2\engine\build.bat

I think this could be causing the problem because changing the file to Windows line endings (which is what bootstrap.bat uses) fixes the problem.

I've attached a patch for completeness.

[p.jackson@…]

Replying to p.jackson@…:

I've attached a patch for completeness.

The patch file should be ignored, I see that the file gets the correct line endings when checked out using SVN.

[viboes]

Could we close this ticket?