[release] Boost 1.87.0 Release Candidate 3 is available
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. -- The Release managers
On Nov 12, 2024, at 6:50 PM, Marshall Clow <mclow.lists@gmail.com> 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
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:
10ea784394be84794ed8981643ea0f05fae38de6aa595353115f85c79e4c1c d7 boost_1_87_0_b1_rc3.tar.gz 56db0fc204e6e0e40e1764800ef82475c96916e86112bc9627d1b94102cb78 6a boost_1_87_0_b1_rc3.7z 45fcc8f7f63e023cdafc1d88b3b915f3feac6bc7aab52a91d5766b5a2248af6d boost_1_87_0_b1_rc3.zip e0c971e3b92aa8ab781fe8239e050078600a446bd26c4509001037872974c 4c2 boost_1_87_0_b1_rc3.tar.bz2
Changes since RC2: * The Boost.Parser library is included
CMake tests are failing with CMake Error at libs/parser/test/CMakeLists.txt:7 (add_custom_target): add_custom_target cannot create target "check" because another target with the same name already exists. The existing target is a custom target created in source directory "/home/runner/work/boost/boost". See documentation for policy CMP0002 for more details. CMake target names are global and need to be prefixed by the project name. In this case, the target should have been boost_parser-check. Although looking at that test/CMakeLists.txt, it doesn't seem to support testing from the superproject, so it probably shouldn't be included at all in that case. That is, the if(BUILD_TESTING AND EXISTS "${CMAKE_CURRENT_SOURCE_DIR}/test/CMakeLists.txt") add_subdirectory(test) endif() part of the root CMakeLists.txt should be removed.
On Wed, Nov 13, 2024 at 6:29 AM Peter Dimov via Boost <boost@lists.boost.org> wrote:
CMake tests are failing with
CMake Error at libs/parser/test/CMakeLists.txt:7 (add_custom_target): add_custom_target cannot create target "check" because another target with the same name already exists. The existing target is a custom target created in source directory "/home/runner/work/boost/boost". See documentation for policy CMP0002 for more details.
CMake target names are global and need to be prefixed by the project name. In this case, the target should have been boost_parser-check.
Although looking at that test/CMakeLists.txt, it doesn't seem to support testing from the superproject, so it probably shouldn't be included at all in that case. That is, the
if(BUILD_TESTING AND EXISTS "${CMAKE_CURRENT_SOURCE_DIR}/test/CMakeLists.txt")
add_subdirectory(test)
endif()
part of the root CMakeLists.txt should be removed.
Done on develop, here: https://github.com/boostorg/parser/commit/6d796287b6011fa5cf041e8d6795cbfa0a... I'll merge this commit to master if/when Marshall gives the thumbs-up Zach
Zach Laine wrote:
On Wed, Nov 13, 2024 at 6:29 AM Peter Dimov via Boost <boost@lists.boost.org> wrote:
CMake tests are failing with
CMake Error at libs/parser/test/CMakeLists.txt:7 (add_custom_target): add_custom_target cannot create target "check" because another target
with
the same name already exists. The existing target is a custom target created in source directory "/home/runner/work/boost/boost". See documentation for policy CMP0002 for more details.
CMake target names are global and need to be prefixed by the project name. In this case, the target should have been boost_parser-check.
Although looking at that test/CMakeLists.txt, it doesn't seem to support testing from the superproject, so it probably shouldn't be included at all in that case. That is, the
if(BUILD_TESTING AND EXISTS "${CMAKE_CURRENT_SOURCE_DIR}/test/CMakeLists.txt")
add_subdirectory(test)
endif()
part of the root CMakeLists.txt should be removed.
Done on develop, here:
https://github.com/boostorg/parser/commit/6d796287b6011fa5cf041e8d67 95cbfa0aaf6fd4
I'll merge this commit to master if/when Marshall gives the thumbs-up
Thanks, tests are fixed now: https://github.com/boostorg/boost/actions/runs/11829983776/job/32962750332
On Wed, Nov 13, 2024 at 9:51 PM Peter Dimov <pdimov@gmail.com> wrote:
Zach Laine wrote:
On Wed, Nov 13, 2024 at 6:29 AM Peter Dimov via Boost <boost@lists.boost.org> wrote:
CMake tests are failing with
[snip]
part of the root CMakeLists.txt should be removed.
Done on develop, here:
https://github.com/boostorg/parser/commit/6d796287b6011fa5cf041e8d67 95cbfa0aaf6fd4
I'll merge this commit to master if/when Marshall gives the thumbs-up
Thanks, tests are fixed now:
https://github.com/boostorg/boost/actions/runs/11829983776/job/32962750332
Marshall, should I merge this commit to master? While working on something unrelated, I also found a subtle bug with a simple fix: https://github.com/boostorg/parser/commit/3eb827dcd6a0de77c1f10956f1ce9d1a0f... Can I merge that one too? Zach
On Nov 14, 2024, at 8:56 PM, Zach Laine via Boost <boost@lists.boost.org> wrote:
On Wed, Nov 13, 2024 at 9:51 PM Peter Dimov <pdimov@gmail.com> wrote:
Zach Laine wrote:
On Wed, Nov 13, 2024 at 6:29 AM Peter Dimov via Boost <boost@lists.boost.org> wrote:
CMake tests are failing with
[snip]
part of the root CMakeLists.txt should be removed.
Done on develop, here:
https://github.com/boostorg/parser/commit/6d796287b6011fa5cf041e8d67 95cbfa0aaf6fd4
I'll merge this commit to master if/when Marshall gives the thumbs-up
Thanks, tests are fixed now:
https://github.com/boostorg/boost/actions/runs/11829983776/job/32962750332
Marshall, should I merge this commit to master?
While working on something unrelated, I also found a subtle bug with a simple fix:
https://github.com/boostorg/parser/commit/3eb827dcd6a0de77c1f10956f1ce9d1a0f...
Can I merge that one too?
Please don’t. Those can be merged after we ship the beta. — Marshall
On Thu, Nov 14, 2024, 11:10 PM Marshall Clow <mclow.lists@gmail.com> wrote:
On Nov 14, 2024, at 8:56 PM, Zach Laine via Boost <boost@lists.boost.org> wrote:
On Wed, Nov 13, 2024 at 9:51 PM Peter Dimov <pdimov@gmail.com> wrote:
Zach Laine wrote:
On Wed, Nov 13, 2024 at 6:29 AM Peter Dimov via Boost <boost@lists.boost.org> wrote:
CMake tests are failing with
[snip]
part of the root CMakeLists.txt should be removed.
Done on develop, here:
https://github.com/boostorg/parser/commit/6d796287b6011fa5cf041e8d67 95cbfa0aaf6fd4
I'll merge this commit to master if/when Marshall gives the thumbs-up
Thanks, tests are fixed now:
https://github.com/boostorg/boost/actions/runs/11829983776/job/32962750332
Marshall, should I merge this commit to master?
While working on something unrelated, I also found a subtle bug with a simple fix:
https://github.com/boostorg/parser/commit/3eb827dcd6a0de77c1f10956f1ce9d1a0f...
Can I merge that one too?
Please don’t.
Those can be merged after we ship the beta.
Gotcha. To be clear -- wait on both of them, right? Zach
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
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.
-- The Release managers
The link provided gives me a 404 error. I believe that the correct link should be: https://boostorg.jfrog.io/artifactory/main/beta/1.87.0.beta1/source/ I have successfully built the libraries on an M1 Pro Macbook pro running macOS Sequoia 15.1 with Homebrew Clang 19.1.3 and cxxstd=11,14,17,20,23. Matt
On Nov 13, 2024, at 6:33 AM, Matt Borland <matt@mattborland.com> wrote:
The link provided gives me a 404 error. I believe that the correct link should be: https://boostorg.jfrog.io/artifactory/main/beta/1.87.0.beta1/source/
This is absolutely correct. That will teach me (hopefully) not to reuse old posts. — Marshall
participants (5)
-
Marshall Clow -
Matt Borland -
Peter Dimov -
Tom Kent -
Zach Laine