- Boost - lists.preview.boost.org

[ci][security] Codecov security breach
by Andrey Semashev 27 Apr '21

27 Apr '21

Hi, I found this in my news feed today: The codecov-bash script that is used to upload codecov reports from CI to codecov.io was maliciously modified to collect sensitive information and send to a third party server. Things like private keys, credentials, auth tokens used in the CI might be compromised. https://discuss.hashicorp.com/t/hcsec-2021-12-codecov-security-event-and-ha… https://about.codecov.io/security-update/ I'm not using codecov, and I have vague understanding how it works, but I've seen it used in Boost libraries' CI. I don't know if they are affected, this is an FYI to the maintainers.

1 0

Fwd: [BOOST][GIL][Histogram]Ordered Maps in place of unordered maps
by sayan chaudhuri 26 Apr '21

26 Apr '21

---------- Forwarded message --------- From: sayan chaudhuri <sayanchaudhuri758(a)gmail.com> Date: Sat, Apr 24, 2021 at 3:08 PM Subject: [BOOST][GIL][Histogram]Ordered Maps in place of unordered maps To: <boost-gil(a)lists.boost.org> Dear Matseuz, The histogram implemented in boost gil uses an unordered map.Wont it have been better with an ordered map? Because the worst case time complexity is better in case of ordered maps. Regards, Yours sincerely, Sayan Chaudhuri

3 2

[Boost][Multiarray]Move for_each.hpp from examples to boost/multi_array
by sayan chaudhuri 25 Apr '21

25 Apr '21

Hello Everyone, I wish to draw attention to the fact that the for_each header file for multiarrays in boost is not present in the include/boost section of the boost multiarray repository. Also, the header file does not have a namespace defined inside it and so the compiler becomes confused as to which for_each function to follow, the one from stl or this one. The for_each is a great utility for boost multiarrays reducing code size and increasing readability. I would like to what others would like to say about these changes. Making these changes allows contributors to other boost libraries to use that functionality in a proper manner. Thanking everyone, Yours sincerely, Sayan Chaudhuri

1 0

[iostreams] [build] Why do iostream tests link against static libraries ?
by Brian Kuhl 22 Apr '21

22 Apr '21

Cross-posting since boost-build is quiet these days. I’m trying to get iostreams working with shared libraries on VxWorks The tests will compile with clang 11 if I comment out the forced dependency on static libraries But I’d like to understand the reason for forcing a link of static libraries with a dynamic executable? https://github.com/boostorg/iostreams/blob/4d2e763ba8b88f3350fbea29b54507a3… rule test-iostreams ( sources * : requirements * : target-name ? ) { return [ run $(sources) /boost/test//boost_unit_test_framework # /<link>static /boost/filesystem//boost_filesystem # /<link>static : # command : # input files : # build requirements <toolset>msvc:<define>_CRT_SECURE_NO_DEPRECATE <toolset>msvc:<define>_SCL_SECURE_NO_DEPRECATE <toolset>cw-9.3,<os>darwin:<runtime-link>static <define>BOOST_IOSTREAMS_NO_LIB <link>shared:<define>BOOST_IOSTREAMS_DYN_LINK=1 $(requirements) : $(target-name) ] ; } If I don’t comment, I get a link error. VxWorks only supports -fpic vs -fPIC clang-vxworks.compile.c++ ../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/unit_test_parameters.o "wr-c++" -x c++ -Wno-c99-extensions -Wno-variadic-macros -O3 -finline-functions -Wno-inline -Wall -pedantic -g -Wno-inline -DBOOST_ALL_NO_LIB=1 -DBOOST_BEAST_ALLOW_DEPRECATED -DBOOST_BEAST_SEPARATE_COMPILATION -I".." -c -o "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/unit_test_parameters.o" "../libs/test/src/unit_test_parameters.cpp" clang-vxworks.archive ../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/libboost_unit_test_framework.a "wr-ar" rcu "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/libboost_unit_test_framework.a" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/compiler_log_formatter.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/debug.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/decorator.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/execution_monitor.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/framework.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/plain_report_formatter.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/progress_monitor.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/results_collector.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/results_reporter.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/test_framework_init_observer.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/test_tools.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/test_tree.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/unit_test_log.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/unit_test_main.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/unit_test_monitor.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/unit_test_parameters.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/junit_log_formatter.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/xml_log_formatter.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/xml_report_formatter.o" clang-vxworks.link ../bin.v2/libs/iostreams/test/array_test.test/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/array_test.vxe "wr-c++" -o "../bin.v2/libs/iostreams/test/array_test.test/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/array_test.vxe" "../bin.v2/libs/iostreams/test/array_test.test/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/array_test.o" "../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/libboost_unit_test_framework.a" "../bin.v2/libs/filesystem/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/libboost_filesystem.a" -shared --start-group --end-group -fpic /opt/git/vx7/compilers/llvm-11.0.0.1/LINUX64/bin/ldarm: ../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/libboost_unit_test_framework.a(test_tools.o): relocation R_ARM_MOVW_ABS_NC against `a local symbol' can not be used when making a shared object; recompile with -fPIC /opt/git/vx7/compilers/llvm-11.0.0.1/LINUX64/bin/ldarm: ../bin.v2/libs/test/build/clang-vxworks-11.0.0.1/debug/cross-compile-vxworks/link-static/libboost_unit_test_framework.a(test_tree.o): relocation R_ARM_MOVW_ABS_NC against `a local symbol' can not be used when making a shared object; recompile with -fPIC

