On Jul 12, 2020, at 8:39 AM, Marshall Clow wrote:

The release candidates for the first 1.74.0 beta release are now available at: https://dl.bintray.com/boostorg/beta/1.74.0.beta.1/source/ https://dl.bintray.com/boostorg/beta/1.74.0.beta.1/source/

The release notes are not yet available.

The SHA256 checksums are as follows: 577a6b575ff2c227e14cce1b929c73d969475e58f3d2ab2901ad234f773bbd12 boost_1_74_0_b1_rc1.7z ba09c72dc848e7c0904922967014d853897b5a634926c910cc3b1fd627c31605 boost_1_74_0_b1_rc1.tar.bz2 2ccdc39efa076822cf1b359f9449f9d07707f3e27a18b393297b25885a9ff45b boost_1_74_0_b1_rc1.tar.gz c267c450166e040a374eaddab5e583cef09f6c3fe96a4db826172d0315c38dd5 boost_1_74_0_b1_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.

I have successfully built the libraries on the following platforms: Ubuntu 18.04 using GCC 7.5: C++03/11/14/17 Mac OS 10.15.5 using "Apple clang version 11.0.3 (clang-1103.0.32.62)”: C++03/11/14/17/2a — Marshall

On Sun, Jul 12, 2020 at 10:39 AM Marshall Clow via Boost-users < boost-users@lists.boost.org> wrote:

The release candidates for the first 1.74.0 beta release are now available at: https://dl.bintray.com/boostorg/beta/1.74.0.beta.1/source/

The release notes are not yet available.

The SHA256 checksums are as follows: 577a6b575ff2c227e14cce1b929c73d969475e58f3d2ab2901ad234f773bbd12 boost_1_74_0_b1_rc1.7z ba09c72dc848e7c0904922967014d853897b5a634926c910cc3b1fd627c31605 boost_1_74_0_b1_rc1.tar.bz2 2ccdc39efa076822cf1b359f9449f9d07707f3e27a18b393297b25885a9ff45b boost_1_74_0_b1_rc1.tar.gz c267c450166e040a374eaddab5e583cef09f6c3fe96a4db826172d0315c38dd5 boost_1_74_0_b1_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 Boost Release Managers

Build look good on windows/visual studio. 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. However, I experienced issues with my (unchanged) packing tools. The Geometry library has some very long path names in its documentation. Even on a windows machine where I have disabled the path length limit I'm seeing errors (my packaging tool I guess). If I'm seeing them, I'm worried others will too. This has been discussed once before: https://github.com/boostorg/geometry/issues/396 there the answer was that some additional cleanup that should have happened but didn't needed to be run. Can this be done again for an -rc2? Thanks, Tom