- Boost - lists.boost.org

[gil] Can I merge one fix for regression in 1.74?
by Mateusz Loskot 27 Jul '20

27 Jul '20

Dear Release Manager, We've received bug report about regression and have just fixed it in the develop branch of GIL: https://github.com/boostorg/gil/commit/8555ba08cd53c2ec5d65ea60bae9578ad586… Can I merge this fix to master? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

2 2

[gil] Can I merge two minor fixes to header dependencies and tests for 1.7.4?
by Mateusz Loskot 26 Jul '20

26 Jul '20

Dear Release Manager, I'd like to request permission to merge these two minor fixes into GIL's master for release with 1.74 1. Fix dynamic_image extension header dependencies https://github.com/boostorg/gil/pull/508 This basically removes all-in-one #include <boost/gil.hpp from GIL's own headers. 2. Re-enable self containing header tests in CMake https://github.com/boostorg/gil/pull/509 Minor correction to an incidental disabling of headers tests in CMake. May I? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

2 4

Two Graphs Common Spanning Trees Issue [GSoC]
by Prakash Tiwari 24 Jul '20

24 Jul '20

Hello, Community Members and developers, I'm student of Google Summer Of Code and contributing to the pgRouting <https://github.com/pgRouting/pgrouting/>[1]. I need to use boost algorithm boost::two_graphs_common_spanning_trees. I have gone through the documentation and try to use it (with help of example.cpp) But I found that this algorithm is not returning the expected results. I have mentioned the example that I have used and explained the expected and given results <https://github.com/prakashupes/ProposalCodes/issues/1>.[2] So, please try to figure out that is it a bug implemented algorithm or It might be possible that I'm using the algorithm in the wrong way. Thanks Prakash Tiwari [1].https://github.com/pgRouting/pgrouting/ [2]. https://github.com/prakashupes/ProposalCodes/issues/1

1 0

[release] Boost 1.74.0 Beta 1 Release Candidate 1
by Marshall Clow 15 Jul '20

15 Jul '20

The release candidates for the first 1.74.0 beta release are now available at: https://dl.bintray.com/boostorg/beta/1.74.0.beta.1/source/ The release notes are not yet available. The SHA256 checksums are as follows: 577a6b575ff2c227e14cce1b929c73d969475e58f3d2ab2901ad234f773bbd12 boost_1_74_0_b1_rc1.7z ba09c72dc848e7c0904922967014d853897b5a634926c910cc3b1fd627c31605 boost_1_74_0_b1_rc1.tar.bz2 2ccdc39efa076822cf1b359f9449f9d07707f3e27a18b393297b25885a9ff45b boost_1_74_0_b1_rc1.tar.gz c267c450166e040a374eaddab5e583cef09f6c3fe96a4db826172d0315c38dd5 boost_1_74_0_b1_rc1.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 Boost Release Managers

4 7

[release] Master branch now closed for 1.74.0 beta release
by Marshall Clow 12 Jul '20

12 Jul '20

1 0

[Release] master branch will be closed for the 1/74/0 beta release TODAY
by Marshall Clow 11 Jul '20

11 Jul '20

Later today the master branch will be closed for all changes. See the calendar here for more dates: https://www.boost.org/development/ <https://www.boost.org/development/> The master branch will be re-opened after the beta release. Thanks, — The Boost Release Team

1 0

CI errors in [serialization] windows cygwin, mingw builds
by Jeff Garland 11 Jul '20

11 Jul '20

