Opened 8 years ago

Last modified 8 years ago

#10330 new Bugs

Boost 1.56 bootstrap.bat failed for intel-win32

Reported by: Elmira Semenova <elmira.a.semenova@…> Owned by:
Milestone: To Be Determined Component: Building Boost
Version: Boost 1.56.0 Severity: Showstopper
Keywords: Cc:

Description

New boost.1.56.0 bootstrap.bat fails on Windows with old toolset and with new intel-win32 toolset I used # unzip boost_1_56_0.zip # ./bootstrap.bat intel-win32 Building Boost.Build engine

Failed to build Boost.Build engine. Please consult bootstrap.log for furter diagnostics.

You can try to obtain a prebuilt binary from . . .

Also, you can file an issue at http://svn.boost.org Please attach bootstrap.log in that case.

From attached bootstrap.log: . . . boost_1_56_0\tools\build\src\engine>.\bootstrap\jam0 -f build.jam --toolset=intel-win32 "--toolset-root= " -win32 clean Invalid option: -w

usage: .\bootstrap\jam0 [ options ] targets...

For boost v1.55.0 I used tar.gz archive and ./bootstrap.bat --with-toolset=intel-win but for 1.56.0 it doesn't work. According to recommendation for Ticket #10136 I use *.zip on Windows, but bootstrap.bat doesn't work for intel-win32

Attachments (1)

bootstrap.txt (3.6 KB ) - added by anonymous 8 years ago.

Download all attachments as: .zip

Change History (6)

comment:1 by Elmira Semenova <elmira.a.semenova@…>, 8 years ago

Version: Boost 1.54.0Boost 1.56.0

by anonymous, 8 years ago

Attachment: bootstrap.txt added

comment:2 by Elmira Semenova <elmira.a.semenova@…>, 8 years ago

Component: NoneBuilding Boost

comment:3 by Elmira Semenova <elmira.a.semenova@…>, 8 years ago

Severity: ProblemShowstopper

comment:4 by John Maddock, 8 years ago

I think I know what's happening here, but not how to fix it: when the name of the toolset conatins a "-" it's seen as two separate arguments when the environment variable %args% is computed, as a result the command line ends up with a stray "-win32" added to it. Someone more familiar with windows batch files than me will have to figure that one out!

comment:5 by Andrei Elovikov <a.elovikov@…>, 8 years ago

Hi all,

This seems to fix it for me.

Note: See TracTickets for help on using tickets.