- Boost - lists.preview.boost.org

2024 Q1 Transparency report
by Louis Tatta 16 May '24

16 May '24

Hello, Louis Tatta here, CEO of The C++ Alliance, Inc, a registered 501(c)(3) non-profit organization dedicated to the support of C++. This is our Q1 2024 transparency report regarding our charitable work for the Boost C++ Library Collection. First, some background on our operations. The C++ Alliance seeks out highly talented and experienced C++ experts and hires them, usually full-time, so they can focus completely on their open-source projects. Our Staff Engineers maintain existing Boost libraries, write new Boost libraries, and contribute to other Boost projects. We employ IT experts full-time to maintain and improve the infrastructure which supports Boost, including the legacy web server, the Drone continuous integration servers, the scripts used to deploy GitHub Actions for Boost repositories, and the scripts which publish the Boost release. In addition, we provide on-demand technical support services for Boost authors and maintainers who have infrastructure-related problems. The Boost Mailing List continues to be the premier place for high-quality discussion of the Boost libraries and tangential C++ Standards related topics. The C++ Alliance supports the use of the mailing lists going forward. We are upgrading it to the latest Mailman version and building an optional web-based front-end allowing interaction using only a browser. We continue to operate the Official C++ Language Slack Workspace ( https://cpp.al/slack) which hosts the most popular interactive discussions regarding the Boost libraries. The C++ Alliance sponsors a paid plan to provide full history, video and audio conferences, collaboration tools, and unlimited document storage for seventeen dedicated Boost library channels and one main Boost discussion channel. Our largest project for Q1 2024 is the continuation of work on the new Boost website. The new site is a C++ social media portal with rich support for user-generated content and a powerful back-end which has visibility into the contributions made on GitHub and the release process. This allows us to deliver an elevated user experience with the hopes of attracting fresh talent to Boost. Also, note that the graphics on the website are hand-drawn by our contract artist and reflect our level of commitment to ensure that Boost, to put it simply, looks good. In Q1 2024 there were a total of two Boost Formal Reviews. One of the reviewed libraries is authored by a C++ Alliance Staff Engineer. None of the reviews were managed by C++ Alliance team members. Out of a total of sixteen submitted reviews for the quarter, eight were from C++ Alliance team members. This quarter, we increased our efforts to build Boost’s social media presence. There were a total of six messages from the @Boost_Libraries X (formerly Twitter) account, all submitted by C++ Alliance team members. Three of them contained artwork from Bob Ostrom commissioned by us. Messages containing images get three times more engagement than text-only messages. We believe that the X platform has unique strategic value for informing newer generations about the Boost value proposition. A total of $406,000 was spent on Boost-related contributions, broken down thusly (and rounded to the nearest thousand): Staff Engineers Compensation $317,000 Website Software Development $64,000 Server Hosting $25,000 During Q1 2024 we employed a total of 12 individuals to contribute to Boost. Here is a high-level summary of accomplishments: Sam Darwin (Chief Technical Officer) * Boost website maintenance and administration * Boost per-pull-request documentation previews * Boost Release Process development, maintenance, and administration * Boost Mailman services maintenance and upgrade * Boost GitHub Actions self-hosted runner project development * Boost Drone service administration and maintenance * New Boost website deployment, administration, and development Dmitry Arkhipov (Staff Engineer) * Boost.JSON maintenance Alan de Freitas (Staff Engineer) https://cppalliance.org/alan/2024/05/07/AlanQ1Update.html * Boost.URL maintenance * Mr. Docs project management (https://mrdocs.com) * GitHub actions support scripts for Boost CI (https://alandefreitas.github.io/cpp-actions/cpp-actions/index.html) Christian Mazakas (Staff Engineer) * Boost.Unordered evolution project * Boost.Buffers development (new library) * Boost.Http.Proto, Boost.Http.Io development (new libraries) Krystian Stasiowski (Staff Engineer) * Boost.StaticString maintenance * Mr. Docs Lead engineer (https://mrdocs.com/) * Clang/LLVM contributions Peter Turcan (Senior Technical Writer) * Boost User Guide development (new documentation) * Boost Contributor Guide (new documentation) * Boost Formal Reviews (new documentation) Matt Borland (Staff Engineer) * Boost.Decimal (proposed library) * Multi (https://github.com/correaa/Boost-Multi) review manager * Boost.Math maintenance Ruben Perez * Boost.PFR integration and maintenance work * Boost.MySQL maintenance (new, accepted library) * Boost.Charconv * User Guide, Contributor Guide contribution (new documentation) Mohammad Nejati (Staff Engineer) * Boost.Http.Proto and Boost.Buffers (new libraries) * Boost-Gecko (full-text site search) * Boost.Beast maintenance Fernando Pelliccioni (Staff Engineer) * Mr. Docs development (https://mrdocs.com/) Spencer Strickland (Senior Web Developer) * New website front-end and scripting Joaquin M Lopez Munoz (Staff Engineer) * Boost.Unordered evolution project lead * Boost.Bimap * Boost promotion and new website

1 0

Fwd: shared_mutex lock() issue
by Max 15 May '24

15 May '24

Hi, It looks like threads-devel is abandoned I posted here. I have tried boost::shared_mutex and found an issue. It looks like it doesn't work as expected. The problem is following code: void lock() { #if defined BOOST_THREAD_PROVIDES_INTERRUPTIONS boost::this_thread::disable_interruption do_not_disturb; #endif boost::unique_lock<boost::mutex> lk(state_change); state.exclusive_waiting_blocked=true; exclusive_cond.wait(lk, boost::bind(&state_data::can_lock, boost::ref(state))); state.exclusive=true; } On lines: state.exclusive_waiting_blocked=true; exclusive_cond.wait(lk, boost::bind(&state_data::can_lock, boost::ref(state))); Here the state is changed and new lock_shared() waits because can_lock_shared returns false in this case. It works as I think it should be. The when "old" readers unlocks mutex the last one unlock_shared() executes void unlock_shared() { ... if (state.no_shared()) { if (state.upgrade) { ... } else { state.exclusive_waiting_blocked=false; //lk.unlock(); } release_waiters(); } where resets state.exclusive_waiting_blocked value. Then notify 2 condition variables(in release_waiters): 1 for readers and 1 for writers. If the writer doesn't win this race and one of the waited readers will be the first one, the writer runs state_data::can_lock and it of course returns false. Then the writer goes to sleep again. But exclusive_waiting_blocked is still false. So in the high pressure of readers, this writer never gets a chance to get control in this case anymore until all readers are gone. This bug was introduced in 1.67 version, before the changes the code was: while (state.shared_count || state.exclusive) { state.exclusive_waiting_blocked=true; exclusive_cond.wait(lk); } but it not the same as (because exclusive_waiting_blocked reassigned): state.exclusive_waiting_blocked=true; exclusive_cond.wait(lk, boost::bind(&state_data::can_lock, boost::ref(state))) Best Regards, Maxim

1 0

Re: [boost] Problem with building 1.85.0
by Ted Lyngmo 15 May '24

15 May '24

Andrey Semashev wrote: > > If you're building Boost from git, you should run `./b2 headers` before building Boost. > > The output you posted is missing the actual compilation errors for these files. Check the earlier compiler messages for these files. Or run `./b2 -j8 --with-filesystem` to build specifically Boost.Filesystem and see the output. Ok, I added `./b2 headers` before `./b2 -j8 install` which didn't change anything that I could see. `./b2 -j8 --with-filesystem` then gave me this: ...patience... ...found 3209 targets... ...updating 46 targets... boost-install.generate-cmake-config- bin.v2/libs/headers/build/stage/boost_headers-config.cmake boost-install.generate-cmake-config- bin.v2/libs/filesystem/build/stage/boost_filesystem-config.cmake boost-install.generate-cmake-config-version- bin.v2/libs/headers/build/stage/boost_headers-config-version.cmake common.copy /home/ted/git/boost/stage/lib/libboost_atomic.so.1.85.0 ln-UNIX /home/ted/git/boost/stage/lib/libboost_atomic.so boost-install.generate-cmake-config- bin.v2/libs/atomic/build/stage/boost_atomic-config.cmake boost-install.generate-cmake-config-version- bin.v2/libs/atomic/build/stage/boost_atomic-config-version.cmake common.copy /home/ted/git/boost/stage/lib/libboost_atomic.a common.copy /home/ted/git/boost/stage/lib/cmake/BoostDetectToolset-1.85.0.cmake common.copy /home/ted/git/boost/stage/lib/cmake/boost_filesystem-1.85.0/boost_filesystem-config.cmake common.copy /home/ted/git/boost/stage/lib/cmake/Boost-1.85.0/BoostConfig.cmake common.copy /home/ted/git/boost/stage/lib/cmake/Boost-1.85.0/BoostConfigVersion.cmake common.copy /home/ted/git/boost/stage/lib/cmake/boost_headers-1.85.0/boost_headers-config.cmake common.copy /home/ted/git/boost/stage/lib/cmake/boost_headers-1.85.0/boost_headers-config-version.cmake common.copy /home/ted/git/boost/stage/lib/cmake/boost_atomic-1.85.0/boost_atomic-config-version.cmake common.copy /home/ted/git/boost/stage/lib/cmake/boost_atomic-1.85.0/libboost_atomic-variant-shared.cmake boost-install.generate-cmake-config-version- bin.v2/libs/filesystem/build/stage/boost_filesystem-config-version.cmake common.copy /home/ted/git/boost/stage/lib/cmake/boost_atomic-1.85.0/boost_atomic-config.cmake common.copy /home/ted/git/boost/stage/lib/cmake/boost_atomic-1.85.0/libboost_atomic-variant-static.cmake common.copy /home/ted/git/boost/stage/lib/cmake/boost_filesystem-1.85.0/boost_filesystem-config-version.cmake gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/unique_path.o libs/filesystem/src/unique_path.cpp:57:10: fatal error: boost/scope/unique_fd.hpp: No such file or directory 57 | #include <boost/scope/unique_fd.hpp> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. "g++" -fvisibility-inlines-hidden -fPIC -m64 -pthread -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_DYN_LINK=1 -DBOOST_COBALT_USE_STD_PMR=1 -DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_FILESYSTEM_HAS_DIRENT_D_TYPE -DBOOST_FILESYSTEM_HAS_FALLOCATE -DBOOST_FILESYSTEM_HAS_FDOPENDIR_NOFOLLOW -DBOOST_FILESYSTEM_HAS_INIT_PRIORITY -DBOOST_FILESYSTEM_HAS_POSIX_AT_APIS -DBOOST_FILESYSTEM_HAS_STATX -DBOOST_FILESYSTEM_HAS_STAT_ST_BLKSIZE -DBOOST_FILESYSTEM_HAS_STAT_ST_MTIM -DBOOST_FILESYSTEM_NO_CXX20_ATOMIC_REF -DBOOST_FILESYSTEM_SOURCE -DNDEBUG -I"." -I"libs/filesystem/src" -c -o "bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/unique_path.o" "libs/filesystem/src/unique_path.cpp" ...failed gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/unique_path.o... gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/unique_path.o libs/filesystem/src/unique_path.cpp:57:10: fatal error: boost/scope/unique_fd.hpp: No such file or directory 57 | #include <boost/scope/unique_fd.hpp> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. "g++" -fvisibility-inlines-hidden -m64 -pthread -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_STATIC_LINK=1 -DBOOST_COBALT_USE_STD_PMR=1 -DBOOST_FILESYSTEM_HAS_DIRENT_D_TYPE -DBOOST_FILESYSTEM_HAS_FALLOCATE -DBOOST_FILESYSTEM_HAS_FDOPENDIR_NOFOLLOW -DBOOST_FILESYSTEM_HAS_INIT_PRIORITY -DBOOST_FILESYSTEM_HAS_POSIX_AT_APIS -DBOOST_FILESYSTEM_HAS_STATX -DBOOST_FILESYSTEM_HAS_STAT_ST_BLKSIZE -DBOOST_FILESYSTEM_HAS_STAT_ST_MTIM -DBOOST_FILESYSTEM_NO_CXX20_ATOMIC_REF -DBOOST_FILESYSTEM_SOURCE -DBOOST_FILESYSTEM_STATIC_LINK=1 -DNDEBUG -I"." -I"libs/filesystem/src" -c -o "bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/unique_path.o" "libs/filesystem/src/unique_path.cpp" ...failed gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/unique_path.o... gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/directory.o libs/filesystem/src/directory.cpp:42:10: fatal error: boost/scope/unique_fd.hpp: No such file or directory 42 | #include <boost/scope/unique_fd.hpp> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. "g++" -fvisibility-inlines-hidden -fPIC -m64 -pthread -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_DYN_LINK=1 -DBOOST_COBALT_USE_STD_PMR=1 -DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_FILESYSTEM_HAS_DIRENT_D_TYPE -DBOOST_FILESYSTEM_HAS_FALLOCATE -DBOOST_FILESYSTEM_HAS_FDOPENDIR_NOFOLLOW -DBOOST_FILESYSTEM_HAS_INIT_PRIORITY -DBOOST_FILESYSTEM_HAS_POSIX_AT_APIS -DBOOST_FILESYSTEM_HAS_STATX -DBOOST_FILESYSTEM_HAS_STAT_ST_BLKSIZE -DBOOST_FILESYSTEM_HAS_STAT_ST_MTIM -DBOOST_FILESYSTEM_NO_CXX20_ATOMIC_REF -DBOOST_FILESYSTEM_SOURCE -DNDEBUG -I"." -I"libs/filesystem/src" -c -o "bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/directory.o" "libs/filesystem/src/directory.cpp" ...failed gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/directory.o... gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/directory.o libs/filesystem/src/directory.cpp:42:10: fatal error: boost/scope/unique_fd.hpp: No such file or directory 42 | #include <boost/scope/unique_fd.hpp> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. "g++" -fvisibility-inlines-hidden -m64 -pthread -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_STATIC_LINK=1 -DBOOST_COBALT_USE_STD_PMR=1 -DBOOST_FILESYSTEM_HAS_DIRENT_D_TYPE -DBOOST_FILESYSTEM_HAS_FALLOCATE -DBOOST_FILESYSTEM_HAS_FDOPENDIR_NOFOLLOW -DBOOST_FILESYSTEM_HAS_INIT_PRIORITY -DBOOST_FILESYSTEM_HAS_POSIX_AT_APIS -DBOOST_FILESYSTEM_HAS_STATX -DBOOST_FILESYSTEM_HAS_STAT_ST_BLKSIZE -DBOOST_FILESYSTEM_HAS_STAT_ST_MTIM -DBOOST_FILESYSTEM_NO_CXX20_ATOMIC_REF -DBOOST_FILESYSTEM_SOURCE -DBOOST_FILESYSTEM_STATIC_LINK=1 -DNDEBUG -I"." -I"libs/filesystem/src" -c -o "bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/directory.o" "libs/filesystem/src/directory.cpp" ...failed gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/directory.o... gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/operations.o libs/filesystem/src/operations.cpp:120:10: fatal error: boost/scope/unique_fd.hpp: No such file or directory 120 | #include <boost/scope/unique_fd.hpp> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. "g++" -fvisibility-inlines-hidden -fPIC -m64 -pthread -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_DYN_LINK=1 -DBOOST_COBALT_USE_STD_PMR=1 -DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_FILESYSTEM_HAS_DIRENT_D_TYPE -DBOOST_FILESYSTEM_HAS_FALLOCATE -DBOOST_FILESYSTEM_HAS_FDOPENDIR_NOFOLLOW -DBOOST_FILESYSTEM_HAS_INIT_PRIORITY -DBOOST_FILESYSTEM_HAS_POSIX_AT_APIS -DBOOST_FILESYSTEM_HAS_STATX -DBOOST_FILESYSTEM_HAS_STAT_ST_BLKSIZE -DBOOST_FILESYSTEM_HAS_STAT_ST_MTIM -DBOOST_FILESYSTEM_NO_CXX20_ATOMIC_REF -DBOOST_FILESYSTEM_SOURCE -DNDEBUG -I"." -I"libs/filesystem/src" -c -o "bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/operations.o" "libs/filesystem/src/operations.cpp" ...failed gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/operations.o... ...skipped <pbin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden>libboost_filesystem.so.1.85.0 for lack of <pbin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden>directory.o... ...skipped <p/home/ted/git/boost/stage/lib>libboost_filesystem.so.1.85.0 for lack of <pbin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden>libboost_filesystem.so.1.85.0... ...skipped <p/home/ted/git/boost/stage/lib>libboost_filesystem.so for lack of <p/home/ted/git/boost/stage/lib>libboost_filesystem.so.1.85.0... ...skipped <pbin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden>libboost_filesystem-variant-shared.cmake for lack of <pbin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden>libboost_filesystem.so.1.85.0... ...skipped <p/home/ted/git/boost/stage/lib/cmake/boost_filesystem-1.85.0>libboost_filesystem-variant-shared.cmake for lack of <pbin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden>libboost_filesystem-variant-shared.cmake... gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/operations.o libs/filesystem/src/operations.cpp:120:10: fatal error: boost/scope/unique_fd.hpp: No such file or directory 120 | #include <boost/scope/unique_fd.hpp> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. "g++" -fvisibility-inlines-hidden -m64 -pthread -O3 -finline-functions -Wno-inline -Wall -fvisibility=hidden -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_STATIC_LINK=1 -DBOOST_COBALT_USE_STD_PMR=1 -DBOOST_FILESYSTEM_HAS_DIRENT_D_TYPE -DBOOST_FILESYSTEM_HAS_FALLOCATE -DBOOST_FILESYSTEM_HAS_FDOPENDIR_NOFOLLOW -DBOOST_FILESYSTEM_HAS_INIT_PRIORITY -DBOOST_FILESYSTEM_HAS_POSIX_AT_APIS -DBOOST_FILESYSTEM_HAS_STATX -DBOOST_FILESYSTEM_HAS_STAT_ST_BLKSIZE -DBOOST_FILESYSTEM_HAS_STAT_ST_MTIM -DBOOST_FILESYSTEM_NO_CXX20_ATOMIC_REF -DBOOST_FILESYSTEM_SOURCE -DBOOST_FILESYSTEM_STATIC_LINK=1 -DNDEBUG -I"." -I"libs/filesystem/src" -c -o "bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/operations.o" "libs/filesystem/src/operations.cpp" ...failed gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/operations.o... ...skipped <pbin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden>libboost_filesystem.a(clean) for lack of <pbin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden>directory.o... ...skipped <pbin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden>libboost_filesystem.a for lack of <pbin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden>directory.o... ...skipped <p/home/ted/git/boost/stage/lib>libboost_filesystem.a for lack of <pbin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden>libboost_filesystem.a... ...skipped <pbin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden>libboost_filesystem-variant-static.cmake for lack of <pbin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden>libboost_filesystem.a... ...skipped <p/home/ted/git/boost/stage/lib/cmake/boost_filesystem-1.85.0>libboost_filesystem-variant-static.cmake for lack of <pbin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden>libboost_filesystem-variant-static.cmake... ...updated 30 targets... ...skipped 10 targets... <p/home/ted/git/boost/stage/lib/cmake/boost_filesystem-1.85.0>libboost_filesystem-variant-shared.cmake <p/home/ted/git/boost/stage/lib/cmake/boost_filesystem-1.85.0>libboost_filesystem-variant-static.cmake <p/home/ted/git/boost/stage/lib>libboost_filesystem.a <p/home/ted/git/boost/stage/lib>libboost_filesystem.so <p/home/ted/git/boost/stage/lib>libboost_filesystem.so.1.85.0 <pbin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden>libboost_filesystem-variant-static.cmake <pbin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden>libboost_filesystem.a <pbin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden>libboost_filesystem.a(clean) <pbin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden>libboost_filesystem-variant-shared.cmake <pbin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden>libboost_filesystem.so.1.85.0 ...failed updating 6 targets... gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/directory.o gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/operations.o gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/unique_path.o gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/directory.o gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/operations.o gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/unique_path.o

4 4

Problem with building 1.85.0
by Ted Lyngmo 13 May '24

13 May '24

Hi! First, I'm not sure if this is the right place for this. https://svn.boost.org/trac/boost seems to be down so I'm not sure where to turn. When I try building 1.85 on Fedora 40 with g++ (GCC) 14.1.1 20240507 (Red Hat 14.1.1-1) I run into a problem. I'm preparing the build like this: git co master && \ git pull -r && \ git co boost-1.85.0 && \ git submodule update --recursive && \ ./bootstrap.sh --with-libraries=all --with-icu \ -with-python-version=3.12.3 --prefix=/home/ted/local && \ echo 'using mpi ;' >> project-config.jam Then building like this: ./b2 -j8 install It however ends like this: ... ...updated 18621 targets... ...skipped 30 targets... <p/home/ted/local/lib/cmake/boost_fiber-1.85.0>libboost_fiber-variant-shared.cmake <p/home/ted/local/lib/cmake/boost_filesystem-1.85.0>libboost_filesystem-variant-shared.cmake <p/home/ted/local/lib/cmake/boost_filesystem-1.85.0>libboost_filesystem-variant-static.cmake <p/home/ted/local/lib/cmake/boost_log-1.85.0>libboost_log-variant-shared.cmake <p/home/ted/local/lib/cmake/boost_log_setup-1.85.0>libboost_log_setup-variant-shared.cmake <p/home/ted/local/lib/cmake/boost_wave-1.85.0>libboost_wave-variant-shared.cmake <p/home/ted/local/lib>libboost_fiber.so <p/home/ted/local/lib>libboost_fiber.so.1.85.0 <p/home/ted/local/lib>libboost_filesystem.a <p/home/ted/local/lib>libboost_filesystem.so <p/home/ted/local/lib>libboost_filesystem.so.1.85.0 <p/home/ted/local/lib>libboost_log.so <p/home/ted/local/lib>libboost_log.so.1.85.0 <p/home/ted/local/lib>libboost_log_setup.so <p/home/ted/local/lib>libboost_log_setup.so.1.85.0 <p/home/ted/local/lib>libboost_wave.so <p/home/ted/local/lib>libboost_wave.so.1.85.0 <pbin.v2/libs/fiber/build/gcc-14/release/threading-multi/visibility-hidden>libboost_fiber-variant-shared.cmake <pbin.v2/libs/fiber/build/gcc-14/release/threading-multi/visibility-hidden>libboost_fiber.so.1.85.0 <pbin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden>libboost_filesystem-variant-static.cmake <pbin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden>libboost_filesystem.a <pbin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden>libboost_filesystem.a(clean) <pbin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden>libboost_filesystem-variant-shared.cmake <pbin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden>libboost_filesystem.so.1.85.0 <pbin.v2/libs/log/build/gcc-14/release/threading-multi/visibility-hidden>libboost_log-variant-shared.cmake <pbin.v2/libs/log/build/gcc-14/release/threading-multi/visibility-hidden>libboost_log.so.1.85.0 <pbin.v2/libs/log/build/gcc-14/release/threading-multi/visibility-hidden>libboost_log_setup-variant-shared.cmake <pbin.v2/libs/log/build/gcc-14/release/threading-multi/visibility-hidden>libboost_log_setup.so.1.85.0 <pbin.v2/libs/wave/build/gcc-14/release/threading-multi/visibility-hidden>libboost_wave-variant-shared.cmake <pbin.v2/libs/wave/build/gcc-14/release/threading-multi/visibility-hidden>libboost_wave.so.1.85.0 ...failed updating 6 targets... gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/directory.o gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/operations.o gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/link-static/threading-multi/visibility-hidden/unique_path.o gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/directory.o gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/operations.o gcc.compile.c++ bin.v2/libs/filesystem/build/gcc-14/release/threading-multi/visibility-hidden/unique_path.o Building boost-1.84.0, or earlier, the same way doesn't show any signs of problems. Is my bootstrapping done in the wrong way? I've used the same way for a long time, but I might just have been lucky that it has worked :) Br, Ted

2 1

What is this "Beman Project Development"?
by René Ferdinand Rivera Morell 12 May '24

12 May '24

I got the email below from discourse.boost.org (I had subscribed long ago). So getting something was not unexpected. What I'm wondering about are this: Q: What is this new "Beman Project Development" thing about? A: It's something from C++Now initiated by The Boost Foundation (DBA) Q: Did they get permission from the Beman family to use Beman Dawes' name this way? A: ?? ---------- Forwarded message --------- From: Jeff Garland via Beman Project <notifications(a)boost.discoursemail.com> Date: Fri, May 3, 2024 at 10:19 AM Subject: [Beman Project] [Beman Project Development] Becoming a member of the beman-project github Jeff-Garland <https://discourse.boost.org/u/jeff-garland> May 3 Please send your github id to @Jeff-Garland <https://discourse.boost.org/u/jeff-garland> @dsankel <https://discourse.boost.org/u/dsankel> or @bretbrownjr <https://discourse.boost.org/u/bretbrownjr> via DM. ------------------------------ Visit Topic <https://discourse.boost.org/t/becoming-a-member-of-the-beman-project-github…> or reply to this email to respond. To unsubscribe from these emails, click here <https://discourse.boost.org/email/unsubscribe/63382355ff9c551129d38f2a59078…> . -- -- René Ferdinand Rivera Morell -- Don't Assume Anything -- No Supone Nada -- Robot Dreams - http://robot-dreams.net

13 43

What is this "Beman Project Development" exactly
by Robert Ramey 10 May '24

10 May '24

I confess that I'm totally mystified by this. I've looked over the web page and it doesn't help me. Here is the "mission statement" from the Boost Foundation website: "The Boost Foundation’s broad C++ mission is: (a) development of high quality, expert reviewed, legally unencumbered, open-source libraries, (b) inspiring standard enhancements, and (c) advancing and disseminating software development best practices. It does this by fostering community engagement, nurturing leaders, providing necessary financial/legal support, and making directional decisions in the event of Boost community deadlock." "Equally important to our mission is the guidance provided by our shared values. These are transparency, inclusivity, consensus-building, federated authorship, and community-driven leadership." Here is the "mission statement" from the Beman Project: "The Beman Project’s mission is to support the efficient design and adoption of the highest quality C++ Standard libraries through implementation experience, user feedback, and technical expertise. Founded at C++Now in 2024 the project strives to aggregate libraries proposed for ISO standardization making a simple usage experience for the C++ Community to try out new libraries. For library authors we assist by helping to make best modern development practices easy. Including CI, coverage, and packaging." Seems to me that they are essentially the same with different wording (excluding the woke paragraph it the Boost Foundation version. A couple miscellaneous questions: a) Why is the Boost Foundation website not part of the Boost.org website? b) So what's the point of all this? Who has promoted/championed it? What is their motivation. Extremely odd to me. add your own questions here. Personally I'd like to see the following: a) consolidation of all this under one umbrella b) More transparency in selection of board of directors. More direct influence on the part of library creators and users. I don't have any idea how to achieve this without creating caos though. c) Distancing Boost from the C++ standard. Boosts original mission was accomplished when the standards committee incorporated a large part of boost directly into the standard. Since then boost's policy of working with the standard library is very confusing. Are we an alternative? or are trying to create new (better?) standard library components. Or are we trying to create canonical implementations of the standard library components? The standard committee is flailing around itself. Three way branch? executors? Does something as elaborate as ranges belong in a standard library? What about testing the standard library? How do we do this? or Not. Do I incorporate the standard library in my heart pacemaker app? Without being able to test any of it? Oh let's not forget "modules" I've been reading up on it and it seems at most a half-baked idea. So boost should only focus on the standard to the extent that it needs to in order to make it's own libraries work. Sorry, I'm just not understanding any of this. Robert Ramey