I've been seeing a bunch of CI errors related to serialization that seem to be new. Not seeing this so much on the test dashboard however. https://ci.appveyor.com/project/jeking3/date-time-1evbf/builds/33988388 gcc.compile.c++ bin.v2\libs\serialization\build\gcc-mngw6\rls\cxstd-11-iso\thrd-mlt\vsblt-hdn\xml_iarchive.o gcc.compile.c++ bin.v2\libs\serialization\build\gcc-mngw6\rls\cxstd-11-iso\thrd-mlt\vsblt-hdn\xml_oarchive.o In file included from ./boost/archive/iterators/mb_from_wchar.hpp:31, from ./boost/archive/impl/xml_oarchive_impl.ipp:28, from libs\serialization\src\xml_oarchive.cpp:23: ./boost/archive/detail/utf8_codecvt_facet.hpp:20: warning: "BOOST_ARCHIVE_DECL" redefined 20 | #define BOOST_ARCHIVE_DECL | In file included from ./boost/archive/detail/auto_link_archive.hpp:26, from ./boost/archive/xml_oarchive.hpp:29, from libs\serialization\src\xml_oarchive.cpp:17: ./boost/archive/detail/decl.hpp:28: note: this is the location of the previous definition 28 | #define BOOST_ARCHIVE_DECL BOOST_SYMBOL_EXPORT | gcc.compile.c++ bin.v2\libs\serialization\build\gcc-mngw6\rls\cxstd-11-iso\thrd-mlt\vsblt-hdn\xml_archive_exception.o gcc.compile.c++ bin.v2\libs\serialization\build\gcc-mngw6\rls\cxs

3 7

Build Errors for ASIO on msvc-10.0 and -11.0
by Tom Kent 10 Jul '20

10 Jul '20

