- Boost - lists.preview.boost.org

Boost 1.78.0 build issue
by Daggumati, Rajesh 21 Mar '22

21 Mar '22

Hi Team, I have built 1.76.0 sucessfully in my visual studio 2019 but when I try to build boost 1.78.0, I am facing some linker issue like below. Please help me to fix it. Severity Code Description Project File Line Suppression State Error LNK1104 cannot open file 'libboost_filesystem-vc142-mt-gd-x64-1_78.lib' checksum-writer-xml C:\Projects\Abba\src-cpp\src\apps\checksum-writer-xml\LINK 1 Error LNK1104 cannot open file 'libboost_filesystem-vc142-mt-gd-x64-1_78.lib' IPLUtilityTest C:\Projects\Abba\src-cpp\src\modules\IPLUtilityTest\LINK 1 Error LNK1104 cannot open file 'libboost_thread-vc142-mt-gd-x64-1_78.lib' FoundationQtTest C:\Projects\Abba\src-cpp\src\modules\FoundationQtTest\LINK 1 Error LNK1104 cannot open file 'libboost_thread-vc142-mt-gd-x64-1_78.lib' FoundationTest C:\Projects\Abba\src-cpp\src\modules\FoundationTest\LINK 1 Error LNK1104 cannot open file 'libboost_program_options-vc142-mt-gd-x64-1_78.lib' console-test-harness C:\Projects\Abba\src-cpp\src\apps\console-test-harness\LINK 1 Error LNK1104 cannot open file 'libboost_filesystem-vc142-mt-gd-x64-1_78.lib' InstrumentTest C:\Projects\Abba\src-cpp\src\modules\InstrumentTest\LINK 1 Error LNK1104 cannot open file 'libboost_thread-vc142-mt-gd-x64-1_78.lib' InstrumentQtTest C:\Projects\Abba\src-cpp\src\modules\InstrumentQtTest\LINK 1 Error LNK1104 cannot open file 'libboost_thread-vc142-mt-gd-x64-1_78.lib' widget-test-harness C:\Projects\Abba\src-cpp\src\apps\widget-test-harness\LINK 1 Error LNK1104 cannot open file 'libboost_thread-vc142-mt-gd-x64-1_78.lib' cytiva-aktaflux C:\Projects\Abba\src-cpp\src\apps\cytiva-aktaflux\LINK 1 Regards, Rajesh D Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.

1 0

[release] Boost 1.79.0 beta 1 released
by Marshall Clow 20 Mar '22

20 Mar '22

Boost release 1.79.0 beta 1 is now available at: <https://boostorg.jfrog.io/artifactory/main/beta/1.79.0.beta1/source/> The SHA256 checksums are as follows: 8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1.tar.bz2 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1.tar.gz 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_0_b1.7z 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1.zip For details of what's in the release, see <https://www.boost.org/users/history/version_1_79_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

4 6

numeric_cast should work with enum's
by Frederick Virchanza Gotham 16 Mar '22

16 Mar '22

