- Boost - lists.boost.org

[release] Boost 1.80.0 beta 1 released
by Glen Fernandes 14 Jul '22

14 Jul '22

Boost release 1.80.0 beta 1 is now available at: https://boostorg.jfrog.io/artifactory/main/beta/1.80.0.beta1/source/ The SHA256 checksums are: boost_1_80_0_b1.tar.bz2 - b29191c1bd4504511f9b1155c6f79f06cc7044444780392ed7358f5778ac7d16 boost_1_80_0_b1.tar.gz - ad3df9f63acd667dcf13375fa0e90e7303f851251e91d1505974bdbbf1f94907 boost_1_80_0_b1.7z - 7bfdf705b1d058c3525be90ed5cb47aacf919cd74aa7d5752d55e78aa60880ba boost_1_80_0_b1.zip - 1b509ed848f153086984658d4d4a57af6230f496a53bf88aba805bb49039012d Release notes (still need updates): https://www.boost.org/users/history/version_1_80_0.html Please try the beta and report any problems you encounter. Thanks, -- Boost Release Team

5 10

[release] Boost 1.80.0 Beta 1 Release Candidate 1 is available
by Marshall Clow 14 Jul '22

14 Jul '22

Available at: <https://boostorg.jfrog.io/ui/native/main/beta/1.80.0.beta1/source> The SHA256 checksums are as follows: b29191c1bd4504511f9b1155c6f79f06cc7044444780392ed7358f5778ac7d16 boost_1_80_0_b1.tar.bz2 7bfdf705b1d058c3525be90ed5cb47aacf919cd74aa7d5752d55e78aa60880ba boost_1_80_0_b1.7z ad3df9f63acd667dcf13375fa0e90e7303f851251e91d1505974bdbbf1f94907 boost_1_80_0_b1.tar.gz 1b509ed848f153086984658d4d4a57af6230f496a53bf88aba805bb49039012d boost_1_80_0_b1.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

5 6

[Graph] Can users on Xcode 7-10 help out?
by Jeremy Murphy 12 Jul '22

12 Jul '22

Dear Boost.Graph users, Is anyone that uses old Xcode 7-10 able to help out with some curious compilation errors? https://github.com/boostorg/graph/issues/298 We'll do our best to fix them but I assume it might be easier for someone that actually uses these particular platforms. Thanks, cheers. Jeremy

1 0

static_string
by Gero Peterhoff 10 Jul '22

10 Jul '22

Hello, if i include <boost/static_string.hpp> i get errors in std::variant: /usr/include/c++/12/variant:774:72: Fehler: Templateargument 4 ist ungültig 774 | void_t<decltype(_Arr<_Ti>{{std::declval<_Tp>()}})>> | ^~ /usr/include/c++/12/variant:804:76: Fehler: Templateargument 3 ist ungültig 804 | struct __accepted_index<_Tp, _Variant, void_t<_FUN_type<_Tp, _Variant>>> | ^ Can you retrace that? boost 1.79 gcc 12.1 -std=gnu++2b openSuse Tumbleweed thx Gero

3 2

[process] Process.Spawn leaves the child in zombie state on posix
by Benedek Tass 08 Jul '22

08 Jul '22

Hi, everyone! This bug was observed in 2022.07.05, using boost version 1.79.0. Similar behaviour was commented on before on online messageboards. Bug description When starting a new, detached process with Process.Spawn in a posix system, if the parent process outlives the child, the child process remains in zombie state for the parent process' lifetime. The bug described above is demonstrated in the CMake project attached to this document. Analysis The spawn function injects the syscall "signal(SIGCHLD, SIG_IGN)" with a functor of type boost::process::detail::posix::sig_init_. This is done to the forked child process, to no avail. And this is not done (and should not be done) in the parent process being too intrusive. Possible mitigation Introducing an in-between forked process that serves as the parent of the to-be-spawned process with SIGCHLD set to SIG_IGN would prevent the spawned process to become zombie, and simultaneously does not disturb the parent process' signal handlers. Introducing another class alternative to sig_init_ with the functionality described above would be a reasonable approach. An implementation sketch of the double fork method can be found in the attached project. System used OS: Ubuntu 18.04.6 LTS arch: x86_64 compiler: gcc-7.5.0 libc: libc-2.27 boost: 1.79.0 (built from source) Best regards, Benedek Tass

