[release] Boost 1.92 RC1 available
The first release candidates for the 1.92.0 release are now available at: https://archives.boost.io/release/1.92.0/source/ The SHA256 checksums are as follows: c4a3b310ddd2472416e091067166b0713be97c63f38c212c484ada022fd296ce boost_1_92_0_rc1.tar.gz 57f2ded2390068a44d88748425067e01a8c285257a4d9611d04ade9d8ec68615 boost_1_92_0_rc1.7z c46baee75ed4b558cf6553630d0615a147ed582812917b57e6f0839d1954549f boost_1_92_0_rc1.zip 5c1d40cb8e19adbf740a4ec2da35b3e58f3f5804b1dce44deb53df72193cbc6c boost_1_92_0_rc1.tar.bz2 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 Aug 6, 2026, at 7:39 AM, Ion Gaztañaga <igaztanaga@gmail.com> wrote:
The first release candidates for the 1.92.0 release are now available at: https://archives.boost.io/release/1.92.0/source/
The SHA256 checksums are as follows:
c4a3b310ddd2472416e091067166b0713be97c63f38c212c484ada022fd296ce boost_1_92_0_rc1.tar.gz
57f2ded2390068a44d88748425067e01a8c285257a4d9611d04ade9d8ec68615 boost_1_92_0_rc1.7z
c46baee75ed4b558cf6553630d0615a147ed582812917b57e6f0839d1954549f boost_1_92_0_rc1.zip
5c1d40cb8e19adbf740a4ec2da35b3e58f3f5804b1dce44deb53df72193cbc6c boost_1_92_0_rc1.tar.bz2
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 boost libraries using 'Apple clang version 21.0.0 (clang-2100.1.1.101)’ on a Mac M4 Mini using C++11/14/17/20/23/2C. There were far fewer warnings than before. logs/clang11-build.txt:17 logs/clang14-build.txt:21 logs/clang17-build.txt:21 logs/clang20-build.txt:24 logs/clang23-build.txt:28 logs/clang2c-build.txt:412 Most of them fall into two boxes: 1) Instantiating `std::char_trats` for types that are now deprecated. Spirit and xpressive, mostly. Example: In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/v1/string:602: /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/v1/__fwd/string.h:45:41: warning: 'char_traits<unsigned char>' is deprecated: char_traits<T> for T not equal to char, wchar_t, char8_t, char16_t or char32_t is non-standard and is provided for a temporary period. It will be removed in a future release, so please migrate off of it. [-Wdeprecated-declarations] 45 | template <class _CharT, class _Traits = char_traits<_CharT>, class _Allocator = allocator<_CharT> > | ^ ./boost/xpressive/traits/cpp_regex_traits.hpp:321:18: note: in instantiation of default argument for 'basic_string<char_type>' required here 321 | typedef std::basic_string<char_type> string_type; | ^~~~~~~~~~~~~~~~~~~~~~~ ./boost/xpressive/traits/cpp_regex_traits.hpp:673:22: note: in instantiation of template class 'boost::xpressive::cpp_regex_traits<unsigned char>' requested here 673 | inline unsigned char cpp_regex_traits<unsigned char>::hash(unsigned char ch) | ^ 2) Missing the final comma on a template argument list (C++26 only). These are mostly (if not all) in function_types. Example: ./boost/function_types/detail/components_impl/arity10_0.hpp:47:90: warning: declaration of a variadic function without a comma before '...' is deprecated [-Wdeprecated-missing-comma-variadic-parameter] 47 | typedef function_types::components<BOOST_FT_syntax(BOOST_FT_cc, BOOST_PP_EMPTY) (T0 , T1 BOOST_FT_ell) BOOST_FT_cv, L> type; | ^ | , ./boost/function_types/detail/pp_variate_loop/preprocessed.hpp:135:23: note: expanded from macro 'BOOST_FT_ell' 135 | # define BOOST_FT_ell ... | ^ I will be filing issues on these. But they’re not worth holding up the release for (IMNSHO) — Marshall
El 06/08/2026 a las 16:39, Ion Gaztañaga via Boost escribió:
The first release candidates for the 1.92.0 release are now available at: https://archives.boost.io/release/1.92.0/source/
The SHA256 checksums are as follows:
c4a3b310ddd2472416e091067166b0713be97c63f38c212c484ada022fd296ce boost_1_92_0_rc1.tar.gz
57f2ded2390068a44d88748425067e01a8c285257a4d9611d04ade9d8ec68615 boost_1_92_0_rc1.7z
c46baee75ed4b558cf6553630d0615a147ed582812917b57e6f0839d1954549f boost_1_92_0_rc1.zip
5c1d40cb8e19adbf740a4ec2da35b3e58f3f5804b1dce44deb53df72193cbc6c boost_1_92_0_rc1.tar.bz2
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.
Successfully built on these platforms/compiler: Windows / b2 toolset=msvc-14.1,msvc-14.2,msvc-14.3,msvc-14.5 address-model=64 Ubuntu 26.04 / b2 toolset=gcc-12,gcc-13,gcc-14,gcc-15,gcc-16 Ubuntu 24.04 / b2 toolset=gcc-10,gcc-11,gcc-12,gcc-13,gcc-14 However, some 32 bit Boost.Context windows buids failed on msvc-14.1 and 14.2. It this expected? ...failed updating 12 targets... msvc.compile.asm bin.v2\libs\context\build\msvc-14.1\debug\x86_32\link-static\threading-multi\asm\jump_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.1\debug\x86_32\link-static\threading-multi\asm\make_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.1\debug\x86_32\link-static\threading-multi\asm\ontop_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.1\release\x86_32\link-static\threading-multi\asm\jump_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.1\release\x86_32\link-static\threading-multi\asm\make_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.1\release\x86_32\link-static\threading-multi\asm\ontop_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.2\debug\x86_32\link-static\threading-multi\asm\jump_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.2\debug\x86_32\link-static\threading-multi\asm\make_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.2\debug\x86_32\link-static\threading-multi\asm\ontop_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.2\release\x86_32\link-static\threading-multi\asm\jump_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.2\release\x86_32\link-static\threading-multi\asm\make_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.2\release\x86_32\link-static\threading-multi\asm\ontop_i386_ms_pe_masm.obj Best, Ion Best, Ion
On Aug 7, 2026, at 4:24 PM, Ion Gaztañaga via Boost <boost@lists.boost.org> wrote:
However, some 32 bit Boost.Context windows buids failed on msvc-14.1 and 14.2. It this expected?
...failed updating 12 targets... msvc.compile.asm bin.v2\libs\context\build\msvc-14.1\debug\x86_32\link-static\threading-multi\asm\jump_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.1\debug\x86_32\link-static\threading-multi\asm\make_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.1\debug\x86_32\link-static\threading-multi\asm\ontop_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.1\release\x86_32\link-static\threading-multi\asm\jump_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.1\release\x86_32\link-static\threading-multi\asm\make_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.1\release\x86_32\link-static\threading-multi\asm\ontop_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.2\debug\x86_32\link-static\threading-multi\asm\jump_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.2\debug\x86_32\link-static\threading-multi\asm\make_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.2\debug\x86_32\link-static\threading-multi\asm\ontop_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.2\release\x86_32\link-static\threading-multi\asm\jump_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.2\release\x86_32\link-static\threading-multi\asm\make_i386_ms_pe_masm.obj msvc.compile.asm bin.v2\libs\context\build\msvc-14.2\release\x86_32\link-static\threading-multi\asm\ontop_i386_ms_pe_masm.obj
Did this happen on 1.91.0? — Marshall
Still seeing the same config issue I reported for the beta RC: - long double support : yes (cached) [2] - std_wstreambuf : yes (cached) [2] error: No best alternative for /D:/RB/boost_1_92_0/libs/graph_parallel/build/boost_graph_parallel with <abi>sysv <address-model>32 <architecture>x86 <asynch-exceptions>off <binary-format>elf <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <boost.cobalt.executor>any_io_executor <boost.cobalt.pmr>std <context-impl>fcontext <coverage>off <debug-store>object <debug-symbols>on <embed-manifest-via>linker <embed-manifest>on <exception-handling>on <extern-c-nothrow>off <inlining>off <known-warnings>hide <link>shared <midl-robust>yes <midl-stubless-proxy>yes <optimization>off <os>NT <pch>on <preserve-test-targets>on <profiling>off <python-debugging>off <python>3.14 <rtti>on <runtime-debugging>on <runtime-link>shared <stdlib>native <strip>off <target-os>windows <testing.execute>on <threadapi>win32 <threading>multi <toolset-msvc:version>14.1 <toolset>msvc <variant>debug <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <windows-api>desktop <x-deduced-platform>x86_32 matched: (empty) matched: (empty) - lzma : no (cached) [2] - zstd : no (cached) [2] Other than that, things look good on Windows/Visual Studio: 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 msvc-14.5 32 X X X msvc-14.5 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. Logs here: https://gist.github.com/teeks99/39e711e05d42fe58959360a1b3e42c7f Tom On Thu, Aug 6, 2026 at 9:41 AM Ion Gaztañaga via Boost < boost@lists.boost.org> wrote:
The first release candidates for the 1.92.0 release are now available at: https://archives.boost.io/release/1.92.0/source/
The SHA256 checksums are as follows:
c4a3b310ddd2472416e091067166b0713be97c63f38c212c484ada022fd296ce boost_1_92_0_rc1.tar.gz
57f2ded2390068a44d88748425067e01a8c285257a4d9611d04ade9d8ec68615 boost_1_92_0_rc1.7z
c46baee75ed4b558cf6553630d0615a147ed582812917b57e6f0839d1954549f boost_1_92_0_rc1.zip
5c1d40cb8e19adbf740a4ec2da35b3e58f3f5804b1dce44deb53df72193cbc6c boost_1_92_0_rc1.tar.bz2
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 _______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/U7DDTRXF...
for Windows '<abi>sysv' is wrong - I believe it should be '<abi>ms' 08.08.2026 04:16:00 Tom Kent via Boost <boost@lists.boost.org>:
Still seeing the same config issue I reported for the beta RC:
- long double support : yes (cached) [2] - std_wstreambuf : yes (cached) [2] error: No best alternative for /D:/RB/boost_1_92_0/libs/graph_parallel/build/boost_graph_parallel with <abi>sysv <address-model>32 <architecture>x86 <asynch-exceptions>off <binary-format>elf <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <boost.cobalt.executor>any_io_executor <boost.cobalt.pmr>std <context-impl>fcontext <coverage>off <debug-store>object <debug-symbols>on <embed-manifest-via>linker <embed-manifest>on <exception-handling>on <extern-c-nothrow>off <inlining>off <known-warnings>hide <link>shared <midl-robust>yes <midl-stubless-proxy>yes <optimization>off <os>NT <pch>on <preserve-test-targets>on <profiling>off <python-debugging>off <python>3.14 <rtti>on <runtime-debugging>on <runtime-link>shared <stdlib>native <strip>off <target-os>windows <testing.execute>on <threadapi>win32 <threading>multi <toolset-msvc:version>14.1 <toolset>msvc <variant>debug <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <windows-api>desktop <x-deduced-platform>x86_32 matched: (empty) matched: (empty) - lzma : no (cached) [2] - zstd : no (cached) [2]
Other than that, things look good on Windows/Visual Studio:
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 msvc-14.5 32 X X X msvc-14.5 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.
Logs here: https://gist.github.com/teeks99/39e711e05d42fe58959360a1b3e42c7f
Tom
On Thu, Aug 6, 2026 at 9:41 AM Ion Gaztañaga via Boost < boost@lists.boost.org> wrote:
The first release candidates for the 1.92.0 release are now available at: https://archives.boost.io/release/1.92.0/source/
The SHA256 checksums are as follows:
c4a3b310ddd2472416e091067166b0713be97c63f38c212c484ada022fd296ce boost_1_92_0_rc1.tar.gz
57f2ded2390068a44d88748425067e01a8c285257a4d9611d04ade9d8ec68615 boost_1_92_0_rc1.7z
c46baee75ed4b558cf6553630d0615a147ed582812917b57e6f0839d1954549f boost_1_92_0_rc1.zip
5c1d40cb8e19adbf740a4ec2da35b3e58f3f5804b1dce44deb53df72193cbc6c boost_1_92_0_rc1.tar.bz2
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 _______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/U7DDTRXF...
_______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/2H3PQRPO...
Hi, I've repeated the build and it looks like it was some kind of problem in my previous configuration. b2.exe toolset=msvc-14.1,msvc-14.2,msvc-14.3,msvc-14.5 address-model=32,64 worked fine: ...updated 16527 targets... The Boost C++ Libraries were successfully built! The following directory should be added to compiler include paths: D:\Data\LocalGit\boost_1_92_0 The following directory should be added to linker library paths: D:\Data\LocalGit\boost_1_92_0\stage\lib Thanks everyone. Best, Ion
Any ideas where that could be coming from? I'm pretty sure I don't set that manually. Tom On Sat, Aug 8, 2026 at 12:15 AM <oliver.kowalke@gmail.com> wrote:
for Windows '<abi>sysv' is wrong - I believe it should be '<abi>ms'
08.08.2026 04:16:00 Tom Kent via Boost <boost@lists.boost.org>:
Still seeing the same config issue I reported for the beta RC:
- long double support : yes (cached) [2] - std_wstreambuf : yes (cached) [2] error: No best alternative for /D:/RB/boost_1_92_0/libs/graph_parallel/build/boost_graph_parallel with <abi>sysv <address-model>32 <architecture>x86 <asynch-exceptions>off <binary-format>elf <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <boost.cobalt.executor>any_io_executor <boost.cobalt.pmr>std <context-impl>fcontext <coverage>off <debug-store>object <debug-symbols>on <embed-manifest-via>linker <embed-manifest>on <exception-handling>on <extern-c-nothrow>off <inlining>off <known-warnings>hide <link>shared <midl-robust>yes <midl-stubless-proxy>yes <optimization>off <os>NT <pch>on <preserve-test-targets>on <profiling>off <python-debugging>off <python>3.14 <rtti>on <runtime-debugging>on <runtime-link>shared <stdlib>native <strip>off <target-os>windows <testing.execute>on <threadapi>win32 <threading>multi <toolset-msvc:version>14.1 <toolset>msvc <variant>debug <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <windows-api>desktop <x-deduced-platform>x86_32 matched: (empty) matched: (empty) - lzma : no (cached) [2] - zstd : no (cached) [2]
Other than that, things look good on Windows/Visual Studio:
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 msvc-14.5 32 X X X msvc-14.5 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.
Logs here: https://gist.github.com/teeks99/39e711e05d42fe58959360a1b3e42c7f
Tom
On Thu, Aug 6, 2026 at 9:41 AM Ion Gaztañaga via Boost < boost@lists.boost.org> wrote:
The first release candidates for the 1.92.0 release are now available at: https://archives.boost.io/release/1.92.0/source/
The SHA256 checksums are as follows:
c4a3b310ddd2472416e091067166b0713be97c63f38c212c484ada022fd296ce boost_1_92_0_rc1.tar.gz
57f2ded2390068a44d88748425067e01a8c285257a4d9611d04ade9d8ec68615 boost_1_92_0_rc1.7z
c46baee75ed4b558cf6553630d0615a147ed582812917b57e6f0839d1954549f boost_1_92_0_rc1.zip
5c1d40cb8e19adbf740a4ec2da35b3e58f3f5804b1dce44deb53df72193cbc6c boost_1_92_0_rc1.tar.bz2
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 _______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at:
https://lists.boost.org/archives/list/boost@lists.boost.org/message/U7DDTRXF...
_______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/2H3PQRPO...
On 11 Aug 2026 00:58, Tom Kent via Boost wrote:
Any ideas where that could be coming from? I'm pretty sure I don't set that manually.
https://github.com/boostorg/context/blob/cc1b9e02cd530d6607becc984e1e5bfa4f7... sysv is set by default. The default_abi rule is used by Boost.Context project in private requirements, i.e. it applies only to Boost.Context. If I'm not mistaken, for everyone else the sysv default remains in effect unless abi is specified on the command line. I think, the feature should be made optional with no default. Boost.Context can continue to use the default_abi rule to deduce it from the target platform, for everyone else it should not be set.
On Sat, Aug 8, 2026 at 12:15 AM <oliver.kowalke@gmail.com> wrote:
for Windows '<abi>sysv' is wrong - I believe it should be '<abi>ms'
08.08.2026 04:16:00 Tom Kent via Boost <boost@lists.boost.org>:
Still seeing the same config issue I reported for the beta RC:
- long double support : yes (cached) [2] - std_wstreambuf : yes (cached) [2] error: No best alternative for /D:/RB/boost_1_92_0/libs/graph_parallel/build/boost_graph_parallel with <abi>sysv <address-model>32 <architecture>x86 <asynch-exceptions>off <binary-format>elf <boost.beast.allow-deprecated>on <boost.beast.separate-compilation>on <boost.cobalt.executor>any_io_executor <boost.cobalt.pmr>std <context-impl>fcontext <coverage>off <debug-store>object <debug-symbols>on <embed-manifest-via>linker <embed-manifest>on <exception-handling>on <extern-c-nothrow>off <inlining>off <known-warnings>hide <link>shared <midl-robust>yes <midl-stubless-proxy>yes <optimization>off <os>NT <pch>on <preserve-test-targets>on <profiling>off <python-debugging>off <python>3.14 <rtti>on <runtime-debugging>on <runtime-link>shared <stdlib>native <strip>off <target-os>windows <testing.execute>on <threadapi>win32 <threading>multi <toolset-msvc:version>14.1 <toolset>msvc <variant>debug <vectorize>off <visibility>hidden <warnings-as-errors>off <warnings>on <windows-api>desktop <x-deduced-platform>x86_32 matched: (empty) matched: (empty) - lzma : no (cached) [2] - zstd : no (cached) [2]
Other than that, things look good on Windows/Visual Studio:
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 msvc-14.5 32 X X X msvc-14.5 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.
Logs here: https://gist.github.com/teeks99/39e711e05d42fe58959360a1b3e42c7f
Tom
On Thu, Aug 6, 2026 at 9:41 AM Ion Gaztañaga via Boost < boost@lists.boost.org> wrote:
The first release candidates for the 1.92.0 release are now available at: https://archives.boost.io/release/1.92.0/source/
The SHA256 checksums are as follows:
c4a3b310ddd2472416e091067166b0713be97c63f38c212c484ada022fd296ce boost_1_92_0_rc1.tar.gz
57f2ded2390068a44d88748425067e01a8c285257a4d9611d04ade9d8ec68615 boost_1_92_0_rc1.7z
c46baee75ed4b558cf6553630d0615a147ed582812917b57e6f0839d1954549f boost_1_92_0_rc1.zip
5c1d40cb8e19adbf740a4ec2da35b3e58f3f5804b1dce44deb53df72193cbc6c boost_1_92_0_rc1.tar.bz2
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 _______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at:
https://lists.boost.org/archives/list/boost@lists.boost.org/message/U7DDTRXF...
_______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/2H3PQRPO...
_______________________________________________ Boost mailing list -- boost@lists.boost.org To unsubscribe send an email to boost-leave@lists.boost.org https://lists.boost.org/mailman3/lists/boost.lists.boost.org/ Archived at: https://lists.boost.org/archives/list/boost@lists.boost.org/message/725GNP7U...
On Thu, 6 Aug 2026 at 16:41, Ion Gaztañaga via Boost <boost@lists.boost.org> wrote:
The first release candidates for the 1.92.0 release are now available at: https://archives.boost.io/release/1.92.0/source/
The SHA256 checksums are as follows:
c4a3b310ddd2472416e091067166b0713be97c63f38c212c484ada022fd296ce boost_1_92_0_rc1.tar.gz
57f2ded2390068a44d88748425067e01a8c285257a4d9611d04ade9d8ec68615 boost_1_92_0_rc1.7z
c46baee75ed4b558cf6553630d0615a147ed582812917b57e6f0839d1954549f boost_1_92_0_rc1.zip
5c1d40cb8e19adbf740a4ec2da35b3e58f3f5804b1dce44deb53df72193cbc6c boost_1_92_0_rc1.tar.bz2
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 under Ubuntu 24.04, clang-22 cxxstd=26. The same warnings reported by Matt, plus a couple of warnings from Cobalt (see below). Regards, Ruben. ./boost/cobalt/detail/main.hpp:31:5: warning: 'main' should not be 'extern "C"' [-Wmain] 31 | int main(int argc, char * argv[]); | ^ 1 warning generated. [redacted]/boost_1_92_0/libs/cobalt/src/io/ssl.cpp:113:45: warning: unused variable 'loc' [-Wunused-variable] 113 | constexpr static boost::source_location loc{BOOST_CURRENT_LOCATION};
participants (6)
-
Andrey Semashev -
Ion Gaztañaga -
Marshall Clow -
oliver.kowalke＠gmail.com -
Ruben Perez -
Tom Kent