- Boost-users - lists.preview.boost.org

boost placeholders help
by Hariharan.A.S 25 Jan '22

25 Jan '22

Hi, I am trying to build my catkin workspace for Ros Noetic in my raspberry pi 400 running Buster. I get the following message while building roscpp Scanning dependencies of target roscpp_generate_messages Scanning dependencies of target roscpp [ 31%] Built target roscpp_generate_messages [ 36%] Building CXX object CMakeFiles/roscpp.dir/src/libros/master.cpp.o [ 36%] Building CXX object CMakeFiles/roscpp.dir/src/libros/network.cpp.o [ 36%] Building CXX object CMakeFiles/roscpp.dir/src/libros/subscriber.cpp.o [ 37%] Building CXX object CMakeFiles/roscpp.dir/src/libros/common.cpp.o [ 38%] Building CXX object CMakeFiles/roscpp.dir/src/libros/publisher_link.cpp.o In file included from /home/pi/ros_catkin_ws/src/ros_comm/roscpp/include/ros/node_handle.h:32, from /home/pi/ros_catkin_ws/src/ros_comm/roscpp/src/libros/subscriber.cpp:29: /home/pi/ros_catkin_ws/src/ros_comm/roscpp/include/ros/publisher.h: In member function ‘boost::function<void(const boost::shared_ptr<ros::SubscriberLink>&)> ros::Publisher::getLastMessageCallback()’: /home/pi/ros_catkin_ws/src/ros_comm/roscpp/include/ros/publisher.h:174:70: error: ‘boost::placeholders’ has not been declared return boost::bind(&Impl::pushLastMessage, impl_.get(), boost::placeholders::_1); ^~~~~~~~~~~~ In file included from /home/pi/ros_catkin_ws/src/ros_comm/roscpp/src/libros/subscriber.cpp:29: /home/pi/ros_catkin_ws/src/ros_comm/roscpp/include/ros/node_handle.h: In member function ‘ros::Subscriber ros::NodeHandle::subscribe(const string&, uint32_t, void (T::*)(M), T*, const ros::TransportHints&)’: /home/pi/ros_catkin_ws/src/ros_comm/roscpp/include/ros/node_handle.h:406:91: error: ‘boost::placeholders’ has not been declared ops.template initByFullCallbackType<M>(topic, queue_size, boost::bind(fp, obj, boost::placeholders::_1)); ^~~~~~~~~~~~ /home/pi/ros_catkin_ws/src/ros_comm/roscpp/include/ros/node_handle.h: In member function ‘ros::Subscriber ros::NodeHandle::subscribe(const string&, uint32_t, void (T::*)(M) const, T*, const ros::TransportHints&)’: /home/pi/ros_catkin_ws/src/ros_comm/roscpp/include/ros/node_handle.h:417:91: error: ‘boost::placeholders’ has not been declared ops.template initByFullCallbackType<M>(topic, queue_size, boost::bind(fp, obj, boost::placeholders::_1)); ^~~~~~~~~~~~ /home/pi/ros_catkin_ws/src/ros_comm/roscpp/include/ros/node_handle.h: In member function ‘ros::Subscriber ros::NodeHandle::subscribe(const string&, uint32_t, void (T::*)(const boost::shared_ptr<const M>&), T*, const ros::TransportHints&)’: /home/pi/ros_catkin_ws/src/ros_comm/roscpp/include/ros/node_handle.h:470:73: error: ‘boost::placeholders’ has not been declared ops.template init<M>(topic, queue_size, boost::bind(fp, obj, boost::placeholders::_1)); ^~~~~~~~~~~~ /home/pi/ros_catkin_ws/src/ros_comm/roscpp/include/ros/node_handle.h: In member function ‘ros::Subscriber ros::NodeHandle::subscribe(const string&, uint32_t, void (T::*)(const boost::shared_ptr<const M>&) const, T*, const ros::TransportHints&)’: /home/pi/ros_catkin_ws/src/ros_comm/roscpp/include/ros/node_handle.h:480:73: error: ‘boost::placeholders’ has not been declared ops.template init<M>(topic, queue_size, boost::bind(fp, obj, boost::placeholders::_1)); ^~~~~~~~~~~~ /home/pi/ros_catkin_ws/src/ros_comm/roscpp/include/ros/node_handle.h: In member function ‘ros::Subscriber ros::NodeHandle::subscribe(const string&, uint32_t, void (T::*)(M), const boost::shared_ptr<U>&, const ros::TransportHints&)’: /home/pi/ros_catkin_ws/src/ros_comm/roscpp/include/ros/node_handle.h:533:97: error: ‘boost::placeholders’ has not been declared ops.template initByFullCallbackType<M>(topic, queue_size, boost::bind(fp, obj.get(), boost::placeholders::_1)); ^~~~~~~~~~~~ /home/pi/ros_catkin_ws/src/ros_comm/roscpp/include/ros/node_handle.h: In member function ‘ros::Subscriber ros::NodeHandle::subscribe(const string&, uint32_t, void (T::*)(M) const, const boost::shared_ptr<U>&, const ros::TransportHints&)’: /home/pi/ros_catkin_ws/src/ros_comm/roscpp/include/ros/node_handle.h:544:97: error: ‘boost::placeholders’ has not been declared ops.template initByFullCallbackType<M>(topic, queue_size, boost::bind(fp, obj.get(), boost::placeholders::_1)); I am not sure how to fix this problem. Any help is much appreciated Thank you Hariharan -- Hariharan.A.S

1 0

Vector values gradients for vector -> scalar function
by Amit Gupta 25 Jan '22

25 Jan '22