7 11

Boost Foundation annual meeting in Aspen
by David Sankel 07 May '24

07 May '24

Hi all! We held our annual Boost Foundation meeting at C++Now last week. At this annual meeting we elect officers for an annual term and directors for staggering two-year terms. Glen Fernandes and Peter Dimov had terms expiring this year and were re-elected for another two-year term. We additionally added Matthew Guidry, who has been regularly active in foundation work, to the director roster. Congrats Matthew! Class A (Terms Expiring 2025) - Bob Steagall [BS] - David Sankel [DS] - Michael Caisse [MJC] - Zach Laine [ZL] - Inbal Levi [IL] - Jeff Garland [JG] - Kristen Shaker [KS] Class B (Terms Expiring 2026) - Glen Fernandes [GF] - Peter Dimov [PD] - Matthew Guidry [MG] - (4 vacant slots) We additionally made officer selections. I will continue for another year as Executive Director, but have stepped down as Chair of the Board of Directors. Kristen Shaker has volunteered to take this on (congrats Kristen!). Zach Laine has agreed to take on the Safety and Inclusion Chair role in her place. Here is the list of officers: - Board of Directors, Chair: Kristen Shaker - Board of Directors, Vice Chair: Glen Fernandes - Conference Chair: Bob Steagall - Director of Summer of Code: Inbal Levi - Executive Director: David Sankel - Secretary: Michael Caisse - Treasurer: Zach Laine - Standardization Chair: Jeff Garland - Safety and Inclusion Chair: Zach Laine We also decided to take down discourse.boost.org due to a general lack of interest by those active in the Boost project. The instance will be utilized by the Beman project <https://www.bemanproject.org/>, an independent initiative focused on providing implementations of libraries proposed for the C++ standard. That's all for now! -- David

