[1.56.0] Release Candidate 2 available
We've created a second release candidate to fix a few issues. The three fixes since RC1 are listed at the end of this mail. The files for 1.56.0 RC2 are available at: http://boost.cowic.de/rc/ As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. The files (and associated md5s) are: MD5 (boost_1_56_0_rc2.7z) = 2e1688886aede1c3348e131a0e73a031 MD5 (boost_1_56_0_rc2.tar.bz2) = 2079fabbfb9fb046e6e12e381eff20fa MD5 (boost_1_56_0_rc2.tar.gz) = 96fe9c5f70759399217dc7ee113ecdd3 MD5 (boost_1_56_0_rc2.zip) = df42b60e120841fc3893de7c2529fc4a Thanks! -- The release managers === Changes Since RC1 === Boost.Thread bug is causing coroutine build to fail on gcc 4.6 in C++11 mode. https://github.com/boostorg/thread/pull/21 Boost.Graph broken on MSVC-12 and gcc-4.4. https://github.com/boostorg/graph/pull/14 Boost.System broken on cygwin, local_free_on_destruction not defined. https://github.com/boostorg/system/pull/4
On Aug 3, 2014, at 7:55 PM, Eric Niebler <eniebler@boost.org> wrote:
We've created a second release candidate to fix a few issues. The three fixes since RC1 are listed at the end of this mail.
The files for 1.56.0 RC2 are available at: http://boost.cowic.de/rc/
Built successfully on Mac OS X with: gcc 4.9.0 clang 3.4 in C++03/11/14 modes — Marshall
Eric Niebler <eniebler <at> boost.org> writes:
=== Changes Since RC1 ===
Boost.Thread bug is causing coroutine build to fail on gcc 4.6 in C++11 mode. https://github.com/boostorg/thread/pull/21
Boost.Graph broken on MSVC-12 and gcc-4.4. https://github.com/boostorg/graph/pull/14
Boost.System broken on cygwin, local_free_on_destruction not defined. https://github.com/boostorg/system/pull/4
Seems like the Boost.Range operators bugfix also got in? https://github.com/boostorg/range/pull/16
Eric Niebler <eniebler <at> boost.org> writes:
We've created a second release candidate to fix a few issues. The three fixes since RC1 are listed at the end of this mail.
The files for 1.56.0 RC2 are available at: http://boost.cowic.de/rc/
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
Tested on MSVC12 Update 3 RC for 32-bit and 64-bit and everything still works as in RC1, plus the compiler crashes are gone.
On Mon, Aug 04, 2014 at 11:08:11AM +0000, Marcel Raad wrote:
Eric Niebler <eniebler <at> boost.org> writes:
We've created a second release candidate to fix a few issues. The three fixes since RC1 are listed at the end of this mail.
The files for 1.56.0 RC2 are available at: http://boost.cowic.de/rc/
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
Tested on MSVC12 Update 3 RC for 32-bit and 64-bit and everything still works as in RC1, plus the compiler crashes are gone.
By "tested", do you mean attempted to build, or actually ran tests? I'm going to assume the former, as the latter is near-impossible for the layman. It's a bit disheartening to see so few attempts to run integrity tests, but I guess it's an artifact of it being underdocumented and hard to run tests and get output from them without being a proper regression test runner. -- Lars Viklund | zao@acc.umu.se
Lars Viklund <zao <at> acc.umu.se> writes:
By "tested", do you mean attempted to build, or actually ran tests? I'm going to assume the former, as the latter is near-impossible for the layman.
It's a bit disheartening to see so few attempts to run integrity tests, but I guess it's an artifact of it being underdocumented and hard to run tests and get output from them without being a proper regression test runner.
By "tested", I mean that in addition to building Boost, I have compiled some of our own projects and run their regression tests, which make heavy use of many Boost libraries. I do sometimes run the Boost regression test suite and have done so for a previous 1.56 build, but there are many expected failures that haven't been marked as such for newer MSVC versions as well as compiler crashes, so I often don't know which failures are critical.
On Mon, Aug 4, 2014 at 7:28 AM, Lars Viklund <zao@acc.umu.se> wrote:
On Mon, Aug 04, 2014 at 11:08:11AM +0000, Marcel Raad wrote:
Eric Niebler <eniebler <at> boost.org> writes:
We've created a second release candidate to fix a few issues. The three fixes since RC1 are listed at the end of this mail.
The files for 1.56.0 RC2 are available at: http://boost.cowic.de/rc/
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
Tested on MSVC12 Update 3 RC for 32-bit and 64-bit and everything still works as in RC1, plus the compiler crashes are gone.
By "tested", do you mean attempted to build, or actually ran tests? I'm going to assume the former, as the latter is near-impossible for the layman.
It's a bit disheartening to see so few attempts to run integrity tests, but I guess it's an artifact of it being underdocumented and hard to run tests and get output from them without being a proper regression test runner.
Yes, that is a problem for testing all of Boost, but it is quite easy to check a particular library. For example, after downloading and unpacking the rc, you can test boost.system like this: cd boost_1_56_0 .\bootstrap cd libs/system/test ..\..\..\b2 HTH, --Beman
On Sun, Aug 3, 2014 at 10:55 PM, Eric Niebler <eniebler@boost.org> wrote:
We've created a second release candidate to fix a few issues. The three fixes since RC1 are listed at the end of this mail.
... === Changes Since RC1 ===
... Boost.System broken on cygwin, local_free_on_destruction not defined. https://github.com/boostorg/system/pull/4
Downloaded RC2 on Windows, and tested the above change with cygwin/gcc, mingw/gcc, VC++ 10, 11, and 12. All boost.system tests passed. Downloaded RC2 on Linux, and tested the above change with gcc. All boost.system tests passed. --Beman
On Mon, Aug 4, 2014 at 2:55 AM, Eric Niebler <eniebler@boost.org> wrote:
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
Windows builds look good: toolset arch compile install Link Execute msvc-8.0 32 X X X X msvc-8.0 64 X X X X msvc-9.0 32 X X X X msvc-9.0 64 X X X X msvc-10.0 32 X X X X msvc-10.0 64 X X X X msvc-11.0 32 X X X X msvc-11.0 64 X X X X msvc-12.0 32 X X X X msvc-12.0 64 X X X X Compile means that the b2 command completed without errors Install means that the installers for the respective version were generated Link means that visual studio was able to link a sample executable to a library (libboost_thread-vcXXX-mt[-gd]-1_XX.lib) generated Execute means that the linked program executed without errors. Tom
Eric Niebler wrote On 4-8-2014 4:55:
We've created a second release candidate to fix a few issues. The three fixes since RC1 are listed at the end of this mail.
The files for 1.56.0 RC2 are available at: http://boost.cowic.de/rc/
I'm a bit lost. Was this RC announced? Or is it an extra RC to fix the show-stoppers? We want to merge some small fixes and doc improvements for 1.56, not really show-stoppers, but still convenient. Will the master open again and will there be an RC3? I hope so. Can the Release Manager team please announce when the master opens again, and when it will be closed? Thanks, Barend
On Aug 4, 2014, at 2:02 PM, Barend Gehrels <barend@xs4all.nl> wrote:
Eric Niebler wrote On 4-8-2014 4:55:
We've created a second release candidate to fix a few issues. The three fixes since RC1 are listed at the end of this mail.
The files for 1.56.0 RC2 are available at: http://boost.cowic.de/rc/
I'm a bit lost. Was this RC announced? Or is it an extra RC to fix the show-stoppers?
This was the announcement for RC2.
We want to merge some small fixes and doc improvements for 1.56, not really show-stoppers, but still convenient.
Will the master open again and will there be an RC3? I hope so. Can the Release Manager team please announce when the master opens again, and when it will be closed?
The master branch is still closed. There may be an RC3, but if there is, it will be specific bug fixes. We’re not going to open up for general changes before the release; the goal here is to make the differences between RC(n) and RC(n+1) as small as possible. We will definitely announce when the master branch is open again, but it will be after we release. — Marshall
On 08/03/2014 07:55 PM, Eric Niebler wrote:
We've created a second release candidate to fix a few issues. The three fixes since RC1 are listed at the end of this mail.
Boost.Graph broken on MSVC-12 and gcc-4.4. https://github.com/boostorg/graph/pull/14
Looks good to me on RHEL6 w/ gcc-4.4 - Thomas
On Sunday 03 August 2014 19:55:18 Eric Niebler wrote:
We've created a second release candidate to fix a few issues. The three fixes since RC1 are listed at the end of this mail.
The files for 1.56.0 RC2 are available at: http://boost.cowic.de/rc/
As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.
The files (and associated md5s) are: MD5 (boost_1_56_0_rc2.7z) = 2e1688886aede1c3348e131a0e73a031 MD5 (boost_1_56_0_rc2.tar.bz2) = 2079fabbfb9fb046e6e12e381eff20fa MD5 (boost_1_56_0_rc2.tar.gz) = 96fe9c5f70759399217dc7ee113ecdd3 MD5 (boost_1_56_0_rc2.zip) = df42b60e120841fc3893de7c2529fc4a
Build succeeded on Linux with gcc {4.4, 4.6, 4.7, 4.8}, C++{03, 11}, link={shared, static}.
participants (9)
-
Andrey Semashev -
Barend Gehrels -
Beman Dawes -
Eric Niebler -
Lars Viklund -
Marcel Raad -
Marshall Clow -
Thomas Suckow -
Tom Kent