3 6

Boost 1.80.0 closed for beta
by Glen Fernandes 07 Jul '22

07 Jul '22

Master is closed for all changes. See the release schedule at: https://www.boost.org/development/index.html -- Release managers

2 1

Boost 1.80 closed for all major changes
by Glen Fernandes 05 Jul '22

05 Jul '22

The next deadlines: - On 2022-07-06 master is closed for all changes. - On 2022-07-13 the beta is published -- Release Managers

3 6

Re: [boost] [Boost-users] Boost.URL review planned for 13-22 August 2022
by Vinnie Falco 29 Jun '22

29 Jun '22

On Fri, Jun 24, 2022 at 2:15 AM Mateusz Loskot via Boost-users <boost-users(a)lists.boost.org> wrote: > we have planned the review shortly after the upcoming release of the Boost 1.80. The review starts in August but there is no rule that says folks can't look at the library sooner :) The library is in very good shape and likely usable for your project today (although we do expect bugs to be found, which will be fixed as they get reported). Check it out here: <https://github.com/CPPAlliance/url> Docs: <https://master.url.cpp.al/> We're glad to answer any questions at any time either on the list or feel free to open an issue in the repository (even if it is just a question). Thanks

2 1

Boost Regression Results Not Updating
by Tom Kent 25 Jun '22

25 Jun '22

I just noticed that something happened with the regression results and they haven't updated since last Friday. https://www.boost.org/development/tests/master/developer/summary.html https://www.boost.org/development/tests/develop/developer/summary.html I'm not sure where these run these days, would it fit in a github action on the regression repo? Tom

3 3

Possible develop config issue on arm32
by Tom Kent 25 Jun '22

25 Jun '22

I have a regression runner running on raspberry pi 32-bit architecture (in addition to a one on 64-bit raspberry pi and tons of X86). gcc-8 builds fine in both master and develop clang-9 builds fine on master clang-9 running the same command line, just on develop, has errors like this [1], finding basic includes: ``` "clang++-9" -c -x c++ -Wno-c99-extensions -std=c++2a -O0 -fno-inline -Wall -g --target=arm-pc-linux -Wno-deprecated-declarations -DBOOST_ALL_NO_LIB=1 -DBOOST_BEAST_ALLOW_DEPRECATED -DBOOST_BEAST_SEPARATE_COMPILATION -DBOOST_TEST_NO_AUTO_LINK=1 -I".." -o "/mnt/fs1/teeks99-05/run/results/boost/bin.v2/libs/accumulators/test/count.test/clang-linux-9~c++2a/debug/link-static/count.o" "../libs/accumulators/test/count.cpp" clang: warning: unknown platform, assuming -mfloat-abi=soft clang: warning: unknown platform, assuming -mfloat-abi=soft In file included from ../libs/accumulators/test/count.cpp:6: In file included from ../boost/test/unit_test.hpp:18: In file included from ../boost/test/test_tools.hpp:17: In file included from ../boost/config.hpp:44: ../boost/config/detail/select_stdlib_config.hpp:26:14: fatal error: 'cstddef' file not found # include <cstddef> ^~~~~~~~~ 1 error generated. ``` The relevant line of the user-config.jam is: using clang : 9~c++2a : clang++-9 : <cxxflags>"-Wno-c99-extensions -std=c++2a" ; The two command lines being run are: run.py --runner=teeks99-05-mc9-2a-32onarmv7l --toolsets=clang-9~c++2a \ "--bjam-options=-j4 address-model=32 --remove-test-targets" \ --comment=info.html --tag=master run.py --runner=teeks99-05-dc9-2a-32onarmv7l --toolsets=clang-9~c++2a \ "--bjam-options=-j4 address-model=32 --remove-test-targets" \ --comment=info.html --tag=develop Any ideas why master and develop would be different in this regard? Something with B2 changes? Thanks, Tom [1] https://www.boost.org/development/tests/develop/developer/output/teeks99-05…

3 2