I am currently exploring boost as autodiff framework for my application. I would like to calculate the derivative of a vector->scalar function. However I could not find a way to evaluate the same, rather I always get total gradient. Example: How to get the following program yield output equivalent to JAX fwd? #include <boost/math/differentiation/autodiff.hpp> #include <iostream> #include<vector> template <typename T> T power_sum(double p, std::vector<T> &z){ T y=0.0; for (int i=0; i<6;i++){ y += pow(z[i], p); } return y; } int main() { using namespace boost::math::differentiation; constexpr unsigned Order = 2; std::vector<double> z_v = {1.,2.,3.,4.,5.,6.}; std::vector<autodiff_fvar<double, Order> > z; for (int i=0; i<6;i++){ z.push_back(make_fvar<double, Order>(z_v[i])); } auto y = power_sum(2.0,z); std::cout<<y<<"\n"; std::cout<<y.derivative(1)<<"\n"; return 0; } JAX output: import jax as jx import jax.numpy as jnp x = jnp.array([1.0, 2.0, 3.0, 4.0, 5.0, 6.0]) def power_sum(x, p): y = x[0] ** p + x[1] ** p + x[2] ** p + x[3] ** p + x[4] ** p + x[5] ** p return y f_prime = jx.jacfwd(power_sum)(x,2.0) f_prime # DeviceArray([ 2., 4., 6., 8., 10., 12.], dtype=float32) I understand I can do it by send array 6 times with all other vvector values being zero. Is there a better way?

1 0

Re: [Boost-users] casually blocked UDP port
by Alexander Carôt 17 Jan '22

17 Jan '22

Hello again, I'd consider using boost asio SO_REUSEPORT option in order to reuse the port if already taken according to this thread: https://stackoverflow.com/questions/34596638/boost-asio-so-reuseport I will try it asap but please let me know if you have concerns or better solutions. Thanks and best Alex P.S.: see below – I now know how to reproduce the issue: When my application does receive UDP streaming data I spontaneously quit the application. Then doing: "netstat -p UDP" shows me the following Proto Recv-Q Send-Q Local Address Foreign Address (state) udp4 1026 0 *.50050 *.* So, basically the receive queue for this socket is not empty and the previous bind port is indeed still there. If anyone has an idea how to proceed from here on please let me know but now I might be able to fix it myself already. Best Alex Thanks for the swift response, Andreas ! In fact I am aware of what you wrote but with regard to the conditions my app works under it is extremely unlikely that some other process is taking this port. However, the next step for me is to identify which process actually has taken it. In that regard a follow-up question: Once an application (which uses boost sockets) has shut down (for crash or other reasons) the local bind port is also automatically released, right ? In other words: Can the OS stick a port although the corresponding application is not existent anymore ? I've been assuming no so far but maybe I am mistaken so I just need confirmation. Thank you, best Alex -- http://www.carot.de Email : Alexander(a)Carot.de Tel.: +49 (0)177 5719797 > Gesendet: Samstag, 15. Januar 2022 um 23:46 Uhr > Von: "Andreas Wehrmann via Boost-users" <boost-users(a)lists.boost.org> > An: boost-users(a)lists.boost.org > Cc: "Andreas Wehrmann" <a.wehrmann(a)yandex.com> > Betreff: Re: [Boost-users] casually blocked UDP port > > Am 14.01.2022 um 22:50 schrieb Alexander Carôt via Boost-users: > > Hello all, > > > > I have a problem with a a casually blocked UDP bind port: My application uses UDP port 50050 and initiates the socket this way: > > > > So I am basically using bind port 50050 and if it fails I am increasing it by one until the bind suceeds. In most cases the bind to port 50050 works fine but casually after a relaunch of the app or a crash the bind port 50050 appears to be blocked which is why it increases to higher numbers. > > > > Hi, > be aware that UDP sockets may are opened and closed for sending a single > request only by many applications/services. > If the sending application doesn't care about the local port and leaves > it up to the OS to assign a local port number, > you may run into the situation that another application/service/daemon > is opening a UDP socket, > not caring about the local port and the OS happens to assign the port > number that you want to bind your own socket to. > > All the best, > Andreas > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > https://lists.boost.org/mailman/listinfo.cgi/boost-users >

2 2

Re: [Boost-users] casually blocked UDP port
by Alexander Carôt 16 Jan '22

16 Jan '22

P.S.: see below – I now know how to reproduce the issue: When my application does receive UDP streaming data I spontaneously quit the application. Then doing: "netstat -p UDP" shows me the following Proto Recv-Q Send-Q Local Address Foreign Address (state) udp4 1026 0 *.50050 *.* So, basically the receive queue for this socket is not empty and the previous bind port is indeed still there. If anyone has an idea how to proceed from here on please let me know but now I might be able to fix it myself already. Best Alex Thanks for the swift response, Andreas ! In fact I am aware of what you wrote but with regard to the conditions my app works under it is extremely unlikely that some other process is taking this port. However, the next step for me is to identify which process actually has taken it. In that regard a follow-up question: Once an application (which uses boost sockets) has shut down (for crash or other reasons) the local bind port is also automatically released, right ? In other words: Can the OS stick a port although the corresponding application is not existent anymore ? I've been assuming no so far but maybe I am mistaken so I just need confirmation. Thank you, best Alex -- http://www.carot.de Email : Alexander(a)Carot.de Tel.: +49 (0)177 5719797 > Gesendet: Samstag, 15. Januar 2022 um 23:46 Uhr > Von: "Andreas Wehrmann via Boost-users" <boost-users(a)lists.boost.org> > An: boost-users(a)lists.boost.org > Cc: "Andreas Wehrmann" <a.wehrmann(a)yandex.com> > Betreff: Re: [Boost-users] casually blocked UDP port > > Am 14.01.2022 um 22:50 schrieb Alexander Carôt via Boost-users: > > Hello all, > > > > I have a problem with a a casually blocked UDP bind port: My application uses UDP port 50050 and initiates the socket this way: > > > > So I am basically using bind port 50050 and if it fails I am increasing it by one until the bind suceeds. In most cases the bind to port 50050 works fine but casually after a relaunch of the app or a crash the bind port 50050 appears to be blocked which is why it increases to higher numbers. > > > > Hi, > be aware that UDP sockets may are opened and closed for sending a single > request only by many applications/services. > If the sending application doesn't care about the local port and leaves > it up to the OS to assign a local port number, > you may run into the situation that another application/service/daemon > is opening a UDP socket, > not caring about the local port and the OS happens to assign the port > number that you want to bind your own socket to. > > All the best, > Andreas > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > https://lists.boost.org/mailman/listinfo.cgi/boost-users >

1 0

casually blocked UDP port
by Alexander Carôt 16 Jan '22