(Sometimes Gmail takes out white space so I'm hoping this post is indented properly.) I think that "numeric_cast" should be able to cast to and from enum types, so that it can be used as follows: #include <cstdint> #include <iostream> using std::cout; using std::endl; enum class Toad : std::uint8_t { Purple, Orange = 0x7f }; enum class Frog { Blue, Yellow, Pink = 0xFFFFu }; int main(void) { try { numeric_cast<Toad>( Frog::Pink ); } catch(std::exception const &e) { cout << e.what() << endl; } std::uint32_t my_32_bit_var = 0xffffffffU; try { numeric_cast<std::uint16_t>(my_32_bit_var); } catch(std::exception const &e) { cout << e.what() << endl; } try { numeric_cast<std::uint8_t>( Frog::Pink ); } catch(std::exception const &e) { cout << e.what() << endl; } try { numeric_cast<Toad>(0x1FFu); } catch(std::exception const &e) { cout << e.what() << endl; } } In order to achieve this behaviour, I've created my own "numeric_cast" in the global namespace as follows: #include <type_traits> // is_enum, underlying_type #include <boost/numeric/conversion/cast.hpp> // numeric_cast template<bool T_is_an_enum, typename T> struct numeric_cast_helper { typedef T type; }; template<typename T> struct numeric_cast_helper<true, T> { typedef typename std::underlying_type<T>::type type; }; template<typename A, typename B> A numeric_cast(B const b) // This function takes its argument by value, and also returns by value -- which is fine for arithmetic types { return static_cast<A>( boost::numeric_cast<typename numeric_cast_helper<std::is_enum<A>::value, A>::type> ( static_cast<typename numeric_cast_helper<std::is_enum<B>::value, B>::type>(b) ) ); }

1 0

Fwd: Boost Digest, Vol 6656, Issue 1
by Sal Pamukcu 11 Mar '22

11 Mar '22

---------- Forwarded message --------- From: <boost-request(a)lists.boost.org> Date: Fri, Mar 11, 2022 at 3:00 PM Subject: Boost Digest, Vol 6656, Issue 1 To: <boost(a)lists.boost.org> Send Boost mailing list submissions to boost(a)lists.boost.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.boost.org/mailman/listinfo.cgi/boost or, via email, send a message with subject or body 'help' to boost-request(a)lists.boost.org You can reach the person managing the list at boost-owner(a)lists.boost.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Boost digest..." The boost archives may be found at: http://lists.boost.org/Archives/boost/ Today's Topics: 1. Re: [Graph] Attempt to resolve open issue (Anne van de Graaf) 2. Master branch now closed for 1.79.0 beta release (Marshall Clow) 3. [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available (Marshall Clow) 4. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available (Marshall Clow) 5. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available (Andrey Semashev) 6. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available (Marshall Clow) 7. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available (Andrey Semashev) 8. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available (Tom Kent) 9. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available (Matt Borland) 10. Re: [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available (Andrey Semashev) ---------- Forwarded message ---------- From: Anne van de Graaf <A.vandeGraaf(a)dianafea.com> To: Jeremy Murphy <jeremy.william.murphy(a)gmail.com> Cc: "boost(a)lists.boost.org" <boost(a)lists.boost.org>, John Maddock < jz.maddock(a)googlemail.com> Bcc: Date: Thu, 10 Mar 2022 13:17:37 +0000 Subject: Re: [boost] [Graph] Attempt to resolve open issue > This is fixed on the develop branch, btw, have you verified that it works as expected now? Apologies for my late reply. Yes, I have verified that the fix on the develop branch works as expected. Thank you very much for the work that you have done. Best regards, Anne On Fri, 10 Dec 2021 at 18:56, Anne van de Graaf <A.vandeGraaf(a)dianafea.com <mailto:A.vandeGraaf@dianafea.com>> wrote: > Hi Anne, > which issue or pull request # is it? Hi Jeremy, It is issue # 268: https://github.com/boostorg/graph/issues/268 Best regards, Anne > Jeremy On Sun, 5 Dec 2021 at 02:20, Anne van de Graaf via Boost < boost(a)lists.boost.org<mailto:boost@lists.boost.org>> wrote: > Hello all, > > I am trying to get an open issue in Boost.Graph resolved. Since I haven't received any response at the corresponding GitHub page nor from the Boost Users mailing list (where I posted the below message last Monday), I am reaching out to you. My aim is to get in touch with the maintainer(s) of Boost.Graph in order to discuss what is the preferred/most efficient way to fix the issue. Since this is my first post to this mailing list, please accept my apologies if you feel this is not the right way to get in touch with the maintainers. In that case, I would appreciate it very much if you could kindly explain what I should have done instead. Please find below a copy of my message that I sent last Monday to the Boost Users mailing list. Thank you very much for your attention and any replies. > Unfortunately, Graph has no current maintainer. I have done some > maintenance on that library in the past, and I know Jeremy Murphy will > be trying to do some this next week, so hopefully one of us can get that > one fixed! Thanks a lot for your reply, John. I didn't know that Boost.Graph doesn't have a current maintainer. It would be great if you or Jeremy could do some maintenance on it. Feel free to contact me if I can help you in any way to get things done. We could then discuss in what way I can contribute. Thanks. Kind regards, Anne > Best, John. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost ---------- Forwarded message ---------- From: Marshall Clow <mclow.lists(a)gmail.com> To: Boost Developers List <boost(a)lists.boost.org> Cc: Bcc: Date: Thu, 10 Mar 2022 06:31:06 -0800 Subject: [boost] Master branch now closed for 1.79.0 beta release Please do not make any commits to the master branch. — Marshall ---------- Forwarded message ---------- From: Marshall Clow <mclow.lists(a)gmail.com> To: Boost Developers List <boost(a)lists.boost.org> Cc: Bcc: Date: Thu, 10 Mar 2022 07:27:19 -0800 Subject: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available are now available at: <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source < https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>> The SHA256 checksums are as follows: 8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_0_b1_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 It fails on Window 11 using GCC-11.2 command line ; b2 cxxstd=20 toolset=gcc --build-type=complete stage here is the error message ; FailBoost1.79.0 Beta 1 Release Candidate 1 (github.com) <https://gist.github.com/salimp2009/854b3c74295b2487c4585be35f8bfbd0> Salim (a new bee in devel :) ---------- Forwarded message ---------- From: Marshall Clow <mclow.lists(a)gmail.com> To: Boost Developers List <boost(a)lists.boost.org> Cc: Bcc: Date: Thu, 10 Mar 2022 08:03:12 -0800 Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available On Mar 10, 2022, at 7:27 AM, Marshall Clow <mclow.lists(a)gmail.com> wrote: > > are now available at: > <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source < https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>> > > The SHA256 checksums are as follows: > > 8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 > 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz > 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip > 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_0_b1_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. I have successfully built the libraries: * On Mac OS 10.15, using Apple clang version 11.0.3, and and c++03/11/14/17/2a — Marshall ---------- Forwarded message ---------- From: Andrey Semashev <andrey.semashev(a)gmail.com> To: boost(a)lists.boost.org Cc: Bcc: Date: Thu, 10 Mar 2022 20:17:42 +0300 Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available On 3/10/22 18:27, Marshall Clow via Boost wrote: > are now available at: > <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source < https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>> > > The SHA256 checksums are as follows: > > 8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 > 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz > 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip > 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_0_b1_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. I'm trying to download the source package now, and the download speed is terrible, ~30-60 KB/s. Is this expected? ---------- Forwarded message ---------- From: Marshall Clow <mclow.lists(a)gmail.com> To: boost(a)lists.boost.org Cc: Bcc: Date: Thu, 10 Mar 2022 09:53:08 -0800 Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available On Mar 10, 2022, at 9:17 AM, Andrey Semashev via Boost < boost(a)lists.boost.org> wrote: > > On 3/10/22 18:27, Marshall Clow via Boost wrote: >> are now available at: >> <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source < https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>> >> >> The SHA256 checksums are as follows: >> >> 8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 >> 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz >> 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip >> 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_0_b1_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. > > I'm trying to download the source package now, and the download speed is > terrible, ~30-60 KB/s. Is this expected? That’s not what I’m seeing. I’m getting > 1 MB/sec — Marshall ---------- Forwarded message ---------- From: Andrey Semashev <andrey.semashev(a)gmail.com> To: boost(a)lists.boost.org Cc: Bcc: Date: Thu, 10 Mar 2022 21:25:53 +0300 Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available On 3/10/22 20:53, Marshall Clow via Boost wrote: > On Mar 10, 2022, at 9:17 AM, Andrey Semashev via Boost < boost(a)lists.boost.org> wrote: >> >> On 3/10/22 18:27, Marshall Clow via Boost wrote: >>> are now available at: >>> <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source < https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>> >>> >>> The SHA256 checksums are as follows: >>> >>> 8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 >>> 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz >>> 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip >>> 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_0_b1_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. >> >> I'm trying to download the source package now, and the download speed is >> terrible, ~30-60 KB/s. Is this expected? > > That’s not what I’m seeing. > I’m getting > 1 MB/sec Possibly, some regional restrictions on JFrog side? I'm not seeing bandwidth issues on other sites, including GitHub, which I assume is US based. BTW, building with gcc 11.2 in C++17 mode on Kubuntu 21.10 succeeds. There are quite a few warnings about auto_ptr being deprecated, and also some suspicious warnings about freeing non-heap-allocated objects in Boost.Wave: https://github.com/boostorg/wave/issues/159 ---------- Forwarded message ---------- From: Tom Kent <lists(a)teeks99.com> To: Boost Developers List <boost(a)lists.boost.org> Cc: Bcc: Date: Thu, 10 Mar 2022 15:33:30 -0600 Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available On Thu, Mar 10, 2022 at 9:27 AM Marshall Clow via Boost < boost(a)lists.boost.org> wrote: > are now available at: > <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source < > https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>> > > The SHA256 checksums are as follows: > > 8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf > boost_1_79_0_b1_rc1.tar.bz2 > 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 > boost_1_79_0_b1_rc1.tar.gz > 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b > boost_1_79_0_b1_rc1.zip > 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 > boost_1_79_0_b1_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 > Looks good on Windows/Visual Studio. toolset arch compile Link Execute msvc-10.0 32 X X X msvc-10.0 64 X X X msvc-11.0 32 X X X msvc-11.0 64 X X X msvc-12.0 32 X X X msvc-12.0 64 X X X msvc-14.0 32 X X X msvc-14.0 64 X X X msvc-14.1 32 X X X msvc-14.1 64 X X X msvc-14.2 32 X X X msvc-14.2 64 X X X msvc-14.3 32 X X X msvc-14.3 64 X X X Compile means that the b2 command completed without errors Link means that visual studio was able to link a sample executable to a library (libboost_thread-vcXXX-mt[-gd]-1_XX.lib) generated Execute means that the linked program executed without errors. Full build logs can be found here: https://gist.github.com/teeks99/acf919a716deeb001acaa2b4f12cb757 Tom ---------- Forwarded message ---------- From: Matt Borland <matt(a)mattborland.com> To: boost(a)lists.boost.org Cc: Bcc: Date: Fri, 11 Mar 2022 10:57:15 +0000 Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available > 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 > > _______________________________________________ Boost.Filesystem fails to build using Apple Clang 13 with C++11/14/17/20 on M1 Pro Architecture. An issue has been opened here ( https://github.com/boostorg/filesystem/issues/231) Matt ---------- Forwarded message ---------- From: Andrey Semashev <andrey.semashev(a)gmail.com> To: boost(a)lists.boost.org Cc: Bcc: Date: Fri, 11 Mar 2022 14:09:22 +0300 Subject: Re: [boost] [release] Boost 1.79.0 Beta 1 Release Candidate 1 is available On 3/11/22 13:57, Matt Borland via Boost wrote: >> 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 >> >> _______________________________________________ > > Boost.Filesystem fails to build using Apple Clang 13 with C++11/14/17/20 on M1 Pro Architecture. An issue has been opened here ( https://github.com/boostorg/filesystem/issues/231) As replied in the issue, your build is picking up headers from a different Boost version in /usr/local/include. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost -- Salim Pamukcu

1 0

[release] Boost 1.79.0 Beta 1 Release Candidate 1 is available
by Marshall Clow 11 Mar '22

11 Mar '22

are now available at: <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source <https://boostorg.jfrog.io/ui/native/main/beta/1.79.0.beta1/source>> The SHA256 checksums are as follows: 8985105623f48d55be01076d98ca4e7a8cb548a8d7f9ad0e1fc3c710d2c75fcf boost_1_79_0_b1_rc1.tar.bz2 4b58e4d3b6ff1176b3c6cb9eec496c1f6d2535270e97ec140da533d68766ca39 boost_1_79_0_b1_rc1.tar.gz 768875ad5c77763445e8b119072cfa1e64854b071a353dd44c3c73ff46df910b boost_1_79_0_b1_rc1.zip 4d05b458cd039afe86003cf7e1e6c3a358b5b2d031892e620eedc344ab200246 boost_1_79_0_b1_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

4 8

Master branch now closed for 1.79.0 beta release
by Marshall Clow 10 Mar '22

10 Mar '22

Please do not make any commits to the master branch. — Marshall

1 0

[Graph] Attempt to resolve open issue
by Anne van de Graaf 10 Mar '22

10 Mar '22

Hello all, I am trying to get an open issue in Boost.Graph resolved. Since I haven't received any response at the corresponding GitHub page nor from the Boost Users mailing list (where I posted the below message last Monday), I am reaching out to you. My aim is to get in touch with the maintainer(s) of Boost.Graph in order to discuss what is the preferred/most efficient way to fix the issue. Since this is my first post to this mailing list, please accept my apologies if you feel this is not the right way to get in touch with the maintainers. In that case, I would appreciate it very much if you could kindly explain what I should have done instead. Please find below a copy of my message that I sent last Monday to the Boost Users mailing list. Thank you very much for your attention and any replies. Original message: When I remove a vertex from a graph, I occasionally experience a crash (on a system running Red Hat Enterprise Linux 8.5). I have been able to replicate the behavior with the following test program: #include <vector> #include <boost/graph/adjacency_list.hpp> int main() { using MyGraph = boost::adjacency_list<boost::setS, boost::vecS, boost::undirectedS>; using MyVertexDescriptor = boost::graph_traits<MyGraph>::vertex_descriptor; using MyVertexDescriptorVec = std::vector<MyVertexDescriptor>; MyGraph g; MyVertexDescriptorVec vertices{ boost::add_vertex( g ), boost::add_vertex( g ), boost::add_vertex( g ) }; boost::add_edge( vertices[0], vertices[1], g ); boost::add_edge( vertices[1], vertices[2], g ); boost::clear_vertex( vertices[0], g ); boost::remove_vertex( vertices[0], g ); return 0; } Also on a Windows platform, I observe similar behavior. When I build the above code with Microsoft Visual Studio 2019 (MSVC 14.27.29110) and run it with a debugger, a debug assertion is triggered ("cannot increment value-initialized map/set iterator"). In both cases (on Linux and Windows platforms), the debugger reveals that the problem is at line 2071 of boost/graph/detail/adjacency_list.hpp. For clarity, I have copied the involved template function below: template < class EdgeList, class vertex_descriptor > inline void reindex_edge_list( EdgeList& el, vertex_descriptor u, boost::disallow_parallel_edge_tag) { for (typename EdgeList::iterator ei = el.begin(); ei != el.end(); ++ei) // line 2071: increment operator fails { if (ei->get_target() > u) { typename EdgeList::value_type ce = *ei; el.erase(ce); --ce.get_target(); el.insert(ce); } } } While I was searching for a proper place to post my question, I found the following issue at GitHub (which was opened on July 1 of this year): https://github.com/boostorg/graph/issues/268. This appears to be the exact same issue. So last week, I added a comment saying that I am facing the exact same problem. Unfortunately, so far no one has responded yet. To me, it seems that the problem is well-understood. Also, some have proposed a bug fix to resolve the issue (including a pull request). Nevertheless, no progress has been made over the past months. So I was just wondering what is the best way to proceed if we want to fix the issue in Boost itself? Is there anything that I can do (apart from starting this thread) to help in resolving the issue? Any feedback is greatly appreciated. Kind regards, Anne van de Graaf

3 6

Windows Build Issue for Boost Wave
by Tom Kent 09 Mar '22

09 Mar '22

In preparation for the lockdown today, I did a dry run of the windows build based on the latest snapshot. During this build I encountered errors with wave on the msvc-12.0 compiler (both 32 & 64 bit). Roughly the following is repeated several times during the build: compile-c-c++ D:\RB\bin.v2\boost\bin.v2\libs\wave\build\msvc-12.0\debug\address-model-32\threading-multi\token_ids.obj token_ids.cpp D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(335) : error C2146: syntax error : missing ';' before identifier 'token_id' D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(335) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(341) : error C2146: syntax error : missing ';' before identifier 'token_id' D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(341) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(341) : error C2086: 'int boost::wave::constexpr' : redefinition D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(335) : see declaration of 'boost::wave::constexpr' D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(347) : error C2144: syntax error : 'bool' should be preceded by ';' D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(347) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(347) : error C2086: 'int boost::wave::constexpr' : redefinition D:\RB\boost_1_79_0\boost/wave/token_ids.hpp(335) : see declaration of 'boost::wave::constexpr' call "D:\RB\bin.v2\boost\bin.v2\standalone\msvc\msvc-12.0\address-model-32\architecture-x86\msvc-setup.bat" x86 >nul cl /Zm800 -nologo "libs\wave\src\token_ids.cpp" -c -Fo"D:\RB\bin.v2\boost\bin.v2\libs\wave\build\msvc-12.0\debug\address-model-32\threading-multi\token_ids.obj" -TP /wd4675 /EHs /GR /Z7 /Od /Ob0 /W3 /MDd /Zc:forScope /Zc:wchar_t /Zc:inline -DBOOST_ALL_DYN_LINK=1 -DBOOST_ALL_NO_LIB=1 -D_CRT_SECURE_NO_DEPRECATE -D_SCL_SECURE_NO_DEPRECATE "-I." ...failed compile-c-c++ D:\RB\bin.v2\boost\bin.v2\libs\wave\build\msvc-12.0\debug\address-model-32\threading-multi\token_ids.obj... Hope this helps, if not fixed it will be blocking the beta rc when it gets rolled. Tom

1 0

Boost 1.79.0 closed for breaking changes and new libraries today
by Glen Fernandes 02 Mar '22

02 Mar '22

We are closed for new libraries and breaking changes today. We will close for all major changes this Friday (2022-03-04). And will close for the beta the following Wednesday (2022-03-09). The Release Managers

1 0

std::numeric_limits<__float128>::signaling_NaN + __float128-Type
by Gero Peterhoff 26 Feb '22

26 Feb '22

Hello, please see https://godbolt.org/z/Ksshxvhaj 1) std::numeric_limits<__float128>::signaling_NaN always returns 0 but gcc-__builtin_nansq doesn't. I think __builtin_nansq is correct as it is also distinct from std::numeric_limits<__float128>::quiet_NaN (__builtin_nanq). 2) The types __float128, __extension__ __float128 (gcc) and _Quad (intel) are identical, but there are different definitions in boost/config/detail/suffix.hpp and boost/math/cstdfloat/cstdfloat_types.hpp. I think it would make sense to have just one definition or is there a reason why it was done that way? If yes, which one is it? You could always use __float128 directly and/or adjust boost/config/detail/suffix.hpp so that it also works with clang/intel. Which way would be better? I would like to help consolidate this but without having to deal with different typedef's or long #define's. thx Gero

3 13