Eric Niebler wrote:
Beman Dawes wrote:
I've gotten badly sidetracked by non-Boost work, but would like to get the 1.39.0 beta out tomorrow if at all possible.
Are there any known showstoppers?
If anyone has a few spare minutes, it would help if they could download one of the current release snapshots from http://boost.cowic.de/rc/, browse around and report any problems spotted.
Seems like bootstrap.bat is busted:
C:\boost\org\1.39-alpha-full\boost-windows-2009-04-22>.\bootstrap.bat
C:\boost\org\1.39-alpha-full\boost-windows-2009-04-22># Copyright (C) 2009 Vladimir Prus '#' is not recognized as an internal or external command, operable program or batch file.
Boo! Copyright addition was the last change to that file, and I have failed to test it. Fixed now.
C:\boost\org\1.39-alpha-full\boost-windows-2009-04-22># '#' is not recognized as an internal or external command, operable program or batch file.
C:\boost\org\1.39-alpha-full\boost-windows-2009-04-22># Distributed under the Boost Software License , Version 1.0. '#' is not recognized as an internal or external command, operable program or batch file.
C:\boost\org\1.39-alpha-full\boost-windows-2009-04-22># (See accompanying file LICENSE_1_0.txt or ht tp://www.boost.org/LICENSE_1_0.txt) '#' is not recognized as an internal or external command, operable program or batch file. Building Boost.Jam build engine The system cannot find the file specified.
If you want to put a comment in a DOS batch file, you use REM, not #. I'm a bit dismayed that this apparently got merged to release without even being tested.
I notice that later this script instructs the user to type "./bjam --help". Remember, this is a windows batch script. The command should be ".\bjam --help" (note the forward slash).
Fixed. Note that the command that user is instructed to actually run uses right slashes. - Volodya