16 Jan '22

Hello all, I have a problem with a a casually blocked UDP bind port: My application uses UDP port 50050 and initiates the socket this way: udp::resolver resolver(dFC->myIoService); int port = 50050; bool failed; do{ failed = false; udp::resolver::query query(udp::v4(), IPAddress, port); try { dFC->s = new udp::socket( dFC->myIoService, udp::endpoint(*resolver.resolve(query))); } catch (std::exception &e) { failed = true; int intPort = this->intConverter(port); intPort++; ostringstream conv; conv << intPort; port = conv.str(); cout << "new port: " << port << endl; } while (failed); So I am basically using bind port 50050 and if it fails I am increasing it by one until the bind suceeds. In most cases the bind to port 50050 works fine but casually after a relaunch of the app or a crash the bind port 50050 appears to be blocked which is why it increases to higher numbers. Now I wonder how the port can still be taken although the app has terminated and if there is way to force the app / the OS using port 50050 ? So far I have seen this on OSX only – on Windows and Linux I haven't noticed it yet. Thanks in advance for any pointer how to resolve my isse, best Alex -- http://www.carot.de Email : Alexander(a)Carot.de Tel.: +49 (0)177 5719797

2 2

exception on boost serialization
by Alessio Mochi 13 Jan '22

13 Jan '22

Hello, I can't resolve my exception when I compile my qt project with visual studio 2022. Error C2039 'throw_exception': is not a member of 'boost' DentalCad E:\boost_1_78_0\boost\serialization\throw_exception.hpp 30 I tried a compile a small example and work correctly without exception. I don't understand how solve the problem. Have you a suggest? Thanks in advance.

4 10

Communicating with MS SQL Server.
by Senthil Cheetancheri 12 Jan '22

12 Jan '22

Hi, Is there a Boost library to communicate with Microsoft SQLServer? I see there is a proposal for MySQL (https://anarthal.github.io/boost-mysql-docs/index.html) but can't seem to find anything for MS SQLServer. Any pointers would be appreciated. Thanks, Senthil.

1 0

Clarification on statechart post_event vs process_event within react()
by John McCabe 10 Jan '22

10 Jan '22

Hi, Apologies if this has already been answered/clarified, but my search of the internet to try to get a definitive answer, at least one I recognised as being definitive, was unsuccessful. Below I have posted some source code, based on the stopwatch example from the tutorial, but using an 'external' object to delegate the actual handling of event stuff to and using the state, rather than simple_state base class, and some other tweaks. This is a cut down version of something that someone I work with has devised, but I just wanted to get a clear answer on whether process_event() should be getting called in cases like this. I think it probably should not since, in the code below, you change state (with a state object's destructor being executed) whilst you're executing that state's react(EvStartStop) function. If someone can confirm this is the correct interpretation that would be very much appreciated. Any questions, feel free to ask (BTW - I'm compiling for C++17) John PS - In case it's of any use, the output from running this code is: ------ Entered Active Entered Stopped Stopped - payload2 m_charValue: a Exited ~Stopped <<<--- This is the bit I don't like the look of because... Entered Running Active - payload2 m_charValue: a <<<--- ... this happens from the forward_event() call payload1 value1: 20 payload1 value2: 200.2 Exited ~Running Entered Stopped Exiting Program Exited ~Stopped Exited ~Active ------ If I swap the //*** comments to the doProcess() lines instead of doPost(), the output seems more sensible ------ Entered Active Entered Stopped Stopped - payload2 m_charValue: a Exited ~Stopped Entered Running Active - payload2 m_charValue: a payload1 value1: 20 payload1 value2: 200.2 Exited ~Running Entered Stopped Exiting Program Exited ~Stopped Exited ~Active ------ ========== code =========== #include <boost/statechart/event.hpp> #include <boost/statechart/state_machine.hpp> #include <boost/statechart/state.hpp> #include <boost/statechart/transition.hpp> #include <boost/statechart/custom_reaction.hpp> #include <boost/mpl/list.hpp> #include <iostream> #include <string> namespace sc = boost::statechart; namespace mpl = boost::mpl; // Forward declare a handler 'class' that's going to have activity delegated to it struct Handler; // Normal example start/stop and reset events struct EvStartStop : sc::event<EvStartStop> {}; struct EvReset : sc::event<EvReset> {}; // A couple of events that carry data with them struct EvPayload1 : sc::event<EvPayload1> { EvPayload1(int value1, double value2) : m_value1 { value1 }, m_value2 { value2 } {}; int m_value1 { 0 }; double m_value2 { 0.0 }; }; struct EvPayload2 : sc::event<EvPayload2> { EvPayload2(const char& charValue) : m_charValue { charValue } {}; char m_charValue { false }; }; // Back to the example bits struct Active; struct StopWatch : sc::state_machine<StopWatch, Active> { typedef sc::transition<EvReset, Active> reactions; // The extra 'handler' stuff void setHandler(Handler* handler) { m_handler = handler; }; Handler* getHandler() const { return m_handler; }; Handler* m_handler { nullptr }; // Used to make post_event() accessible from an external class...seems unpleasant, but... using sc::state_machine<StopWatch, Active>::post_event; }; // The implementation of the Handler class; created with a reference to a StopWatch object struct Handler { Handler(StopWatch& stopWatch) : m_stopWatch { stopWatch } {}; void doPost() { m_stopWatch.post_event(EvStartStop()); } void doProcess() { m_stopWatch.process_event(EvStartStop()); } StopWatch& m_stopWatch; }; struct Stopped; struct Active : sc::state<Active, StopWatch, Stopped> { Active(my_context ctx) : my_base { ctx } { std::cout << "Entered Active" << std::endl; }; ~Active() { std::cout << "Exited ~Active" << std::endl; }; typedef mpl::list<sc::custom_reaction<EvPayload1>, sc::custom_reaction<EvPayload2>, sc::transition<EvReset, Active>> reactions; sc::result react(const EvPayload1& payload1) { std::cout << "payload1 Event NOT HANDLED" << std::endl; return discard_event(); } sc::result react(const EvPayload2& payload2) { std::cout << "Active - payload2 m_charValue: " << payload2.m_charValue << std::endl; return discard_event(); } }; struct Running : sc::state<Running, Active> { Running(my_context ctx) : my_base { ctx } { std::cout << "Entered Running" << std::endl; }; ~Running() { std::cout << "Exited ~Running" << std::endl; }; typedef mpl::list<sc::custom_reaction<EvPayload1>, sc::transition<EvStartStop, Stopped>> reactions; sc::result react(const EvPayload1& payload1) { std::cout << "payload1 value1: " << payload1.m_value1 << std::endl; std::cout << "payload1 value2: " << payload1.m_value2 << std::endl; //***context<StopWatch>().getHandler()->doPost(); context<StopWatch>().getHandler()->doProcess(); return discard_event(); } }; struct Stopped : sc::state<Stopped, Active> { Stopped(my_context ctx) : my_base { ctx } { std::cout << "Entered Stopped" << std::endl; }; ~Stopped() { std::cout << "Exited ~Stopped" << std::endl; }; typedef mpl::list<sc::custom_reaction<EvPayload2>, sc::transition<EvStartStop, Running>> reactions; sc::result react(const EvPayload2& payload2) { std::cout << "Stopped - payload2 m_charValue: " << payload2.m_charValue << std::endl; //***context<StopWatch>().getHandler()->doPost(); context<StopWatch>().getHandler()->doProcess(); return forward_event(); } }; int main() { StopWatch myWatch; Handler myHandler(myWatch); myWatch.setHandler(&myHandler); myWatch.initiate(); myWatch.process_event(EvPayload2 { 'a' }); myWatch.process_event(EvPayload1 { 20, 200.2 }); std::cout << "Exiting Program" << std::endl; return 0; }

1 1

boost.gil build failed with GCC11 and -std=c++20
by Qiang Ren 10 Jan '22

10 Jan '22

Hi, I am on ubuntu 20.04, I have GCC9.4 and 10.3 and 11.1 installed. I found that when set "-std=c++20", with gcc11, boost.gil will failed to build. Here is the simple test cpp to reproduce the issue: #include <sstream> #include <boost/gil.hpp> #include <boost/gil/extension/io/png.hpp> namespace gil = boost::gil; int main() { gil::rgb8_image_t img; std::stringstream buf(std::ios::in | std::ios::out | std::ios::binary); gil::read_and_convert_image(buf, img, gil::png_tag{}); return 0; } the build command is: g++ -o test test_gcc11_gil.cc -std=c++20 -I${THIRD_PARTY}/boost/boost_1_78_0 -L${THIRD_PARTY}/libpng/1.6.37/lib/ -lpng If replaced '-std=c++20' with '-std=c++17', the build would be OK, but with 'c++20', gcc 11 failed with the following errors: In file included from /data/lin/ThirdParty/boost/boost_1_78_0/boost/gil/extension/io/png/read.hpp:13, from /data/lin/ThirdParty/boost/boost_1_78_0/boost/gil/extension/io/png.hpp:11, from test_gcc11_gil.cc:3: /data/lin/ThirdParty/boost/boost_1_78_0/boost/gil/extension/io/png/tags.hpp:576:32: error: expected unqualified-id before ‘)’ token 576 | image_read_info< png_tag >() | ^ /data/lin/ThirdParty/boost/boost_1_78_0/boost/gil/extension/io/png/tags.hpp:711:36: error: expected unqualified-id before ‘)’ token 711 | image_read_settings< png_tag >() | ^ In file included from /data/lin/ThirdParty/boost/boost_1_78_0/boost/gil/extension/io/png/read.hpp:21, from /data/lin/ThirdParty/boost/boost_1_78_0/boost/gil/extension/io/png.hpp:11, from test_gcc11_gil.cc:3: /data/lin/ThirdParty/boost/boost_1_78_0/boost/gil/io/make_reader.hpp: In instantiation of ‘typename boost::gil::get_reader<String, FormatTag, ConversionPolicy>::type boost::gil::make_reader(Device&, const FormatTag&, const ConversionPolicy&, typename std::enable_if<typename boost::mp11::detail::mp_and_impl<boost::mp11::mp_list<boost::gil::detail::is_adaptable_input_device<FormatTag, Device, void>, boost::gil::is_format_tag<FormatTag> >, void>::type::value>::type*) [with Device = std::__cxx11::basic_stringstream<char>; FormatTag = boost::gil::png_tag; ConversionPolicy = boost::gil::detail::read_and_convert<boost::gil::default_color_converter>; typename boost::gil::get_reader<String, FormatTag, ConversionPolicy>::type = boost::gil::reader<boost::gil::detail::istream_device<boost::gil::png_tag>, boost::gil::png_tag, boost::gil::detail::read_and_convert<boost::gil::default_color_converter> >; typename std::enable_if<typename boost::mp11::detail::mp_and_impl<boost::mp11::mp_list<boost::gil::detail::is_adaptable_input_device<FormatTag, Device, void>, boost::gil::is_format_tag<FormatTag> >, void>::type::value>::type = void;typename boost::mp11::detail::mp_and_impl<boost::mp11::mp_list<boost::gil::detail::is_adaptable_input_device<FormatTag, Device, void>, boost::gil::is_format_tag<FormatTag> >, void>::type =std::integral_constant<bool, true>]’: /data/lin/ThirdParty/boost/boost_1_78_0/boost/gil/io/read_and_convert_image.hpp:263:34: required from ‘void boost::gil::read_and_convert_image(Device&, Image&, const FormatTag&, typename std::enable_if<typename boost::mp11::detail::mp_and_impl<boost::mp11::mp_list<boost::gil::detail::is_read_device<FormatTag, Device, void>, boost::gil::is_format_tag<FormatTag> >, void>::type::value>::type*) [with Device = std::__cxx11::basic_stringstream<char>; Image = boost::gil::image<boost::gil::pixel<unsigned char, boost::gil::layout<boost::mp11::mp_list<boost::gil::red_t, boost::gil::green_t, boost::gil::blue_t> > >, false, std::allocator<unsigned char> >; FormatTag = boost::gil::png_tag; typename std::enable_if<typename boost::mp11::detail::mp_and_impl<boost::mp11::mp_list<boost::gil::detail::is_read_device<FormatTag, Device, void>, boost::gil::is_format_tag<FormatTag> >, void>::type::value>::type = void; typename boost::mp11::detail::mp_and_impl<boost::mp11::mp_list<boost::gil::detail::is_read_device<FormatTag, Device, void>, boost::gil::is_format_tag<FormatTag> >, void>::type = std::integral_constant<bool, true>]’ test_gcc11_gil.cc:11:30: required from here /data/lin/ThirdParty/boost/boost_1_78_0/boost/gil/io/make_reader.hpp:193:30: error: no matching function for call to ‘boost::gil::image_read_settings<boost::gil::png_tag>::image_read_settings()’ 193 | return make_reader(file, image_read_settings<FormatTag>(), cc); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /data/lin/ThirdParty/boost/boost_1_78_0/boost/gil/extension/io/png/read.hpp:13, from /data/lin/ThirdParty/boost/boost_1_78_0/boost/gil/extension/io/png.hpp:11, from test_gcc11_gil.cc:3: /data/lin/ThirdParty/boost/boost_1_78_0/boost/gil/extension/io/png/tags.hpp:718:5: note: candidate: ‘boost::gil::image_read_settings<boost::gil::png_tag>::image_read_settings(const point_t&, const point_t&)’ 718 | image_read_settings( const point_t& top_left | ^~~~~~~~~~~~~~~~~~~ /data/lin/ThirdParty/boost/boost_1_78_0/boost/gil/extension/io/png/tags.hpp:718:5: note: candidate expects 2 arguments, 0 provided /data/lin/ThirdParty/boost/boost_1_78_0/boost/gil/extension/io/png/tags.hpp:707:8: note: candidate: ‘constexpr boost::gil::image_read_settings<boost::gil::png_tag>::image_read_settings(const boost::gil::image_read_settings<boost::gil::png_tag>&)’ 707 | struct image_read_settings< png_tag > : public image_read_settings_base | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /data/lin/ThirdParty/boost/boost_1_78_0/boost/gil/extension/io/png/tags.hpp:707:8: note: candidate expects 1 argument, 0 provided /data/lin/ThirdParty/boost/boost_1_78_0/boost/gil/extension/io/png/tags.hpp:707:8: note: candidate: ‘constexpr boost::gil::image_read_settings<boost::gil::png_tag>::image_read_settings(boost::gil::image_read_settings<boost::gil::png_tag>&&)’ /data/lin/ThirdParty/boost/boost_1_78_0/boost/gil/extension/io/png/tags.hpp:707:8: note: candidate expects 1 argument, 0 provided Only gcc 11 will fail with '-std=c++20', gcc9 and gcc 10 worked fine. I guess that gcc11 has implemented more c++20 features than gcc9 and gcc10. Since the boost project updates more quickly than gcc, I hope this issue might be fixed in the next boost version. Thanks, Qiang Ren

2 2

Dimension conversion for free?
by KL 08 Jan '22

08 Jan '22

1 0

TypeTraits
by Gero Peterhoff 27 Dec '21

27 Dec '21

Hello John, Some time ago I asked whether further type traits would be included in boost. Unfortunately that somehow fizzled out. Because based on this, many useful functions and classes can first be defined that behave correctly. But the problems are much deeper and I would like to show a solution here. 1) For some types there are feature-tesing-macros (e.g. __cpp_char8_t, __cpp_unicode_characters), but not for most. So this is incomplete. So we need this (plus the __cpp_lib-macros): - __cpp_char8/16/32_t, __cpp charw_t, __cpp_char_t - __cpp_int8/16/32/64/128_t - __cpp_float16/32/64/80/128_t, __cpp_float16b_t - __cpp_bool_t 2) Building on this, we can then query, e.g. struct has_float80: bool_constant < #if defined (__cpp_float80_t) true #else false #endif > {}; template <typename Type> struct is_float80: bool_constant < #if defined (__cpp_float80_t) is_same_v<Type, float80> #else false #endif > {}; This has to be done for all types. 3) Then we can further classify; plus is_X_v and concepts: character: template <typename Type> struct is_character: bool_constant < #if defined (__cpp_char32_t) is_same_v<Type, char32_t> || #elif defined (__cpp_char16_t) is_same_v<Type, char16_t> || #elif defined (__cpp_char8_t) is_same_v<Type, char8_t> || #elif defined (__cpp_charw_t) is_same_v<Type, wchar_t> || #endif is_same_v<Type, char> > {}; template <typename Type> struct is_unsigned_character: bool_constant < is_unsigned_v<Type> && character_v<Type> > {}; template <typename Type> is_signed_character: bool_constant < is_signed_v<Type> && character_v<Type> > {}; float: template <typename Type> struct is_floating_point: bool_constant < #if defined (__cpp_float128_t) is_same_v<Type, float128_t> || #elif defined (__cpp_float80_t) is_same_v<Type, float80_t> || #elif defined (__cpp_float64_t) is_same_v<Type, float64_t> || #elif defined (__cpp_float32_t) is_same_v<Type, float32_t> || #elif defined (__cpp_float16b_t) is_same_v<Type, float16b_t> || #elif defined (__cpp_float16_t) is_same_v<Type, float16_t> || #endif false > {}; integer: template <typename Type> struct is_unsigned_integer: bool_constant < #if defined (__cpp_int128_t) is_same_v<Type, uint128_t> || #elif defined (__cpp_int64_t) is_same_v<Type, uint64_t> || #elif defined (__cpp_int32_t) is_same_v<Type, uint32_t> || #elif defined (__cpp_int16_t) is_same_v<Type, uint16_t> || #elif defined (__cpp_int8_t) is_same_v<Type, uint8_t> || #endif false > {}; template <typename Type> struct is_signed_integer: bool_constant < #if defined (__cpp_int128_t) is_same_v<Type, int128_t> || #elif defined (__cpp_int64_t) is_same_v<Type, int64_t> || #elif defined (__cpp_int32_t) is_same_v<Type, int32_t> || #elif defined (__cpp_int16_t) is_same_v<Type, int16_t> || #elif defined (__cpp_int8_t) is_same_v<Type, int8_t> || #endif false > {}; template <typename Type> struct is_integer: bool_constant < is_unsigned_integer_v<Type> || is_signed_integer_v<Type> > {}; logic: template <typename Type> struct is_logic: bool_constant < is_same_v<Type, bool> > {}; With that we would have created the basics to be able to continue working properly at all. 4) 3 more steps to make things easier #define bitsof(ARG) (size_t(sizeof(ARG) * CHAR_BIT)) Like std::numbers with std::strings with various constantans namespace strings { constexpr static auto empty = ""; constexpr static auto nullptr = "nullptr"; constexpr static auto Void = "void"; constexpr static auto True = "true"; constexpr static auto False = "false"; constexpr static auto indeterminate = "indeterminate"; constexpr static auto overdeterminate = "overdeterminate"; constexpr static auto underdeterminate = "underdeterminate"; constexpr static auto bin = "bin"; constexpr static auto oct = "oct"; constexpr static auto dec = "dec"; constexpr static auto hex = "hex"; constexpr static auto literal_bin = "0b"; constexpr static auto literal_oct = "0o"; constexpr static auto literal_dec = "0d"; constexpr static auto literal_hex = "0x"; } and more and for streams so that you don't have to fumble with the flags namespace detail { using format_flags_t = typename std::ios_base::fmtflags; static inline constexpr format_flags_t defaultfloat = format_flags_t{}, hexfloat = std::ios_base::fixed | std::ios_base::scientific; inline format_flags_t get_flags (const std::ios_base & stream, const format_flags_t & fieldmask) noexcept { return stream.flags () & fieldmask; } } // detail inline bool is_boolalpha (const std::ios_base & stream) noexcept {return (stream.flags () & stream.boolalpha) == stream.boolalpha; } inline bool is_showbase (const std::ios_base & stream) noexcept {return (stream.flags () & stream.showbase) == stream.showbase; } inline bool is_showpoint (const std::ios_base & stream) noexcept {return (stream.flags () & stream.showpoint) == stream.showpoint; } inline bool is_skip (const std::ios_base & stream) noexcept {return (stream.flags () & stream.skipws) == stream.skipws; } inline bool is_uppercase (const std::ios_base & stream) noexcept {return (stream.flags () & stream.uppercase) == stream.uppercase; } inline bool is_lowercase (const std::ios_base & stream) noexcept {return! is_uppercase (stream); } inline bool is_float_bin (const std::ios_base & stream) noexcept {return false; } inline bool is_float_hex (const std::ios_base & stream) noexcept {return detail::get_flags (stream, stream.floatfield) == detail::hexfloat; } inline bool is_float_fixed (const std::ios_base & stream) noexcept {return detail::get_flags (stream, stream.floatfield) == stream.fixed; } inline bool is_float_default (const std::ios_base & stream) noexcept {return detail::get_flags (stream, stream.floatfield) == detail::defaultfloat; } inline bool is_float_scientific (const std::ios_base & stream) noexcept {return detail::get_flags (stream, stream.floatfield) == stream.scientific; } inline bool is_integer_bin (const std::ios_base & stream) noexcept {return false; } inline bool is_integer_oct (const std::ios_base & stream) noexcept {return detail::get_flags (stream, stream.basefield) == stream.oct; } inline bool is_integer_dec (const std::ios_base & stream) noexcept {return detail::get_flags (stream, stream.basefield) == stream.dec; } inline bool is_integer_hex (const std::ios_base & stream) noexcept {return detail::get_flags (stream, stream.basefield) == stream.hex; } 5) And now we can finally get correctly working functions, e.g. template <integer Type, unsigned_integer Bits> inline constexpr Type shl(const Type& arg, const Bits& bits) noexcept { using unsigned_type = make_unsigned_t<Type>; const type res {Type(arg << unsigned_type(bits))}; return (bits < bitsof(Type)) ? res : Type{0}; } template <integer Type, unsigned_integer Bits> inline constexpr Type shr(const Type& arg, const Bits& bits) noexcept { using unsigned_type = make_unsigned_t<Type>; const type ovl {is_signed_integer_v<Type> ? ((arg < Type{0})? Type(-1) : Type{0}) : Type{0}}, res {Type(arg >> unsigned_type(bits))}; return (bits < bitsof(Type)) ? res : ovl; } and classes, e.g. constexpr bool2/3/4 with template <> struct is_logic<bool4>: true_type {}; template <> struct is_logic<bool3>: true_type {}; template <> struct is_logic<bool2>: true_type {}; (I am happy to send it to you, because boost::tribool does not meet the requirements). PS: I could have used the days multi-array/multi-index; but that's done because all of these libs are not constexpr. Will these be updated again? thx Gero

