- Boost-users - lists.boost.org

[release] Boost 1.73.0
by Marshall Clow 28 Apr '20

28 Apr '20

Release 1.73.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains 2 new libraries and numerous enhancements and bug fixes for existing libraries. For details, including download links, see < http://www.boost.org/users/news/version_1.73.0> You can also download directly from: < https://dl.bintray.com/boostorg/release/1.73.0/> To install this release on your system, see < http://www.boost.org/doc/libs/release/more/getting_started/index.html> Thanks to everyone who participated in this release. Thanks, -- The Boost Release Team Marshall Clow, Micheal Caisse and Glen Fernandes

1 0

[release] Boost 1.73.0 Release Candidate 1
by Marshall Clow 26 Apr '20

26 Apr '20

The first release candidates for the 1.73.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.73.0/source/> The SHA256 checksums are as follows: d2e7501bb04fe7abc09aa93f013ae997604286a882da1bd36ddd96ea1163ea71 boost_1_73_0_rc1.7z 4eb3b8d442b426dc35346235c8733b5ae35ba431690e38c6a8263dce9fcbb402 boost_1_73_0_rc1.tar.bz2 9995e192e68528793755692917f9eb6422f3052a53c5e13ba278a228af6c7acf boost_1_73_0_rc1.tar.gz 0909a79524f857ef54570ceef8f397cc0629202532cc997785479c7c08bbc2a4 boost_1_73_0_rc1.zip 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

3 7

Using coroutines in ASIO
by Pedro Pinto 25 Apr '20

25 Apr '20

Hi there, I am trying to compile the asio co-routine example but as far as I can tell boost is looking for an <experimental/coroutine> header that does not exist on my system. I am using boost 1.71 and gcc on ubuntu 20.04. I tried both stock gcc (v9 on ubuntu) which does not have a coroutine header and gcc 10 which does have it but not under the experimental directory. Here is the output with gcc 10: /usr/lib/ccache/g++ -I../../src -g -Wall -pedantic -Wextra -Werror -DASIO_HAS_CO_AWAIT -DBOOST_ASIO_HAS_CO_AWAIT -fcoroutines --std=c++2a -fdiagnostics-color -MD -MT CMakeFiles/mcbridge.dir /src/main.cpp.o -MF CMakeFiles/mcbridge.dir/src/main.cpp.o.d -o CMakeFiles/mcbridge.dir/src/main.cpp.o -c ../../src/main.cpp In file included from /usr/include/boost/asio/co_spawn.hpp:22, from ../../src/main.cpp:4: /usr/include/boost/asio/awaitable.hpp:22:10: fatal error: experimental/coroutine: No such file or directory 22 | #include <experimental/coroutine> Any ideas on how to compile this example?

2 1

10 slots for the Google Summer of Code 2020
by David Bellot 22 Apr '20

22 Apr '20

Hi Boost community, this year Google allocated 10 slots for the Google Summer of Code. It's again a great achievement thanks to the hard work of our team of dedicated mentors. We are now selecting the best students among all the proposals we receive. We received 79 proposals this year. 10 of them will be selected. This year, a lot of proposals if not all are targeting a finalization of the work which has been done in the previous GSoCs and we should see a lot of code being pushed in production. It's a very exciting time for all of us. The mentors are now hard at work to choose the students. We'll keep you informed when it's official. Best regards, David

1 0

Re: [Boost-users] [random_device] App crash on boost::ramdom::random_device
by 박형근(HYUNGGUN PARK) 22 Apr '20

22 Apr '20

> On Fri, Apr 17, 2020 at 10:29 AM 박형근(HYUNGGUN PARK) via Boost-users > <boost-users(a)lists.boost.org> wrote: > > > > My app crash on customer's site. It crashes everytime the app is > starting. > > It happens on Chinese Windows7 (64bit) OS but it runs well on my PC > > with > Korean Windows7 OS and English Windows7 OS. > > My app is built on VisualStudio 2010 (x86 build, C++) using > > websocketpp > library and boost 1.55. > > The call-stack from the dump file shows my app(TMSClient100) called > websocketpp::endpoint, then it called boost::random::random_device > then ThrowException. Here's the call-stack info: > > > > 14 001cf6ac 7113872d e06d7363 00000001 00000003 > > KERNELBASE!RaiseException+0x58 > > 15 001cf6e4 713b7c5a 001cf704 713d9350 b621b77b > > msvcr100!_CxxThrowException+0x48 > > [f:\dd\vctools\crt_bld\self_x86\crt\prebuild\eh\throw.cpp @ 157] > > 16 001cf814 713b7da3 001cf840 b621b9a7 002a19bc > > TMSClient100!boost::random::random_device::impl::error+0x15a > > 17 001cf8b8 713b7f7b 001cf8dc b621b94b 00000000 > > TMSClient100!boost::random::random_device::impl::impl+0x143 > > Check the exception message. Is it failing because it: > 1. Could not find a provider name > 2. Could not acquire CSP context > > If #1, this might be solved by upgrading from Boost 1.55 to a newer > version. This fix in particular: > https://github.com/boostorg/random/commit/dc2fdeac443fb56c87a03a0887c9 > e7c8 > e1d3296d > went into Boost 1.56. > > Glen Glen, Thank you for your reply. Thanks to your suggestion, upgrade from Boost 1.55 to 1.56 solved this problem. Thank you very much. Harry

