December 2020 - Boost-users

Boost 1.75.0 Release Candidate 1 -- macOS
by DV Henkel-Wallace 10 Dec '20

10 Dec '20

> Date: Thu, 3 Dec 2020 06:54:13 -0800 > From: Marshall Clow <mclow.lists(a)gmail.com <mailto:mclow.lists@gmail.com>> > > > [release] Boost 1.75.0 Release Candidate 1 > Built fine on macOS 11.0.1 using llvm 11.0.0 ./b2 cxxstd=2a boost.locale.icu=off boost.locale.std=off threading=multi -sNO_COMPRESSION=1 Darwin KA-19.local 20.1.0 Darwin Kernel Version 20.1.0: Sat Oct 31 00:07:11 PDT 2020; root:xnu-7195.50.7~2/RELEASE_X86_64 x86_64 clang version 11.0.0 Target: x86_64-apple-darwin20.1.0 Lots of deprecated warnings for use of boost/bind.hpp and boost/detail/iterator.hpp as well as using enums as bitfields. But otherwise OK.

2 1

QT MinGW32 : bootstrap stacktrace (header only) not showing function names and lines numbers shows only address
by Mehdi Est 05 Dec '20

05 Dec '20

Hi Everyone, I am trying to print stack-trace using boost *HEADER-ONLY. *I am using descriptions under Configuration and Build <https://www.boost.org/doc/libs/1_74_0/doc/html/stacktrace/configuration_and…> to compile a simple code using QT MinGW32 I also use the below macros to tune boost: -DBOOST_STACKTRACE_USE_WINDBG -DBOOST_STACKTRACE_USE_ADDR2LINE -DBOOST_STACKTRACE_ADDR2LINE_LOCATION I have no clue why the function names and line numbers are not showing up. Any comment is appreciated. Mike *Below are compile and build instructions:* g++ -g3 -DBOOST_STACKTRACE_USE_WINDBG -DBOOST_STACKTRACE_USE_ADDR2LINE -DBOOST_STACKTRACE_ADDR2LINE_LOCATION=C:\Qt_5_12\Tools\mingw730_32\bin\addr2line.exe -I../../../boost_1_73_0 -c main.cpp -omain.o g++ main.o -o stack_traces.exe -L"C:\Program Files (x86)\Windows Kits\10\Lib\10.0.19041.0\um\x86" -L"C:\temp\libbacktrace" -lkernel32 -luser32 -lgdi32 -lwinspool -lcomdlg32 -ladvapi32 -lshell32 -lole32 -luuid -lodbc32 -lodbccp32 -lDbgEng *And here is the output ... * 0# 0x00402C75 in stack_traces 1# 0x00401602 in stack_traces 2# 0x004016CE in stack_traces 3# 0x0040138B in stack_traces 4# _BaseThreadInitThunk in KERNEL32 5# _RtlGetAppContainerNamedObjectPath in ntdll 6# _RtlGetAppContainerNamedObjectPath in ntdll 1 + 2 = 3 *The code (main.cpp)* Is fairly simple as below: #include <iostream> #include <boost/stacktrace.hpp> double add(double a, double b){ std::cout << boost::stacktrace::stacktrace(); std::cout << a << " + " << b << " = " << (a+b) << std::endl; return a+b; } int main(){ add(1,2); return 0; }

2 2

[release] Boost 1.75.0 Release Candidate 1
by Marshall Clow 04 Dec '20

04 Dec '20

[release] Boost 1.75.0 Release Candidate 1 The first release candidates for the 1.75.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.75.0/source/> The SHA256 checksums are as follows: caf36d7c13b3d8ce62282a64a695113945a13b0f1796a45160726d04295f95ed boost_1_75_0_rc1.zip aeb26f80e80945e82ee93e5939baebdca47b9dee80a07d3144be1e1a6a66dd6a boost_1_75_0_rc1.tar.gz 953db31e016db7bb207f11432bef7df100516eeb746843fa0486a222e3fd49cb boost_1_75_0_rc1.tar.bz2 3a8b314871646e7404886736273c053278ba71b11347f72d4751411d65d6d1a5 boost_1_75_0_rc1.7z 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 4

Boost.Numeric.Interval: Please specify rounding control mechanism
by Bastien Commelongue 01 Dec '20

01 Dec '20

Hello, I am building an app for IOS (ARM) and I had this issue while compiling: *Boost.Numeric.Interval: Please specify rounding control mechanism.* C99 version should be used in this case but __USE_ISOC99 is not defined. Modifying the condition with this code (using __cplusplus) fixed the issue: *boost/numeric/interval/hw_rounding.hpp(36)* *#if defined(BOOST_NUMERIC_INTERVAL_NO_HARDWARE) && (defined(__USE_ISOC99) || defined(__MSL__) || (defined __cplusplus && __cplusplus >= 201103L))# include <boost/numeric/interval/detail/c99_rounding_control.hpp>#endif* Let me know if I missed something or if you plan to integrate this modification in a next version. Cheers, Bastien Commelongue

2 1