After seeing the announcement that library freeze is coming, I just tried building the master snapshot with the build scripts I use for building the windows releases. I encountered failures in msvc-10.0 and msvc-11.0 for ASIO. .\boost/asio/execution/any_executor.hpp(940) : error C2668: 'boost::asio::execution::detail::any_executor_base::query_fn_impl' : ambiguous call to overloaded function .\boost/asio/execution/any_executor.hpp(915): could be 'void boost::asio::execution::detail::any_executor_base::query_fn_impl<Ex,Prop>(void *,const void *,const void *,boost::type *)' with [ Ex=void, Prop=boost::asio::execution::context_as_t<boost::asio::execution_context &> ] .\boost/asio/execution/any_executor.hpp(902): or 'void boost::asio::execution::detail::any_executor_base::query_fn_impl<Ex,Prop>(void *,const void *,const void *,boost::type *)' with [ Ex=void, Prop=boost::asio::execution::context_as_t<boost::asio::execution_context &> ] .\boost/asio/execution/any_executor.hpp(887): or 'void boost::asio::execution::detail::any_executor_base::query_fn_impl<Ex,Prop>(void *,const void *,const void *,boost::type *)' with [ Ex=void, Prop=boost::asio::execution::context_as_t<boost::asio::execution_context &> ] .\boost/asio/execution/any_executor.hpp(875): or 'void boost::asio::execution::detail::any_executor_base::query_fn_impl<Ex,Prop>(void *,const void *,const void *,boost::type *)' with [ Ex=void, Prop=boost::asio::execution::context_as_t<boost::asio::execution_context &> ] .\boost/asio/execution/any_executor.hpp(859): or 'void boost::asio::execution::detail::any_executor_base::query_fn_impl<Ex,Prop>(void *,const void *,const void *,boost::type *)' with [ Ex=void, Prop=boost::asio::execution::context_as_t<boost::asio::execution_context &> ] .\boost/asio/execution/any_executor.hpp(849): or 'void boost::asio::execution::detail::any_executor_base::query_fn_impl<Ex,Prop>(void *,const void *,const void *,boost::type *)' with [ Ex=void, Prop=boost::asio::execution::context_as_t<boost::asio::execution_context &> ] .\boost/asio/execution/any_executor.hpp(837): or 'void boost::asio::execution::detail::any_executor_base::query_fn_impl<Ex,Prop>(void *,const void *,const void *,boost::type *)' with [ Ex=void, Prop=boost::asio::execution::context_as_t<boost::asio::execution_context &> ] .\boost/asio/execution/any_executor.hpp(827): or 'void boost::asio::execution::detail::any_executor_base::query_fn_impl<Ex,Prop>(void *,const void *,const void *,void *)' with [ Ex=void, Prop=boost::asio::execution::context_as_t<boost::asio::execution_context &> ] while trying to match the argument list '(void *, const void *, const void *, int)' .\boost/asio/execution/any_executor.hpp(1782) : see reference to function template instantiation 'void boost::asio::execution::detail::any_executor_base::query_fn<Ex,T1>(void *,const void *,const void *)' being compiled with [ Ex=void, T1=boost::asio::execution::context_as_t<boost::asio::execution_context &> ] .\boost/asio/execution/any_executor.hpp(1782) : see reference to function template instantiation 'const boost::asio::execution::detail::any_executor_base::prop_fns<Poly> *boost::asio::execution::any_executor<<unnamed-symbol>,boost::asio::execution::detail::blocking::never_t<I>,boost::asio::execution::prefer_only<InnerProperty>,boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::tracked_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::untracked_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::fork_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::continuation_t<0>>>::prop_fns_table<void>(void)' being compiled with [ Poly=boost::asio::execution::any_executor<boost::asio::execution::context_as_t<boost::asio::execution_context &>,boost::asio::execution::detail::blocking::never_t<0>,boost::asio::execution::prefer_only<boost::asio::execution::detail::blocking::possibly_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::tracked_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::untracked_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::fork_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::continuation_t<0>>>, <unnamed-symbol>=boost::asio::execution::context_as_t<boost::asio::execution_context &>, I=0, InnerProperty=boost::asio::execution::detail::blocking::possibly_t<0> ] .\boost/asio/execution/any_executor.hpp(1782) : while compiling class template member function 'boost::asio::execution::any_executor<<unnamed-symbol>,boost::asio::execution::detail::blocking::never_t<I>,boost::asio::execution::prefer_only<InnerProperty>,boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::tracked_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::untracked_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::fork_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::continuation_t<0>>>::any_executor(void)' with [ <unnamed-symbol>=boost::asio::execution::context_as_t<boost::asio::execution_context &>, I=0, InnerProperty=boost::asio::execution::detail::blocking::possibly_t<0> ] .\boost/asio/detail/io_object_impl.hpp(168) : see reference to class template instantiation 'boost::asio::execution::any_executor<<unnamed-symbol>,boost::asio::execution::detail::blocking::never_t<I>,boost::asio::execution::prefer_only<InnerProperty>,boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::tracked_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::untracked_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::fork_t<0>>,boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::continuation_t<0>>>' being compiled with [ <unnamed-symbol>=boost::asio::execution::context_as_t<boost::asio::execution_context &>, I=0, InnerProperty=boost::asio::execution::detail::blocking::possibly_t<0> ] .\boost/asio/basic_socket.hpp(1804) : see reference to class template instantiation 'boost::asio::detail::io_object_impl<IoObjectService,Executor>' being compiled with [ IoObjectService=boost::asio::detail::win_iocp_socket_service<boost::asio::ip::udp>, Executor=boost::asio::any_io_executor ] .\boost/asio/basic_datagram_socket.hpp(53) : see reference to class template instantiation 'boost::asio::basic_socket<Protocol,Executor>' being compiled with [ Protocol=boost::asio::ip::udp, Executor=boost::asio::any_io_executor ] libs\log\src\syslog_backend.cpp(315) : see reference to class template instantiation 'boost::asio::basic_datagram_socket<Protocol>' being compiled with [ Protocol=boost::asio::ip::udp ] Hopefully this can be cleared up before the beta. Thanks, Tom

3 3

[stl_interfaces] Ok to merge small fix to C++20-mode builds before release?
by Zach Laine 09 Jul '20

09 Jul '20

I have just committed a fix to develop that addresses compilation errors in C++20 builds. Is it too late to merge this to master? The change is here: https://github.com/boostorg/stl_interfaces/commit/6d31433af0b7cb8c7f9140ce4… Zach

2 2

[Boost][Outcome] Compile error?
by Emil Dotchevski 07 Jul '20

07 Jul '20

When exceptions are disabled, I get: In file included from ../../../../boost/outcome/result.hpp:34: In file included from ../../../../boost/outcome/boost_result.hpp:36: In file included from ../../../../boost/exception_ptr.hpp:9: In file included from ../../../../boost/exception/detail/exception_ptr.hpp:17: ../../../../boost/exception/detail/clone_current_exception.hpp:22:6: error: This header requires exception handling to be enabled. Is there a way to configure Outcome so it does not use (boost) exception_ptr?

5 20