1 0

Reminder: BinTray is shutting down 1-May
by Marshall Clow 21 Apr '21

21 Apr '21

Bintray is “sunsetting” on the 1st of May. At that time, you will be unable to download boost releases from there. Before that time, their service will be occasionally interrupted. We will be updating the web site before then, but the new location is: https://boostorg.jfrog.io/artifactory/main/release/ <https://boostorg.jfrog.io/artifactory/main/release/> So instead of downloading from: https://dl.bintray.com/boostorg/release/1.76.0/source/boost_1_76_0.tar.gz You should download from: https://boostorg.jfrog.io/artifactory/main/release/1.76.0/source/boost_1_76… This applies to all releases from 1.63.0 onward — Marshall

1 0

Master branch now open for merging
by Marshall Clow 19 Apr '21

19 Apr '21

No restrictions; the release calendar is up to date. https://boost.org/development <https://boost.org/development> Next milestone: 23-Jun Boost 1.77.0 closed for new libraries and breaking changes — Marshall

1 0

Re: [boost] [Boost-users] [release] Boost 1.76.0
by Glen Fernandes 17 Apr '21

17 Apr '21

On Fri, Apr 16, 2021 at 7:28 PM Edward Diener wrote: > I noticed on the main web page where it has under > "News" the "Version 1.76.0" that "Updated Libraries:" list nothing even > though there are plenty of updates for libraries at > https://www.boost.org/users/history/version_1_76_0.html. The fix for this has been committed; it should take effect automatically in about an hour or so. Glen

1 0

[release] Boost 1.76.0
by Marshall Clow 16 Apr '21

16 Apr '21

Release 1.76.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 no 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.76.0> You can also download directly from: <https://boostorg.jfrog.io/artifactory/main/release/1.76.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, Michael Caisse, Glen Fernandes

1 0

[release] Boost 1.76.0 Release Candidate 12
by Marshall Clow 14 Apr '21

14 Apr '21

The second release candidates for the 1.76.0 release are now available at: <https://boostorg.jfrog.io/artifactory/main/release/1.76.0/source/ <https://dl.bintray.com/boostorg/release/1.76.0/source/>> The SHA256 checksums are as follows: 7bd7ddceec1a1dfdcbdb3e609b60d01739c38390a5f956385a12f3122049f0ca boost_1_76_0_rc2.tar.gz 0fd43bb53580ca54afc7221683dfe8c6e3855b351cd6dce53b1a24a7d7fbeedd boost_1_76_0_rc2.zip 88782714f8701b6965f3fce087a66a1262601dd5ccd5b2e5305021beb53042a1 boost_1_76_0_rc2.7z f0397ba6e982c4450f27bf32a2a83292aba035b827a5623a14636ea583318c41 boost_1_76_0_rc2.tar.bz2 Changes from RC1: * A missing include was added to a Boost.Regex header. This fixes compilation on gcc 11. 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 3

[gsoc21][boost.multiprecision] Realisation of Quad Double
by Abhishek Kujur 13 Apr '21

13 Apr '21

Greetings, My name is Abhishek Kujur, I am CSE student at Kalinga Institute of Technology. I have used c++ for like 6 years and I have understanding of C++ Stl, object orientation and template metaprogramming. I would love to be selected at GSOC 2021 by contributing to C++'s well known library, Boost Library. I would be interested in feedback and suggestions. The link to my proposal is: https://docs.google.com/document/d/1NnrBhA4Hu0JYwjSSQJgCTlgYZaYl2FrVinp6h-Z…

3 2