1 0

[Boost] [test] strange behaviour when comparing floating point numbers
by Matthijs Möhlmann 21 Apr '20

21 Apr '20

Hi, I am trying to compare two floating point numbers but am encountering somewhat strange behaviour. The minimal compilable example: #define BOOST_TEST_MODULE tests #define BOOST_TEST_DYN_LINK #include <boost/test/unit_test.hpp> BOOST_AUTO_TEST_SUITE(testsuite) BOOST_AUTO_TEST_CASE(test1) { namespace tt = boost::test_tools; BOOST_TEST(0.1 == 0.2, tt::tolerance(0.01)); // will fail BOOST_TEST(0.1f == 0.2f, tt::tolerance(0.02)); // will fail too, but different error message... } BOOST_AUTO_TEST_SUITE_END() When compiling with: clang++ (clang version 7.0.1-8 (tags/RELEASE_701/final)) flags: -o main -g -std=c++17 -stdlib=libc++ -lboost_unit_test_framework main.cpp boost: 1.72.0 I'll get the following output: Running 1 test case... main.cpp(10): error: in "testsuite/test1": check 0.1 == 0.2 has failed [0.10000000000000001 != 0.20000000000000001]. Relative difference exceeds tolerance [1 > 0.01] main.cpp(11): error: in "testsuite/test1": check 0.1f == 0.2f has failed [0.100000001 != 0.200000003] *** 2 failures are detected in the test module "tests" Why am I getting two different messages? I expected those to be the same... Regards, Matthijs

2 2

[program_options] cmake discovery issue
by Jeanette C. 21 Apr '20

21 Apr '20

Hello, I can't say when these errors first appeared, certainly not in Boost 1.63 . I have a project working with cmake and the following cmmake lines: set(Boost_USE_MULTITHREADED ON) find_package(Boost 1.58 REQUIRED COMPONENTS program_options filesystem date_time system) if (Boost_PROGRAM_OPTIONS_FOUND) set (INCS ${INCS} ${Boost_INCLUDE_DIRS}) set (LIBS ${LIBS} ${Boost_PROGRAM_OPTIONS_LIBRARY} ${Boost_SYSTEM_LIBRARY}) endif (Boost_PROGRAM_OPTIONS_FOUND) Which says that it found the libraries and lower down produces this error: CMake Error in CMakeLists.txt: Imported target "Boost::program_options" includes non-existent path "/include" in its INTERFACE_INCLUDE_DIRECTORIES. Possible reasons include: * The path was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and references files it does not provide. This error appears twice in the output. My cmake skills are too meagre to trace it to a particular point in the Boost Cmake modules. Could someone please help? Is it perhaps my fault for not updating a call somewhere? Best wishes and TIA, Jeanette -- * Website: http://juliencoder.de - for summer is a state of sound * Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g * SoundCloud: https://soundcloud.com/jeanette_c * Twitter: https://twitter.com/jeanette_c_s * Audiobombs: https://www.audiobombs.com/users/jeanette_c * GitHub: https://github.com/jeanette-c There's no time to loose And next week, You might not see me here <3 (Britney Spears)

1 0

Continuous Deployment of Boost.Beast-based server
by Dominique Devienne 21 Apr '20

21 Apr '20

Imagine I have a WebSocket server, implemented using Boost.Asio and Boost.Beast. It's deployed and serving clients in production or test environments, but I fixed a bug, checked in a fix, passed CI, and would like to redeploy, but w/o downtime for existing clients. New clients should use the same address, but be served by the newly deployed fixed server. While on-ongoing WebSocket connections keep on using the old server. Is that possible? In-process? Or one must use some kind of "front-end server" redirecting new traffic (i.e. new WebSocket session and/or HTTP requests) to separate processes? (nginx? little GoLang exe? In C++ Boost.Asio based? else?) If not possible in-process, then how to know when older server is no longer in use, to gracefully stop it? Asio servers typically run forever, i.e. never run out of work, even when they temporarily have nothing to do, by design. The goal is to do this on "premise" (i.e. not in the cloud), on a single machine (no containers), and cross-platform (Windows and Linux). Thanks, --DD

3 6