1 0

Looking for review manager for async_mqtt
by Takatoshi Kondo 06 May '24

06 May '24

Hi, I've proposed a MQTT communication library based on Boost.Asio. https://github.com/redboltz/async_mqtt Fortunately, I got two endorsements, so far. Thank you Klemens and JoaquÃn. https://lists.boost.org/Archives/boost/2024/04/256650.php https://lists.boost.org/Archives/boost/2024/04/index.php However, I couldn't find a review manager, so far. https://www.boost.org/development/submissions.html I think that I am at step4 and step5 in the Boost Library Submission Process. I'm looking for review managers for async_mqtt now. I think that Boost.Beast, Boost.MySQL, and Boost.Redis are developed on Boost.Asio. I referred to those libraries for async_mqtt development. async_mqtt is using Boost.Beast for WebSocket communication. If those libraries developers would be interested in review managers, I would appreciate it. Of course, any other people are welcome. Best Regards, Takatoshi Kondo

1 0

GSOC '24 at Boost
by David Bellot 05 May '24

05 May '24

Hi all, Another year, another GSOC's coming! As you all know now, Inbal is in charge of managing our GSOC program at Boost. Over the past years, I had the pleasure to work with many of you and we had the chance to have many great students and mentors. This year, however, it seems we don't have enough mentors yet. I know it's just the beginning of the year, but I would like to encourage you to join this program as a mentor, and help students to participate in Boost and become great C++ developers. It's a very rewarding journey I took myself years ago and you will learn so much, both on the technical and human side. If you want to become a mentor, just add your name to this shared spreadsheet: https://docs.google.com/spreadsheets/d/1_eUWRsXnhi_JwKZbHZsGQf3WNUESsAPE4lV… Cheers, David

4 3

Compression libraries such as zlib and zstd ought to be first class boost libraries
by Nigel Stewart 05 May '24

05 May '24

Hello all, I've been having a fairly hard time enabling zlib and zstd for boost 1.85.0 so we can make use of the compression support in iostreams module. We do have some specifics - static linking, non-standard file names and not system-installed. Windows and Linux. For various reasons it looks like we're going to copy certain files into our modules, rather than puzzle over making this work. It's not ideal, but workable. But along the way it's become clear that this functionality is not first-class boost citizen. Such as the broken links in the documentation, and various historical questions via google reporting similar issues. There are also other copies of zlib in the beast tree, because it's obviously needed for HTTP stuff too. zstd too? So I did think that I should at least mention that zlib, zstd, bzip2 and xv-utils all ought to be promoted to first-class boost libraries even though the majority of the maintenance is coming from upstream. They ought to be part of the "big tarball" and enabled and built by default regardless of what happens to be installed on the system. The cmake stuff ought to "just work" the way it does for other boost modules. I'm not quite volunteering myself, but it seems like a start to pose the question. The developer experience could be significantly improved for this particular corner of things. - Nigel Stewart

7 24