On 4/10/24 13:47, Mohammad Nejati [ashtum] via Boost wrote:
I don't think this picked up the fix, or something about the build process here is different than what is happening in beast
It seems that boost_1_85_0_rc2.zip and boost_1_85_0_rc2.tar.bz2 are generated from different commits in the master branch.
The fix is included in boost_1_85_0_rc2.zip.
Looking at .json files, Windows archives (boost_1_85_0_rc2.zip, boost_1_85_0_rc2.7z) were generated from commit 2942b46dcd5be23e2ef310d78f45fb87a7aede90, which is correct and includes all three fixes, and POSIX archives (boost_1_85_0_rc2.tar.gz, boost_1_85_0_rc2.tar.bz2) were generated from commit 09990b1791a3d398a058f40dc2eca65463d85ed8, which only includes Boost.ProgramOptions fix.
On Tue, Apr 9, 2024 at 8:46 PM Tom Kent via Boost
wrote: On Tue, Apr 9, 2024 at 9:23 AM Marshall Clow via Boost < boost@lists.boost.org> wrote:
The second 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:
06bdbef025de63a22baf997d49d34f38455975529ee05ab73379338e572d0df4 boost_1_85_0_rc2.zip 623a9e5288bae94c0c01b733873ea12613af35f4fc433059a0ddaa5cf0033ce1 boost_1_85_0_rc2.tar.bz2 f7b6b252f488dc8a386bfc79bf7197772c4400f847f0dee50754bb23847d40d2 boost_1_85_0_rc2.7z ec9347228d2c8a7189685b48fe4609a837d3dde45973d4457a8f2396d2c446da boost_1_85_0_rc2.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.
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 don't think this picked up the fix, or something about the build process here is different than what is happening in beast. I'm still seeing the file: boost_1_85_0/libs\beast\doc\html\beast\ref\boost__asio__traits__query_static_constexpr_member_lt__beast__test__immediate_executor_comma__Property_comma__typename_enable_if_lt__std__is_convertible_lt__Property_comma__execution__blocking_t__gt___value__gt___type__gt_.html
This is in the .tar.bz2 file with SHA256: 623a9e5288bae94c0c01b733873ea12613af35f4fc433059a0ddaa5cf0033ce1
Tom
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost