On Nov 12, 2024, at 6:50 PM, Marshall Clow wrote:

The third release candidates for the 1.87.0 release are now available at: https://boostorg.jfrog.io/artifactory/main/release/1.87.0/source/

The SHA256 checksums are as follows:

10ea784394be84794ed8981643ea0f05fae38de6aa595353115f85c79e4c1cd7 boost_1_87_0_b1_rc3.tar.gz 56db0fc204e6e0e40e1764800ef82475c96916e86112bc9627d1b94102cb786a boost_1_87_0_b1_rc3.7z 45fcc8f7f63e023cdafc1d88b3b915f3feac6bc7aab52a91d5766b5a2248af6d boost_1_87_0_b1_rc3.zip e0c971e3b92aa8ab781fe8239e050078600a446bd26c4509001037872974c4c2 boost_1_87_0_b1_rc3.tar.bz2

Changes since RC2: * The Boost.Parser library is included * A bug that caused compile failures in stl_interfaces with recent versions of clang has been fixed. * A bug that caused compile failures on Boost.Proces with gcc has been fixed.

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 built the libraries on x86 on Mac OS Sonoma 14.7.1 (23H222) using 'Apple clang version 16.0.0 (clang-1600.0.26.4)’ All the libraries built successfully on C++11/14/17/20/23/2c — Marshall

On Tue, Nov 12, 2024 at 8:50 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:

The third release candidates for the 1.87.0 release are now available at: https://boostorg.jfrog.io/artifactory/main/release/1.87.0/source/

The SHA256 checksums are as follows:

10ea784394be84794ed8981643ea0f05fae38de6aa595353115f85c79e4c1cd7 boost_1_87_0_b1_rc3.tar.gz 56db0fc204e6e0e40e1764800ef82475c96916e86112bc9627d1b94102cb786a boost_1_87_0_b1_rc3.7z 45fcc8f7f63e023cdafc1d88b3b915f3feac6bc7aab52a91d5766b5a2248af6d boost_1_87_0_b1_rc3.zip e0c971e3b92aa8ab781fe8239e050078600a446bd26c4509001037872974c4c2 boost_1_87_0_b1_rc3.tar.bz2

Changes since RC2: * The Boost.Parser library is included * A bug that caused compile failures in stl_interfaces with recent versions of clang has been fixed. * A bug that caused compile failures on Boost.Proces with gcc has been fixed.

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.

Looks good on Windows/Visual Studio (with msvc-14.0 removed). toolset arch compile Link Execute 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 msvc-14.3 32 X X X msvc-14.3 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 log here: https://gist.github.com/teeks99/0df41b0f4063086f2bde413618d8fe31 Tom