1 0

Boost geometry: 3d difference and union?
by KL 13 Dec '21

13 Dec '21

2 1

Question on boost shared memory allocators
by Da Xu 08 Dec '21

08 Dec '21

Hi folks, got a couple of questions about using shared memory allocators. Please see below. I have the following code template <typename T> using CAP_Alloc = cached_adaptive_pool<T, segment_manager_t>; using CAP_Shmem_String = basic_string<char, std::char_traits<char>, CAP_Alloc<char> >; using CAP_Shmem_String_Alloc = CAP_Alloc<CAP_Shmem_String>; using CAP_Shmem_Void_Alloc = CAP_Alloc<void>; class MyDataBlock{ using pointer = CAP_Shmem_String_Alloc::pointer; pointer strData; float extraData; MyDataBlock(): strData(nullptr), extraData(0.0) {} MyDataBlock(const CAP_Shmem_Void_Alloc& alloc) { /* My question is how do I convert CAP_Shmem_Void_Alloc to type CAP_Shmem_String_Alloc to call allocate? And do I pass in the void allocator as a construction argument? Is there a difference between allocate and construct? */ } ~MyDataBlock() { /* To delete the memory, do I need to keep around a copy of the original allocator, so I can call deallocate or destroy? Or can that be derived or converted from somewhere, like calling strData->alloc() ? */ } } Any help would be greatly appreciated. Thank you.