Building boost 1.72 with arm 64 bit gcc compiler
by Rahul Sreeram 20 Apr '20

20 Apr '20

Hi, I am trying to build boost 1.72 with arm 64 bit compiler. I am seeing the error: No best alternative for libs/context/build/asm_sources Although, after getting this error, compilation looks to succeed, but I am not sure if it did properly or not. I have this line in the project-config.jam: using gcc : arm : aarch64-fsl-linux-g++ --sysroot=/sysroots/aarch64-fsl-linux ; After running b2, I get the following output: ./b2 toolset=gcc-arm Performing configuration checks - default address-model : 64-bit - default architecture : arm Building the Boost C++ Libraries. error: No best alternative for libs/context/build/asm_sources next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>qcc not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>pe <threading>multi <toolset>msvc not matched next alternative: required properties: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>o32 <address-model>32 <architecture>mips1 <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>o32 <address-model>32 <architecture>mips1 <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>n64 <address-model>64 <architecture>mips1 <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>n64 <address-model>64 <architecture>mips1 <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>xcoff <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>xcoff <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>xcoff <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>xcoff <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>32_64 <architecture>power <binary-format>mach-o <threading>multi not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>riscv <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>s390x <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf <threading>multi <toolset>intel not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>clang not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>clang-win not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>intel not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>msvc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>intel not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>intel not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>clang not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>clang-win not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>intel not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>msvc not matched next alternative: required properties: <abi>x32 <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>x32 <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>x32 <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>intel not matched next alternative: required properties: <abi>sysv <address-model>32_64 <architecture>x86 <binary-format>mach-o <threading>multi not matched next alternative: required properties: <abi>sysv <architecture>combined <binary-format>mach-o <threading>multi not matched - C++11 mutex : yes - lockfree boost::atomic_flag : yes - Boost.Config Feature Check: cxx11_auto_declarations : yes - Boost.Config Feature Check: cxx11_constexpr : yes - Boost.Config Feature Check: cxx11_defaulted_functions : yes - Boost.Config Feature Check: cxx11_final : yes - Boost.Config Feature Check: cxx11_hdr_mutex : yes - Boost.Config Feature Check: cxx11_hdr_tuple : yes - Boost.Config Feature Check: cxx11_lambdas : yes - Boost.Config Feature Check: cxx11_noexcept : yes ...... Regards, Rahul

3 2

[random_device] App crash on boost::ramdom::random_device
by 박형근(HYUNGGUN PARK) 17 Apr '20

17 Apr '20

Hi there! My app crash on customer's site. It crashes everytime the app is starting. It happens on Chinese Windows7 (64bit) OS but it runs well on my PC with Korean Windows7 OS and English Windows7 OS. My app is built on VisualStudio 2010 (x86 build, C++) using websocketpp library and boost 1.55. The call-stack from the dump file shows my app(TMSClient100) called websocketpp::endpoint, then it called boost::random::random_device then ThrowException. Here's the call-stack info: 14 001cf6ac 7113872d e06d7363 00000001 00000003 KERNELBASE!RaiseException+0x58 15 001cf6e4 713b7c5a 001cf704 713d9350 b621b77b msvcr100!_CxxThrowException+0x48 [f:\dd\vctools\crt_bld\self_x86\crt\prebuild\eh\throw.cpp @ 157] 16 001cf814 713b7da3 001cf840 b621b9a7 002a19bc TMSClient100!boost::random::random_device::impl::error+0x15a 17 001cf8b8 713b7f7b 001cf8dc b621b94b 00000000 TMSClient100!boost::random::random_device::impl::impl+0x143 18 001cf904 71383901 b621b8ab 001cfac4 002a17e8 TMSClient100!boost::random::random_device::random_device+0x8b 19 001cf928 7137eb2c 002a17e8 b621b8ef 001cfac4 TMSClient100!websocketpp::endpoint<websocketpp::connection<websocketpp::config::asio_client>,websocketpp::config::asio_client>::endpoint<websocketpp::connection<websocketpp::config::asio_client>,websocketpp::config::asio_client>+0x191 [d:\dev\tms\trunk\library\library_c++_3\websocketpp\websocketpp\endpoint.hpp @ 101] 1a 001cf96c 713598c2 002a1790 b621b83b 001cfa08 TMSClient100!TMS::CWebSocketClient::CWebSocketClient+0x9c [d:\dev\tms\trunk\library\library_c++_3\tmsclient100\websocketclient.cpp @ 15] 1b 001cf9b8 010316cd b620327e 00388fa8 0103c908 TMSClient100!TMS::CTMSClient::CTMSClient+0xf2 [d:\dev\tms\trunk\library\library_c++_3\src\tmsclient.cpp @ 25] Any suggestion how to debug this problem will be greatly appreciated. Harry Park

3 2