Re: [release] Boost 1.73.0 Release Candidate 1

From: Tom Kent (lists_at_[hidden])
Date: 2020-04-23 21:45:03

On Thu, Apr 23, 2020 at 8:53 AM Marshall Clow via Boost <
boost_at_[hidden]> wrote:

> The first release candidates for the 1.73.0 release are now available at:
>
> <https://dl.bintray.com/boostorg/release/1.73.0/source/>
>
> The SHA256 checksums are as follows:
>
> d2e7501bb04fe7abc09aa93f013ae997604286a882da1bd36ddd96ea1163ea71
>  boost_1_73_0_rc1.7z
> 4eb3b8d442b426dc35346235c8733b5ae35ba431690e38c6a8263dce9fcbb402
>  boost_1_73_0_rc1.tar.bz2
> 9995e192e68528793755692917f9eb6422f3052a53c5e13ba278a228af6c7acf
>  boost_1_73_0_rc1.tar.gz
> 0909a79524f857ef54570ceef8f397cc0629202532cc997785479c7c08bbc2a4
>  boost_1_73_0_rc1.zip
>
> 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 Release managers
>

I had four failures attempting to build on windows. However, they were
atypical in that the build stalled out and would not continue, rather than
producing an error.

The last items in the terminal before stalling out was something like:
D:\ReleaseBuild\bin.v2\boost\bin.v2\libs\wave\build\msvc-14.0\release\link-static\runtime-link-static\threadapi-win32\threading-multi\libboost_wave-variant-vc140-mt-s-x32-1_73-static.cmake
        1 file(s) copied.
common.copy
D:\ReleaseBuild\boost_1_73_0\lib32-msvc-14.0\libboost_wave-vc140-mt-s-x32-1_73.lib
D:\ReleaseBuild\bin.v2\boost\bin.v2\libs\wave\build\msvc-14.0\release\link-static\runtime-link-static\threadapi-win32\threading-multi\libboost_wave-vc140-mt-s-x32-1_73.lib
        1 file(s) copied.

It seemed to be generally in wave, however one time it failed in log. This
example shows the problem during msvc-14.0, but I believe I also saw it in
14.1 one of the times. I had experienced something similar during the beta
build, and after succeeding I was unable to reproduce it on the same
computer, somehow related to caching? Very weird, and I don't think we
should release while this is ongoing.

On the fifth try, I was able to get a good build for all versions of visual
studio I was attempting.

toolset     arch    compile Link    Execute
msvc-10.0   32      X       X       X
msvc-10.0   64      X       X       X
msvc-11.0   32      X       X       X
msvc-11.0   64      X       X       X
msvc-12.0   32      X       X       X
msvc-12.0   64      X       X       X
msvc-14.0   32      X       X       X
msvc-14.0   64      X       X       X
msvc-14.1   32      X       X       X
msvc-14.1   64      X       X       X
msvc-14.2   32      X       X       X
msvc-14.2   64      X       X       X

Compile means that the b2 command completed without errors
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.

Full build logs can be found here:
https://gist.github.com/teeks99/586e868be64464e474233d20d35de656

Tom