1 0

[release] Boost 1.78.0
by Marshall Clow 08 Dec '21

08 Dec '21

Release 1.78.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 numerous enhancements and bug fixes for existing libraries. For details, including download links, see <http://www.boost.org/users/news/version_1.78.0> You can also download directly from: <https://boostorg.jfrog.io/artifactory/main/release/1.78.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.78.0 Release Candidate 1
by Marshall Clow 03 Dec '21

03 Dec '21

The first release candidates for the 1.78.0 release are now available at: <https://boostorg.jfrog.io/artifactory/main/release/1.78.0/source/> The SHA256 checksums are as follows: 94ced8b72956591c4775ae2207a9763d3600b30d9d7446562c552f0a14a63be7 boost_1_78_0_rc1.tar.gz f22143b5528e081123c3c5ed437e92f648fe69748e95fa6e2bd41484e2986cc3 boost_1_78_0_rc1.zip 090cefea470bca990fa3f3ed793d865389426915b37a2a3258524a7258f0790c boost_1_78_0_rc1.7z 8681f175d4bdb26c52222665793eef08490d7758529330f98d3b29dd0735bccc boost_1_78_0_rc1.tar.bz2 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

[Graph] Occasional crash when removing a vertex
by Anne van de Graaf 29 Nov '21

29 Nov '21

