Boost logo

Boost :

From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2024-04-11 21:44:52


On 4/12/24 00:31, Marshall Clow via Boost wrote:
> The third release candidates for the 1.85.0 release are now available at:
> <https://boostorg.jfrog.io/artifactory/main/release/1.85.0/source/>
>
> The SHA256 checksums are as follows:
>
> e712fe7eb1b9ec37ac25102525412fb4d74e638996443944025791f48f29408a boost_1_85_0_rc3.zip
> 7009fe1faa1697476bdc7027703a2badb84e849b7b0baad5086b087b971f8617 boost_1_85_0_rc3.tar.bz2
> 16d16b9658753117c1434e5450c5eac194957f4b6d0b390b9d07900d37c115a4 boost_1_85_0_rc3.7z
> be0d91732d5b0cc6fbb275c7939974457e79b54d6f07ce2e3dfdd68bef883b0b boost_1_85_0_rc3.tar.gz
>
> The changes from RC1 are:
>
> * Boost.ASIO docs generate very long file names that are not usable on Windows.
> * Boost.Program options does not build in C++23 mode on clang truck (to be clang 19 before boost 1.86.0 is released)
> Note: It is possible that this is a bug in clang, and it’s in a clang that is not released yet.
> * Boost.Log has some broken links in its documentation.
> * A meaningless change to Boost.Array (add a space to a test file)
>
> Apparently the RC2 tarballs were mis-buiilt; some of them were missing the required changes.
> I believe that RC3 resolves that problem.
>
> 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 can confirm that the .tar.bz2 file contains the Boost.Log fix and all
.json files reference the same commit
ab7968a0bbcf574a7859240d1d8443f58ed6f6cf.


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk