[release] Boost 1.85.0 Release Candidate 2 is available
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
On Apr 9, 2024, at 9:23 AM, Marshall Clow
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.
I have built the libraries on ARM on Mac OS Ventura 13.4.1 (22G313) using 'Apple clang version 15.0.0 (clang-1500.3.9.4)’ All the libraries built successfully on C++11/14/17/20/2b The following libraries failed to build on C++03: Boost.Contract Boost.Coroutine Boost.Graph Boost.ProgramOptions Boost.Random Boost.Serialization Boost.Thread — Marshall
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Am Dienstag, dem 09.04.2024 um 09:23 -0500 schrieb Marshall Clow via Boost:
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 build them and used them on my project with Windows 10 and MSVC 2019. All seems ok. - - Georg -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEcSCAewDCysh7zXDlcEsNp+0azOkFAmYVa14ACgkQcEsNp+0a zOm73g/7BADsQOvvVEvnweLn6ZWzEs4+DlVDVHFkinuVhxeJUMDdcUqFKNq5vjLN wU+yJ+HAOTkb4DIaX0QGAHAuS9kyt6rz535IVk560PsMC7P8kMAN8hn5fOsb4nSi fkEZIaYzbqaknMFXz8e0M/RyvJ/qjJ64w4+uKkzk33RsIE/cWYDBIG7h53boGeku vNTv+oWMENrk3Ib9bGCxZ73Qf89kBQli909xRQRdFTDd543WMOh7csPYh1pT5S62 ZMnECJdG+cRH3uclWl9s+2HqgLbNOeYGhGzqVHZwXlKdScCPcpANW+Ig+NfkuIBY /LTuS3Jy5PmHLTHO8jDSMsCl8JwFOhkzsqRroVtcHk9Ux1VD7baUfi01KFuvSPwB CVAsVkca7kkhjdX3veLGMEK7ouw6MqU6RE4QlJuljBkFra12XxkJ7CXpQru9pz0w 5rG4fJFxQaybvHqIVclxgWBI9OSFsMc6xE/eUi2V/gPHnXAYJI0zxJ8xN+0lSqKm gsIR8nTlOPhVqOwWTrK3e6spfb6yYx7V08mnLgkoevoamq2E9YDweGw6LtP5PdGD F3hiTJiE7Tgvsj9Gu+zBvkd81YNjScDWe2fFRoCkgeASAdLwBu4JwIGWk8+DZrR8 CJXH5uVNfSfoEWdODclw7mSuLQJbn+0jkgNkCF7ZLUEa41EnQB8= =OPJh -----END PGP SIGNATURE-----
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
On 4/9/24 20:16, 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
Boost.Log fix is also missing in the RC2.
On Tue, Apr 9, 2024 at 1:28 PM Andrey Semashev wrote:
On 4/9/24 20:16, Tom Kent 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. 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
Boost.Log fix is also missing in the RC2.
This is strange because the commit bot picked up the change.
On Apr 9, 2024, at 10:27 AM, Andrey Semashev via Boost
On 4/9/24 20:16, 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
Boost.Log fix is also missing in the RC2.
Well, crud. I’ll be looking into this today. — Marshall
On Thu, Apr 11, 2024 at 11:15 AM Marshall Clow wrote:
On Apr 9, 2024, at 10:27 AM, Andrey Semashev wrote:
Boost.Log fix is also missing in the RC2.
Well, crud.
I’ll be looking into this today.
I think we saw this before, but I couldn't figure it out: https://github.com/boostorg/dynamic_bitset/issues/77 Glen
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.
On Tue, Apr 9, 2024 at 8:46 PM Tom Kent via Boost
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
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
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 an M1 Mac running Sonoma 14.4.1 with homebrew clang 17.0.6 and homebrew GCC 13.2.0 using cxxstd=11,14,17,20,23. Only thing of note is charconv and scope both do not have boost-1.85.0.beta1 tags. Marshall was pinged in: https://github.com/boostorg/charconv/issues/175, but just wanted to make sure they will get the release tags. Thanks. Matt
participants (7)
-
Andrey Semashev
-
Georg Gast
-
Glen Fernandes
-
Marshall Clow
-
Matt Borland
-
Mohammad Nejati [ashtum]
-
Tom Kent