Hello all, 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 <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

1 0

assigning a "float128" variable with a regular "double" variable
by Jacques Mequin 27 Nov '21

27 Nov '21

I am a fresh new user ( I need to extend some EIGEN library feature by using your float128 ) How to assign a "float128" variable with a regular "double" variable ? With my source code in attachement double double_pi = 3.141592653589793 ; float128 float128_pi = 3.141592653589793Q ; produces the output that looks fine to me double_pi = 3.141592653589793e+00 float128_pi = 3.141592653589793000000000000000000e+00 but thestatement float128_pi = double_pi ; produces float128_pi = 3.141592653589793115997963468544185e+00 How to get 3.141592653589793000000000000000000e+00 also from an assigment ??? What am I doing wrong ? Thanks for any help Regards, Jacques

2 2

Fw: How to access global fixture class member
by Ming Cheng 21 Nov '21

21 Nov '21

________________________________ From: Ming Cheng Sent: Thursday, November 18, 2021 6:52 AM To: Boost-interest(a)lists.boost.org <Boost-interest(a)lists.boost.org> Subject: How to access global fixture class member Hi struct Myconfig{ int m_any; }; BOOST_GLOBAL_FIXTURE(Myconfig) How to access m_any?

1 1

boost units and single-precision floats
by Carel Combrink 19 Nov '21

