[release] Boost 1.86.0 Beta 1 Release Candidate 4 is available
[ RC3 was malformed as a result of some tooling failures ] The fourth (and hopefully final) RC for the 1.86.0 Beta release is now available. Available at: https://archives.boost.io/beta/1.86.0.beta1/source/ The SHA256 checksums are as follows: cad677f5b746bd83c68131766554b56ebf40eb7ba94823526b03820db9dbc049 boost_1_86_0_b1_rc4.7z 6c3b6b6b1760090ebd658b764c9006d9579df2a20763ede356e059fe52989277 boost_1_86_0_b1_rc4.tar.bz2 cc0e5c0fb54ea8762c2eb9fbfd185cb8ccbe1ad33c218883f9438dbe2f9a795b boost_1_86_0_b1_rc4.zip 82b59c0ca4d3b8bbf910ffdbbf535ef738fa1d648b8ba6f2608b516a58f89c55 boost_1_86_0_b1_rc4.tar.gz Changed libraries between RC2 and RC4: Boost.Process fixed some build issues on Windows 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 Jul 24, 2024, at 11:29 AM, Marshall Clow <mclow.lists@gmail.com> wrote:
[ RC3 was malformed as a result of some tooling failures ]
The fourth (and hopefully final) RC for the 1.86.0 Beta release is now available.
Available at: https://archives.boost.io/beta/1.86.0.beta1/source/
The SHA256 checksums are as follows:
cad677f5b746bd83c68131766554b56ebf40eb7ba94823526b03820db9dbc049 boost_1_86_0_b1_rc4.7z 6c3b6b6b1760090ebd658b764c9006d9579df2a20763ede356e059fe52989277 boost_1_86_0_b1_rc4.tar.bz2 cc0e5c0fb54ea8762c2eb9fbfd185cb8ccbe1ad33c218883f9438dbe2f9a795b boost_1_86_0_b1_rc4.zip 82b59c0ca4d3b8bbf910ffdbbf535ef738fa1d648b8ba6f2608b516a58f89c55 boost_1_86_0_b1_rc4.tar.gz
Changed libraries between RC2 and RC4: Boost.Process fixed some build issues on Windows
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 have built the boost libraries on a x86_64 machine running Mac OS X 14.5 using "Apple clang version 15.0.0 (clang-1500.3.9.4)” The libraries were built successfully using C++11/14/17/20/2B. However, when building for C++03, the following libraries failed to build * contract * graph * program_options * serialization * test * thread — Marshall
On 7/24/24 11:30 AM, Marshall Clow via Boost wrote:
On Jul 24, 2024, at 11:29 AM, Marshall Clow <mclow.lists@gmail.com> wrote:
However, when building for C++03, the following libraries failed to build
* contract * graph * program_options * serialization * test * thread
— Marshall
Given that its been decided to discourage usage of C++ 03, I would suggest that libraries not be tested with this toolset. It sends a confusing message. Robert Ramey
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On Wed, Jul 24, 2024 at 4:09 PM Robert Ramey via Boost < boost@lists.boost.org> wrote:
Given that its been decided to discourage usage of C++ 03, I would suggest that libraries not be tested with this toolset. It sends a confusing message.
Maybe I'm wrong about this but my impression is that if you don't support C++03, you still shouldn't break the build. There's a way in the Jamfile to make it such that b2 just skips over your library because it doesn't meet the requirements. You can use something like this: https://github.com/cppalliance/http_proto/blob/31e7cc801bea82a9f110f9c608ea9... Seems to work pretty alright. You can do: b2 libs/http_proto/build cxxstd=03 and b2 won't complain. - Christian
On Jul 25, 2024, at 8:03 AM, Christian Mazakas via Boost <boost@lists.boost.org> wrote:
On Wed, Jul 24, 2024 at 4:09 PM Robert Ramey via Boost < boost@lists.boost.org> wrote:
Given that its been decided to discourage usage of C++ 03, I would suggest that libraries not be tested with this toolset. It sends a confusing message.
Maybe I'm wrong about this but my impression is that if you don't support C++03, you still shouldn't break the build.
There's a way in the Jamfile to make it such that b2 just skips over your library because it doesn't meet the requirements.
You can use something like this: https://github.com/cppalliance/http_proto/blob/31e7cc801bea82a9f110f9c608ea9...
Seems to work pretty alright.
You can do: b2 libs/http_proto/build cxxstd=03
and b2 won't complain.
The problem - at least the last time that I looked into this - was that the libraries that are failing don’t have any problem with C++03 directly, but they use other boost libraries that have dropped C++03 support. And yes, I agree that if you run “b2 cxxstd=03”, you should get a set of libraries that work with C++03, and no build errors. Libraries that don’t support C++03 should not be built. — Marshall
[ RC3 was malformed as a result of some tooling failures ]
The fourth (and hopefully final) RC for the 1.86.0 Beta release is now available.
Available at: https://archives.boost.io/beta/1.86.0.beta1/source/
The SHA256 checksums are as follows:
cad677f5b746bd83c68131766554b56ebf40eb7ba94823526b03820db9dbc049 boost_1_86_0_b1_rc4.7z 6c3b6b6b1760090ebd658b764c9006d9579df2a20763ede356e059fe52989277 boost_1_86_0_b1_rc4.tar.bz2 cc0e5c0fb54ea8762c2eb9fbfd185cb8ccbe1ad33c218883f9438dbe2f9a795b boost_1_86_0_b1_rc4.zip 82b59c0ca4d3b8bbf910ffdbbf535ef738fa1d648b8ba6f2608b516a58f89c55 boost_1_86_0_b1_rc4.tar.gz
Changed libraries between RC2 and RC4: Boost.Process fixed some build issues on Windows
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 successfully built the libraries on x86_64 RHEL 9.4 using GCC 11.4.1 with cxxstd=11,14,17,20,2b. Matt
On Wed, Jul 24, 2024 at 1:29 PM Marshall Clow via Boost < boost@lists.boost.org> wrote:
[ RC3 was malformed as a result of some tooling failures ]
The fourth (and hopefully final) RC for the 1.86.0 Beta release is now available.
Available at: https://archives.boost.io/beta/1.86.0.beta1/source/
The SHA256 checksums are as follows:
cad677f5b746bd83c68131766554b56ebf40eb7ba94823526b03820db9dbc049 boost_1_86_0_b1_rc4.7z 6c3b6b6b1760090ebd658b764c9006d9579df2a20763ede356e059fe52989277 boost_1_86_0_b1_rc4.tar.bz2 cc0e5c0fb54ea8762c2eb9fbfd185cb8ccbe1ad33c218883f9438dbe2f9a795b boost_1_86_0_b1_rc4.zip 82b59c0ca4d3b8bbf910ffdbbf535ef738fa1d648b8ba6f2608b516a58f89c55 boost_1_86_0_b1_rc4.tar.gz
Changed libraries between RC2 and RC4: Boost.Process fixed some build issues on Windows
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
Looks good on Windows/Visual Studio. toolset arch compile Link Execute msvc-14.0 32 X X X msvc-14.0 64 X X X 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 build logs can be found here: https://gist.github.com/teeks99/12216d11f1ccbbcb6b0817f43f2ad459 Tom
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 attempted to build the libraries with homebrew LLVM 18.1.8 on an M1 Pro Mac running macOS 14.5, but Boost.Cobalt and Boost.Log both fail to build because of: Undefined symbols for architecture arm64: "std::exception_ptr::__from_native_exception_pointer(void*)", referenced from: std::exception_ptr std::make_exception_ptr[abi:ne180100]<boost::system::error_code>(boost::system::error_code) in exception.o boost::asio::detail::thread_info_base::capture_current_exception() in main.o "___cxa_init_primary_exception", referenced from: std::exception_ptr std::make_exception_ptr[abi:ne180100]<boost::system::error_code>(boost::system::error_code) in exception.o boost::asio::detail::thread_info_base::capture_current_exception() in main.o ld: symbol(s) not found for architecture arm64 I have opened an issue against homebrew here: https://github.com/Homebrew/homebrew-core/issues/178435. There are linked LLVM issues, and a comment from a Homebrew maintainer that says a workaround has already been applied to brewed LLVM to fix the LLVM issues. On the positive homebrew GCC-14 and Xcode provided clang 15.0.0 both successfully build the libraries. Matt
participants (5)
-
Christian Mazakas -
Marshall Clow -
Matt Borland -
Robert Ramey -
Tom Kent