19 Nov '21

Hi, I have aliases for radians and degrees that use float as the storage type. When I convert between these two units I see the assembly promote the values to doubles and then back to floats. How can I make sure that all operations and conversions stay in floats? PS: I would not be surprised if I have defined my aliases or/and my conversion functions incorrectly. My Code: === using radians_f = boost::units::quantity<boost::units::si::plane_angle, float>; using degrees_f = boost::units::quantity<boost::units::degree::plane_angle, float>; degrees_f to_degrees(const radians_f& angle) { return static_cast<degrees_f>(angle); } radians_f to_radians(const degrees_f& angle) { return static_cast<radians_f>(angle); } === >From compiler explorer I see the following assembly instructions: https://godbolt.org/z/Gnjr54dn6 cvtss2sd - Converts a single-precision floating-point value in the “convert-from” source operand to a double-precision floating-point value in the destination operand. mulsd - Multiplies the low double-precision floating-point value in the second source operand by the low double-precision floating-point value in the first source operand. cvtsd2ss - Converts a double-precision floating-point value in the “convert-from” source operand to a single-precision floating-point value Any help will be appreciated. Regards, Carel

1 0

Using Boost Compute with ArrayFire
by Muhammad Hassan Khan 17 Nov '21

17 Nov '21

Hi, I am trying to run a code which uses functions from both boost compute library and arrayfire library. I am getting the following errors when I try to build the code: Scanning dependencies of target hello [ 50%] Building CXX object CMakeFiles/hello.dir/hello.cpp.o In file included from /opt/arrayfire/include/CL/cl.h:32, from /usr/include/boost/compute/cl.hpp:19, from /usr/include/boost/compute/system.hpp:20, from /usr/include/boost/compute/algorithm/accumulate.hpp:17, from /usr/include/boost/compute/algorithm.hpp:18, from /usr/include/boost/compute.hpp:14, from /home/rcms/debruijn/arrayfire/hello.cpp:2: /opt/arrayfire/include/CL/cl_version.h:34:104: note: #pragma message: cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 220 (OpenCL 2.2) 34 | #pragma message("cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 220 (OpenCL 2.2)") | ^ [100%] Linking CXX executable hello /usr/bin/ld: CMakeFiles/hello.dir/hello.cpp.o: undefined reference to symbol 'clGetDeviceIDs@@OPENCL_1.0' /usr/bin/ld: /opt/arrayfire/lib64/libOpenCL.so.1: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/hello.dir/build.make:85: hello] Error 1 make[1]: *** [CMakeFiles/Makefile2:76: CMakeFiles/hello.dir/all] Error 2 make: *** [Makefile:84: all] Error 2 The code I am using is a very simple helloworld using functions from both libraries. #include <iostream> #include <boost/compute.hpp> #include <arrayfire.h> namespace compute = boost::compute; using namespace af; int main() { // Boost Compute Part // get the default device compute::device device = compute::system::default_device(); // print the device's name and platform std::cout << "hello from " << device.name(); std::cout << " (platform: " << device.platform().name() << ")" << std::endl; // Array Fire Part std::cout<< "ArrayFire Part:" << std::endl; af::setDevice(0); af::info(); return 0; } The CMakeList used to build the project is: cmake_minimum_required(VERSION 3.0) project(deBruijn_Graph) find_package(ArrayFire) add_executable(hello hello.cpp) target_link_libraries(hello ArrayFire::afopencl) I do not have a programming background. Please guide me on what I am doing wrong. Regards, Hassan <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

1 0

pgRouting use BGL
by Vicky Vergara 12 Nov '21

12 Nov '21

Hello, First of all, I want to congratulate you for the amazing job you are doing. I am the main developer of pgRouting, and the project is part of the OSGeo Foundation [2] community projects. pgRouting extends the PostGIS / PostgreSQL geospatial database to provide geospatial routing functionality. I would like pgRouting [1] to be added on the list of "Boost Graph Library Users" The Boost license is on the projects repository [3] and we document when a boost graph function is used for example in [4] [1] https://pgrouting.org/ [2] https://www.osgeo.org [3] https://github.com/pgRouting/pgrouting [4] https://docs.pgrouting.org/latest/en/pgr_aStar.html Thanks Vicky Vergara -- Georepublic UG (haftungsbeschränkt) Salzmannstraße 44, 81739 München, Germany Vicky Vergara Operations Research eMail: vicky(a)georepublic.de Web: https://georepublic.info Tel: +49 (089) 4161 7698-1 Fax: +49 (089) 4161 7698-9 Commercial register: Amtsgericht München, HRB 181428 CEO: Daniel Kastl

2 1

[release] Boost 1.7.0 beta 1 released
by Marshall Clow 11 Nov '21

11 Nov '21

Boost release 1.77.0 beta 1 is now available at: <https://boostorg.jfrog.io/artifactory/main/beta/1.78.0.beta1/source/> The SHA256 checksums are as follows: 7a3a025451dfa2923129214eef7d16b03c02310a353d02158a549f6caa4284b0 boost_1_78_0_b1.tar.bz2 c491b1dcb916195598aa6581d6708d57fcc750516641c22511c088d572de9c07 boost_1_78_0_b1.tar.gz 35e7a3b0eb412a3933e57c72ba96374eb7d88ff1f89dbec62a16d67ffea2105a boost_1_78_0_b1.7z e6b68feb2f63401c96ca9fe25e939b409189fbe526a6e784e4bd69832c8f09cb boost_1_78_0_b1.zip For details of what's in the release, see <https://www.boost.org/users/history/version_1_78_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

2 2

Boost.asio. Crash in Tutorial Timer.5, "Synchronizing handlers in multithreaded programs"
by Senthil Cheetancheri 11 Nov '21

11 Nov '21

Hi, I'm learning to use Boost.asio by going through the tutorials at [1]. However, the listing for "Synchronizing handlers in multithreaded programs" crashes on my Ubuntu. Source listing (about 70 lines) is at [2]. I have given my compilation steps, stack trace from gdb, and boost information below. Can you please advise how I can get this working right? [1] https://www.boost.org/doc/libs/1_77_0/doc/html/boost_asio/tutorial.html [2] https://www.boost.org/doc/libs/1_77_0/doc/html/boost_asio/tutorial/tuttimer… I compiled and ran as follows: $ g++ -g -o timer_5.1 timer_5.1.cpp -lpthread -lboost_thread $ ./timer_5.1 Timer 1: 0 Timer 2: 1 Timer 1: 2 Timer 2: 3 Timer 1: 4 Timer 2: 5 Timer 1: 6 Timer 2: 7 Timer 1: 8 Timer 2: 9 Segmentation fault (core dumped) The backtrace from gdb is: $ cat gdb_log.txt #0 0x00007ffff799f88b in ?? () from /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.65.1 #1 0x00007ffff79a0bd5 in ?? () from /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.65.1 #2 0x00007ffff7bbb6db in start_thread (arg=0x7ffff6851700) at pthread_create.c:463 #3 0x00007ffff711e71f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 I have the following boost library installed: $ sudo apt show libboost-all-dev Package: libboost-all-dev Version: 1.65.1.0ubuntu1 Priority: optional Section: universe/libdevel Source: boost-defaults Origin: Ubuntu Maintainer: Ubuntu Developers <ubuntu-devel-discuss(a)lists.ubuntu.com> Original-Maintainer: Debian Boost Team <pkg-boost-devel(a)lists.alioth.debian.org> Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 10.2 kB Depends: libboost-dev, libboost-tools-dev, libboost-atomic-dev, libboost-chrono-dev, libboost-container-dev, libboost-context-dev, libboost-coroutine-dev, libboost-date-time-dev, libboost-exception-dev, libboost-fiber-dev, libboost-filesystem-dev, libboost-graph-dev, libboost-graph-parallel-dev, libboost-iostreams-dev, libboost-locale-dev, libboost-log-dev, libboost-math-dev, libboost-mpi-dev, libboost-mpi-python-dev, libboost-numpy-dev, libboost-program-options-dev, libboost-python-dev, libboost-random-dev, libboost-regex-dev, libboost-serialization-dev, libboost-signals-dev, libboost-stacktrace-dev, libboost-system-dev, libboost-test-dev, libboost-thread-dev, libboost-timer-dev, libboost-type-erasure-dev, libboost-wave-dev Homepage: http://www.boost.org/ Download-Size: 2,340 B APT-Manual-Installed: yes . . . Thanks in advance. Thanks, Senthil.

2 1

[release] Boost 1.78.0 Beta 1 Release Candidate 1 is available
by Marshall Clow 09 Nov '21

09 Nov '21

The first release candidates for the 1.78.0 beta release are now available at: <https://boostorg.jfrog.io/ui/native/main/beta/1.78.0.beta1/source <https://boostorg.jfrog.io/ui/native/main/beta/1.78.0.beta1/source>> The SHA256 checksums are as follows: 7a3a025451dfa2923129214eef7d16b03c02310a353d02158a549f6caa4284b0 boost_1_78_0_b1_rc1.tar.bz2 c491b1dcb916195598aa6581d6708d57fcc750516641c22511c088d572de9c07 boost_1_78_0_b1_rc1.tar.gz 35e7a3b0eb412a3933e57c72ba96374eb7d88ff1f89dbec62a16d67ffea2105a boost_1_78_0_b1_rc1.7z e6b68feb2f63401c96ca9fe25e939b409189fbe526a6e784e4bd69832c8f09cb boost_1_78_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 Release managers

4 6

Boost libraries packaged for build2
by Boris Kolpackov 02 Nov '21

02 Nov '21

We have added support for the build2 build systems to 136 out of 145 Boost libraries and version 1.77.0 is now available from the cppget.org package repository. For details, see: https://build2.org/blog/build2-boost.xhtml

1 0