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

[interprocess] Determine size of managed_shared_memory
by Kai Benndorf 12 Oct '19

12 Oct '19

Hi all, I want to create a managed_shared_memory in exactly the size I needed. Therefore I do something like this: size = sizeof( common_managed_shared_memory ); size += sizeof( MyClassInSharedMem ); managed_shared_memory segment(create_only, "name", size ); MyClassInSharedMem allocates itself some memory by segment->allocate(). I added this also to the size, but get a boost::interprocess::bad_alloc exception on allocating this additional memory. Are there some magic bytes I forgot to add? Many thanks in advance Kai

3 2

boost::filtered_graph filtering on vertex color... if I only had a colormap
by Brian Davis 19 Jul '19

19 Jul '19

Lets say I have a graph g (of type graph_t) and a color map (boy I wish I had a colormap): typedef boost::property_map<graph_t, boost::vertex_color_t>::type color_map_t; or is it? auto indexmap = boost::get(boost::vertex_index, g); auto colors = boost::make_vector_property_map<boost::default_color_type>(indexmap); or maybe? auto indexmap = boost::get(boost::vertex_index, g); auto colors = boost::make_vector_property_map<boost::vertex_color_t>(indexmap); or possibly some goop found on the internet? boost::make_iterator_property_map(color_map.begin(), boost::get(boost::vertex_index, data_->g), color_map[0]) or other internet goop? typedef boost::property_map<GraphType, boost::vertex_color_t>::type color_map_t; color_map_t colorMap; boost::color_map(colorMap)) or other internet goop?? std::vector<int> colorMap(num_vertices(g), boost::white_color); so confused... (certainly not surprised why bgl is not a part of stl) Can someone help explain the various types and ways of specifying colormaps and the logic for each way and means? and a function (if I could get that far without VS syntax highlighter going bonkers and gobs of compiler errors.. you know the type): make_pretty(g, colormap ) which colors the graph colormap and a filter struct for boost::filtered_graph<Graph, EdgePredicate, VertexPredicate> (where I wonder why if I only want to filter vertices I have to set boost::keep_all for EdgePredicate... sigh... I know the answer... and also know how long it found me to find/figure out boost::keep_all - and if you are looking for boost::keep_all and found it here... your welcome ;-) ) and modifying (probably incorrectly) boost::filtered_graph example to: template <typename ColorMap> struct vertex_color_filter_eq { vertex_color_filter_eq() { } vertex_color_filter_eq(ColorMap colormap/*, boost::default_color_type c*/) : m_colormap(colormap)/*, m_c(c)*/ { } template <typename Vertex> bool operator()(const Vertex& v) const { return 0 < get(m_colormap, v); //return c < get(m_colormap, v); } ColorMap m_colormap; //boost::default_color_type m_c; }; auto indexmap = boost::get(boost::vertex_index, g); auto colors = boost::make_vector_property_map<boost::default_color_type>(indexmap); // some where here I would call make_pretty(g, colors) typedef property_map<graph_t, boost::vertex_color_t>::type ColorMap_t; vertex_color_filter<ColorMap_t> filter(colors); // boost::filtered_graph<graph_t, boost::keep_all, VertexPredicate> boost::filtered_graph<graph_t, boost::keep_all, vertex_color_filter> fg(g, filter); // Later say if I could get it compile and better if it compiled and worked I could move on and auto color = boost::red_color; typedef property_map<graph_t, boost::vertex_color_t>::type ColorMap_t; vertex_color_filter<ColorMap_t> filter(colors, color); boost::filtered_graph<graph_t, boost::keep_all, vertex_color_filter> fg(g, filter); Maybe if I color them yellow, I can then reach the wizard pull back the curtain and ask how to create a color map... If I only had a color map.

4 6

[test] Use-after-free with --log_sink=file, reported by gcc 7.2
by Avi Kivity 23 Jan '18

23 Jan '18

When static destructors are called, as the program exits, we destroy boost::unit_test::(anonymous namespace)::s_log_impl()::the_inst. This has a member vector, m_log_formatter_data. When destroying the second member, we run an ios_base_all_saver destructor, which attempts to restore a stream's format, however that stream has already been deallocated. Maybe that stream is in another static destructor, which was not ordered wrt. this one? Or maybe it was destroyed even earlier, when unit_test_main() exited. From ASan log, it loofs like the former. One static destructor is run from /usr/include/boost/test/impl/framework.ipp:459, while the other is run from /unit_test_log.ipp:122, so there is no ordering abong them. *** No errors detected ================================================================= ==1745==ERROR: AddressSanitizer: heap-use-after-free on address 0x6160000016a8 at pc 0x0000015f8892 bp 0x7ffecdb0b720 sp 0x7ffecdb0b710 READ of size 8 at 0x6160000016a8 thread T0 #0 0x15f8891 in std::ios_base::width(long) /usr/include/c++/7/bits/ios_base.h:723 #1 0x161dea0 in boost::io::ios_base_all_saver::restore() /usr/include/boost/io/ios_state.hpp:340 #2 0x161dda6 in boost::io::ios_base_all_saver::~ios_base_all_saver() /usr/include/boost/io/ios_state.hpp:336 #3 0x168a22e in void boost::checked_delete<boost::io::ios_base_all_saver>(boost::io::ios_base_all_saver*) /usr/include/boost/core/checked_delete.hpp:34 #4 0x171b7c5 in boost::detail::sp_counted_impl_p<boost::io::ios_base_all_saver>::dispose() /usr/include/boost/smart_ptr/detail/sp_counted_impl.hpp:78 #5 0x58b2c4 in boost::detail::sp_counted_base::release() /usr/include/boost/smart_ptr/detail/sp_counted_base_std_atomic.hpp:109 #6 0x58b51e in boost::detail::shared_count::~shared_count() /usr/include/boost/smart_ptr/detail/shared_count.hpp:419 #7 0x161eadc in boost::shared_ptr<boost::io::ios_base_all_saver>::~shared_ptr() /usr/include/boost/smart_ptr/shared_ptr.hpp:337 #8 0x1589a8a in ~unit_test_log_data_helper_impl /usr/include/boost/test/impl/unit_test_log.ipp:87 #9 0x15f0891 in _Destroy<boost::unit_test::(anonymous namespace)::unit_test_log_data_helper_impl> /usr/include/c++/7/bits/stl_construct.h:98 #10 0x15eb8ad in __destroy<boost::unit_test::(anonymous namespace)::unit_test_log_data_helper_impl*> /usr/include/c++/7/bits/stl_construct.h:108 #11 0x15e32c7 in _Destroy<boost::unit_test::(anonymous namespace)::unit_test_log_data_helper_impl*> /usr/include/c++/7/bits/stl_construct.h:137 #12 0x15cd317 in _Destroy<boost::unit_test::(anonymous namespace)::unit_test_log_data_helper_impl*, boost::unit_test::(anonymous namespace)::unit_test_log_data_helper_impl> /usr/include/c++/7/bits/stl_construct.h:206 #13 0x15c0de2 in ~vector /usr/include/c++/7/bits/stl_vector.h:434 #14 0x158aa72 in ~unit_test_log_impl /usr/include/boost/test/impl/unit_test_log.ipp:122 #15 0x7f6c2db90b57 in __run_exit_handlers (/lib64/libc.so.6+0x3bb57) #16 0x7f6c2db90ba9 in exit (/lib64/libc.so.6+0x3bba9) #17 0x7f6c2db76010 in __libc_start_main (/lib64/libc.so.6+0x21010) #18 0x4172e9 in _start (/home/avi/seastar/build/debug/tests/memcached/test_ascii_parser_g+0x4172e9) 0x6160000016a8 is located 296 bytes inside of 544-byte region [0x616000001580,0x6160000017a0) freed by thread T0 here: #0 0x7f6c32c9d6d8 in operator delete(void*, unsigned long) (/lib64/libasan.so.4+0xe16d8) #1 0x1717f1e in boost::detail::sp_counted_impl_pd<std::basic_ofstream<char, std::char_traits<char> >*, boost::detail::sp_ms_deleter<std::basic_ofstream<char, std::char_traits<char> > > >::~sp_counted_impl_pd() /usr/include/boost/smart_ptr/detail/sp_counted_impl.hpp:127 #2 0xc1563b in boost::detail::sp_counted_base::destroy() /usr/include/boost/smart_ptr/detail/sp_counted_base_std_atomic.hpp:89 #3 0x58b3e4 in boost::detail::sp_counted_base::weak_release() /usr/include/boost/smart_ptr/detail/sp_counted_base_std_atomic.hpp:123 #4 0x58b2f3 in boost::detail::sp_counted_base::release() /usr/include/boost/smart_ptr/detail/sp_counted_base_std_atomic.hpp:110 #5 0x58b51e in boost::detail::shared_count::~shared_count() /usr/include/boost/smart_ptr/detail/shared_count.hpp:419 #6 0x15fe350 in boost::shared_ptr<std::basic_ofstream<char, std::char_traits<char> > >::~shared_ptr() /usr/include/boost/smart_ptr/shared_ptr.hpp:337 #7 0x160f9ec in boost::unit_test::runtime_config::stream_holder::~stream_holder() /usr/include/boost/test/unit_test_parameters.hpp:96 #8 0x16fb8fc in std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder>::~pair() /usr/include/c++/7/bits/stl_pair.h:198 #9 0x16fb964 in void __gnu_cxx::new_allocator<std::_Rb_tree_node<std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder> > >::destroy<std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder> >(std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder>*) /usr/include/c++/7/ext/new_allocator.h:140 #10 0x16ef009 in void std::allocator_traits<std::allocator<std::_Rb_tree_node<std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder> > > >::destroy<std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder> >(std::allocator<std::_Rb_tree_node<std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder> > >&, std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder>*) /usr/include/c++/7/bits/alloc_traits.h:487 #11 0x16d81bc in std::_Rb_tree<boost::unit_test::output_format, std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder>, std::_Select1st<std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder> >, std::less<boost::unit_test::output_format>, std::allocator<std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder> > >::_M_destroy_node(std::_Rb_tree_node<std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder> >*) /usr/include/c++/7/bits/stl_tree.h:650 #12 0x16adac7 in std::_Rb_tree<boost::unit_test::output_format, std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder>, std::_Select1st<std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder> >, std::less<boost::unit_test::output_format>, std::allocator<std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder> > >::_M_drop_node(std::_Rb_tree_node<std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder> >*) /usr/include/c++/7/bits/stl_tree.h:658 #13 0x167e5af in std::_Rb_tree<boost::unit_test::output_format, std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder>, std::_Select1st<std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder> >, std::less<boost::unit_test::output_format>, std::allocator<std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder> > >::_M_erase(std::_Rb_tree_node<std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder> >*) /usr/include/c++/7/bits/stl_tree.h:1858 #14 0x1649760 in std::_Rb_tree<boost::unit_test::output_format, std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder>, std::_Select1st<std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder> >, std::less<boost::unit_test::output_format>, std::allocator<std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder> > >::~_Rb_tree() /usr/include/c++/7/bits/stl_tree.h:949 #15 0x160f988 in std::map<boost::unit_test::output_format, boost::unit_test::runtime_config::stream_holder, std::less<boost::unit_test::output_format>, std::allocator<std::pair<boost::unit_test::output_format const, boost::unit_test::runtime_config::stream_holder> > >::~map() /usr/include/c++/7/bits/stl_map.h:294 #16 0x161009b in boost::unit_test::framework::state::~state() /usr/include/boost/test/impl/framework.ipp:459 #17 0x7f6c2db90b57 in __run_exit_handlers (/lib64/libc.so.6+0x3bb57) previously allocated by thread T0 here: #0 0x7f6c32c9c158 in operator new(unsigned long) (/lib64/libasan.so.4+0xe0158) #1 0x169dfd6 in boost::detail::shared_count::shared_count<std::basic_ofstream<char, std::char_traits<char> >*, boost::detail::sp_ms_deleter<std::basic_ofstream<char, std::char_traits<char> > > >(std::basic_ofstream<char, std::char_traits<char> >*, boost::detail::sp_inplace_tag<boost::detail::sp_ms_deleter<std::basic_ofstream<char, std::char_traits<char> > > >) /usr/include/boost/smart_ptr/detail/shared_count.hpp:206 #2 0x16728db in boost::shared_ptr<std::basic_ofstream<char, std::char_traits<char> > >::shared_ptr<std::basic_ofstream<char, std::char_traits<char> >, boost::detail::sp_inplace_tag<boost::detail::sp_ms_deleter<std::basic_ofstream<char, std::char_traits<char> > > > >(std::basic_ofstream<char, std::char_traits<char> >*, boost::detail::sp_inplace_tag<boost::detail::sp_ms_deleter<std::basic_ofstream<char, std::char_traits<char> > > >) /usr/include/boost/smart_ptr/shared_ptr.hpp:372 #3 0x163c6e6 in boost::detail::sp_if_not_array<std::basic_ofstream<char, std::char_traits<char> > >::type boost::make_shared<std::basic_ofstream<char, std::char_traits<char> >>() /usr/include/boost/smart_ptr/make_shared_object.hpp:250 #4 0x15fe6ad in boost::unit_test::runtime_config::stream_holder::setup(boost::unit_test::basic_cstring<char const> const&) /usr/include/boost/test/unit_test_parameters.hpp:114 #5 0x155cd45 in boost::unit_test::framework::impl::setup_loggers() /usr/include/boost/test/impl/framework.ipp:861 #6 0x1561113 in boost::unit_test::framework::init(bool (*)(), int, char**) /usr/include/boost/test/impl/framework.ipp:1033 #7 0x1599d40 in boost::unit_test::unit_test_main(bool (*)(), int, char**) /usr/include/boost/test/impl/unit_test_main.ipp:189 #8 0x15c067f in main tests/test-utils.cc:84 #9 0x7f6c2db76009 in __libc_start_main (/lib64/libc.so.6+0x21009) SUMMARY: AddressSanitizer: heap-use-after-free /usr/include/c++/7/bits/ios_base.h:723 in std::ios_base::width(long) Shadow bytes around the buggy address: 0x0c2c7fff8280: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x0c2c7fff8290: 00 00 00 00 06 fa fa fa fa fa fa fa fa fa fa fa 0x0c2c7fff82a0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c2c7fff82b0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c2c7fff82c0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd =>0x0c2c7fff82d0: fd fd fd fd fd[fd]fd fd fd fd fd fd fd fd fd fd 0x0c2c7fff82e0: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c2c7fff82f0: fd fd fd fd fa fa fa fa fa fa fa fa fa fa fa fa 0x0c2c7fff8300: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa 0x0c2c7fff8310: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd 0x0c2c7fff8320: fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd fd Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user: f7 Container overflow: fc Array cookie: ac Intra object redzone: bb ASan internal: fe Left alloca redzone: ca Right alloca redzone: cb ==1745==ABORTING

2 5

Boost.Test: floating point comparison using absolute diference
by Georgios Sermaidis 30 Dec '17

30 Dec '17

Hi all, I am trying to find a way to make the boost unit test framework use an absolute difference for floating point comparison instead of the relative difference. I searched the documentation to try to find a suitable decorator but couldn’t find anything. Any help is much appreciated! #define BOOST_TEST_MODULE example #include <boost/test/included/unit_test.hpp> // boost::unit_test::tolerance uses relative difference and hence this test will pass; // is there anything I can use here to indicate absolute difference? BOOST_AUTO_TEST_CASE(my_test, * boost::unit_test::tolerance(0.1) ) { BOOST_TEST(10.1 == 10.3); }

2 4

Boost Unit Test: How to run only the enabled tests of a test suite?
by Maarten Anonymous 28 Dec '17

28 Dec '17

Hey, I'm looking for a way to only run the enabled unit tests of a tests suite. I have the following test suite: #define BOOST_TEST_MODULE decorator_predicate#include <boost/test/included/unit_test.hpp>namespace utf = boost::unit_test; BOOST_AUTO_TEST_SUITE(test_suite_1) BOOST_AUTO_TEST_CASE(bare_test){ BOOST_TEST(true);} BOOST_AUTO_TEST_CASE(enabled_test, * utf::enabled()){ BOOST_TEST(true);} BOOST_AUTO_TEST_CASE(disabled_test, * utf::disabled()){ BOOST_TEST(false);} BOOST_AUTO_TEST_SUITE_END() BOOST_AUTO_TEST_SUITE(test_suite_2) BOOST_AUTO_TEST_CASE(bare_test){ BOOST_TEST(true);} BOOST_AUTO_TEST_CASE(enabled_test, * utf::enabled()){ BOOST_TEST(true);} BOOST_AUTO_TEST_CASE(disabled_test, * utf::disabled()){ BOOST_TEST(false);} BOOST_AUTO_TEST_SUITE_END() Compilation and running: # Compile the test g++ predicate.cpp -o predicate # List all tests./predicate --list_content test_suite_1* bare_test* enabled_test* disabled_test test_suite_2* bare_test* enabled_test* disabled_test # Run the tests that are enabled by default./predicateRunning 4 test cases... *** No errors detected # Here, I would like to only run the enabled tests of test_suite_1.# Instead, all tests are run. Including the disabled../predicate -t test_suite_1Running 3 test cases... predicate.cpp(21): error: in "test_suite_1/disabled_test": check false has failed *** 1 failure is detected in the test module "decorator_predicate" How can I only run the enabled tests of tst_suite1? Only bare_test and enabled_test should be run. Thanks!

2 1

[test] Set fixture for all tests
by Florian Lindner 28 Dec '17

28 Dec '17

Hello, can I set a fixture for the entire test tree, so that it is called before and after each test case? BOOST_FIXTURE_TEST_CASE does that for a test suite, but how can I apply it to all tests e.g. the master test suite? Thanks, Florian

2 1

shared mutex ( read -write lock) for fibers
by Cristian Lorenzetto 23 Dec '17

23 Dec '17

is there a read-write lock for fibers? fibers mutex works also in a "normal" Thread when the scheduler is not installed?

1 0

[Units] Name a unit for output
by Santiago Ospina 20 Dec '17

20 Dec '17

Hello boost-users, I would like to know if there is an equivalent for giving a name and a symbol given a unit in boost::units (maybe scaled from another one). I know the example of naming base units, however, it would imply I'd have to create a system and a conversion for every unit I want to implement. I tried to write it directly from the scaled version, like this: template<> struct scale_minute<60, static_rational<1> > { static const long base = 60; typedef Detail::static_rational<1> exponent; typedef double value_type; static value_type value() { return(60); } static std::string name() { return("minute"); } static std::string symbol() { return("m"); } }; however, it is adding my scaled name plus my base name (say the base name is “s” which stands for seconds, then it would print “m” + "s”). Any idea how to overcome with that?

2 2

Re: [Boost-users] boost.msm and boost.mp11
by Didi JP BGF 19 Dec '17

19 Dec '17

Hi, there is this library that I use ... https://github.com/boost-experimental/sml ... Though I do not what the boost status is... On Tue, Dec 19, 2017 at 4:27 PM, Bogdan via Boost-users < boost-users(a)lists.boost.org> wrote: > Now that boost 1.66 includes mp11, is there a plan to upgrade the > meta-state > machine library (boost.msm) to something less macro dependent? > Thank you, > Bogdan > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > https://lists.boost.org/mailman/listinfo.cgi/boost-users > -- Didi JP BGF 15 Rue Albert Roussel 75017 Paris skype : bdidierjp

1 0

[release] Boost 1.66.0
by Daniel James 19 Dec '17

19 Dec '17

Release 1.66.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 N 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.66.0> You can also download directly from: <https://dl.bintray.com/boostorg/release/1.66.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 Vladimir Prus, Marshall Clow, Eric Niebler, Daniel James, Beman Dawes

2 1

boost.msm and boost.mp11
by Bogdan 19 Dec '17

19 Dec '17

Now that boost 1.66 includes mp11, is there a plan to upgrade the meta-state machine library (boost.msm) to something less macro dependent? Thank you, Bogdan

1 0

Adding C++/CLI code to my project makes app crash on startup
by Sergio Basurco 19 Dec '17

19 Dec '17

Hi, I'm using Boost 1.65.1 with Visual Studio 2015 (v140 compiler). Also, I'm using the following libs dynamically: boost_unit_test_framework boost_log boost_filesystem boost_thread boost_system boost_log_setup boost_chrono boost_date_time boost_regex And I want to add C++/CLI code which is built with /clr. This used to work with v110 and Boost 1.57. Now I'm getting this error just when launching the application. *0xc000007b* All binaries are 32bits. I'm also using the following define: BOOST_ALL_DYN_LINK Any idea on why this may happen? -- Saludos / Best regards, *Sergio Basurco* Coherent Synchro

7 12

Issue installing boost 1.65.1 on Centos 7
by Forum (io) 15 Dec '17

15 Dec '17

Dear All, I actually have a problem installing OpenEXR on a Centos 7. My problem is around ilmbase package and pyilmbas *and boost* as boost is required. And I have issue installing boost that I download from here https://gist.github.com/1duo/2d1d851f76f8297be264b52c1f31a2ab Before i decrive my problem let me explain where I looking around boost. When I compil ilambase, I got this error message: /$ ./compile --prefix=/opt/ilmbase2-2-0/ Both display this message/ / /checking for boost::python... no *** Could not run the boost::python test program, checking why... *** The test program could not be compiled. Is boost::python installed? *** Check that the cflags (below) includes the boost::python include directory *** *** Flags used by the test: *** cflags: -g -O2 -I/usr/include/python2.7 -g -O2 -I/usr/include/python2.7 *** ldflags: -L/opt/ilmbase-2-2-0/lib -L/usr/lib64 -L/opt/ilmbase-2-2-0/lib -L/usr/lib64 *** *** You can also run configure with --disable-boostpythontest to skip this test. configure: error: Could not compile boost::python test program. /Someone suggested me to install boost as a share. I downloaded the boost 1.65.1 an untar it into /root/install-package/ Then I tried the following command: cd /root/install-package/boost_1_65_1 sudo ./bootstrap.sh --prefix=/opt/boost_1.65.1 sudo ./b2 address-model=64 variant=release threading=multi link=shared Note that my first attend was with that command cd /root/install-package/boost_1_65_1 sudo ./bootstrap.sh --prefix=/opt/boost_1.65.1 sudo ./b2 And boost was install in /opt/boost_1.65.1 But since I use the command sudo ./b2 address-model=64 variant=release threading=multi link=shared No folder was created in /opt/boost_1.65.1 and at the of the process, this was displayed The following directory should be added to compiler include paths: /root/install-package/boost_1_65_1 The following directory should be added to linker library paths: /root/install-package/boost_1_65_1/stage/lib Then it's look like it boost has been installed in the same folder, where it has been extracted *The my question, what did I do wrong and how can I install boost in /opt/boost_1.65.1 and make it share for ilmbase and OpenEXR? * Feel you free to ask addintionnal question if I missed to provide you Many thank for your help Cheers Pierre* *

2 1

Named pipe available to other processes (boost::process)
by Mike Gibson 15 Dec '17

15 Dec '17

It seems that boost::process::basic_pipe::basic_pipe(const std::string& name) on posix creates a fifo using mkfifo, opens it and then unlinks it. I imagine there's a good reason for the unlink step in some situations, but it's causing me issues. I would like to use the fifo later with a non-boost::process started process, so by the time I get around to starting the second process, it can't access the fifo. Is there any workaround for this?

1 0

Re: [Boost-users] [boost] [release] Boost 1.66.0 Release Candidate 2
by Marcel Raad 15 Dec '17

15 Dec '17

> -----Original Message----- > From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Olaf van > der Spek via Boost > Sent: Donnerstag, 14. Dezember 2017 16:11 > To: boost(a)lists.boost.org > Cc: Olaf van der Spek <ml(a)vdspek.org>; boost-users(a)lists.boost.org > Subject: Re: [boost] [release] Boost 1.66.0 Release Candidate 2 > > On Thu, Dec 14, 2017 at 2:03 PM, Daniel James via Boost > <boost(a)lists.boost.org> 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. > > "Info: Boost.Config is older than your compiler version - probably > nothing bad will happen - but you may wish to look for an update Boost > version. Define BOOST_CONFIG_SUPPRESS_OUTDATED_MESSAGE to > suppress > this message." > generates so much noise, could it be suppressed for 15.5 if the > updates to config can't be included? The message itself tells a trivial way to suppress it - so I don't see any problem? Marcel

1 0

Re: [Boost-users] [boost] [release] Boost 1.66.0 Release Candidate 2
by Marcel Raad 15 Dec '17

15 Dec '17

Hi, > -----Original Message----- > From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Olaf van > der Spek via Boost > Sent: Donnerstag, 14. Dezember 2017 16:02 > To: boost(a)lists.boost.org > Cc: Olaf van der Spek <ml(a)vdspek.org>; boost-users(a)lists.boost.org > Subject: Re: [boost] [release] Boost 1.66.0 Release Candidate 2 > > On Thu, Dec 14, 2017 at 2:03 PM, Daniel James via Boost > <boost(a)lists.boost.org> wrote: > > The second release candidates for the 1.66.0 release are now available at: > > > > <https://dl.bintray.com/boostorg/prerelease/> > > Repository path missing or not specified. the correct path seems to be https://dl.bintray.com/boostorg/release/1.66.0/source/ Marcel

3 2

ASIO and windows registered IO
by Tore Halvorsen 15 Dec '17

15 Dec '17

Hi, Have anyone tried to use the windows registered IO functionality with ASIO?

2 1

[release] Boost 1.66.0 Release Candidate 2
by Daniel James 14 Dec '17

14 Dec '17

The second release candidates for the 1.66.0 release are now available at: <https://dl.bintray.com/boostorg/prerelease/> The in progress release notes are: <http://www.boost.org/users/history/in_progress.html> Library documentation is available at: <http://www.boost.org/doc/libs/1_66_0/> The SHA256 checksums are as follows: 596389389c005814ecb2a6b64c31dccd2c3e6fbc5a802b4dfada999ae5844628 boost_1_66_0_rc2.7z 5721818253e6a0989583192f96782c4a98eb6204965316df9f5ad75819225ca9 boost_1_66_0_rc2.tar.bz2 bd0df411efd9a585e5a2212275f8762079fed8842264954675a4fddc46cfcf60 boost_1_66_0_rc2.tar.gz e1c55ebb00886c1a96528e4024be98a38b815115f62ecfe878fcf587ba715aad boost_1_66_0_rc2.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.

2 1

Re: [Boost-users] [boost] [release] Boost 1.66.0 Release Candidate 2
by Daniel James 14 Dec '17

14 Dec '17

On 14 December 2017 at 15:02, Olaf van der Spek <ml(a)vdspek.org> wrote: > On Thu, Dec 14, 2017 at 2:03 PM, Daniel James via Boost > <boost(a)lists.boost.org> wrote: >> The second release candidates for the 1.66.0 release are now available at: >> >> <https://dl.bintray.com/boostorg/prerelease/> > > Repository path missing or not specified. Sorry, should be: https://dl.bintray.com/boostorg/release/1.66.0/source/

1 0

Newbie: BGL & planar graphs
by ano kato 13 Dec '17

13 Dec '17

Hello everyone! I am using BGL to test for the planarity of drawings of graphs. The coordinates are hardcoded into the source code. Here's what the graph should look like: <https://i.imgur.com/UGA0mRB.png>. This definitely isn't planar and yet is_straight_line_drawing() returns 1! I'm quite confused. Am I doing something wrong? Thank you to anyone who replies. #include <iostream> #include <vector> #include <boost/graph/adjacency_list.hpp> #include <boost/property_map/property_map.hpp> #include <boost/graph/is_straight_line_drawing.hpp> using namespace boost; typedef struct { size_t x,y; } coord_t; int main(void) { typedef adjacency_list<vecS, vecS, undirectedS, property<vertex_index_t, int> > graph; graph Moser(7); add_edge(0,1,Moser); add_edge(0,6,Moser); add_edge(0,4,Moser); add_edge(1,6,Moser); add_edge(1,2,Moser); add_edge(2,6,Moser); add_edge(2,5,Moser); add_edge(2,3,Moser); add_edge(3,4,Moser); add_edge(4,5,Moser); graph G(Moser); int k = num_vertices(G); typedef std::vector<coord_t> cvec; typedef boost::iterator_property_map <cvec::iterator, property_map<graph, vertex_index_t>::type // ? > foo_t; cvec v(num_vertices(G)); foo_t drawing(v.begin(), get(vertex_index, G)); coord_t x[k]; x[0].x = 20; x[0].y = 10; x[1].x = 50; x[1].y = 10; x[2].x = 58; x[2].y = 52; x[3].x = 00; x[3].y = 30; x[4].x = 35; x[4].y = 50; x[5].x = 12; x[5].y = 51; x[6].x = 70; x[6].y = 30; graph_traits<graph>::vertex_iterator vi, vi_end; for(boost::tie(vi, vi_end) = vertices(G); vi != vi_end; ++vi) put(drawing, *vi, x[*vi]); if(is_straight_line_drawing(G,drawing)) std::cout << "This is a straight line planar drawing!" << std::endl; return 0; }

2 2

(Newbie) Embedded programming, memory pools, and allocate_shared()
by Steven Boswell II 13 Dec '17

13 Dec '17

I apologize for bothering the mailing-list with this newbie question, but after searching the Net for several days, I still can't find the answers I'm looking for. I am considering using Boost for a project I'm doing on an embedded system.I can't seem to find a lot of discussion on the particulars of Boost in embedded systems, just a few here and there.The biggest relevant limitation in embedded programming is on dynamic memory allocation -- the usual pattern is to allocate all necessary memory in "startup" phases, e.g. launching the program, loading the next playing-field in a game application, etc. I believe I can do what I want with allocate_shared() and fixed-size memory pools.The first big issue I have is trying to figure out the size of the objects that'll be allocated from the pool.I don't want to just allocate a raw block of memory; I want to allocate a block with space for a certain number of objects of a homogeneous type.But an object_pool for a type T doesn't accurately reflect what allocate_shared() is going to try to create.From much digging around, it looks like it's actually creating a subclass of boost::detail::sp_counted_base, e.g. boost::detail::sp_counted_impl_pd<P,D>, boost::detail::sp_counted_impl_pda<P,D,A>, etc.It seems like I'm not supposed to refer to that class directly, but I don't know how else to get the size of individual objects for my pool-allocator.Also, navigating all the template-parameters needed by these classes is proving to be mind-twisting. Probably just because I'm seeing it for the first time. Another example of where I need to track down the implementation class is with async-operation handlers in Boost::ASIO, e.g. completion handlers for socket's async_read_some(), generic handlers passed to io_service::post(), and so on. In the case of socket::async_read_some(), there's an example in boost/doc/html/boost_asio/example/cpp03/allocation/server.cpp which shows how to allocate completion-handlers from a pool, but not how to get the size of the necessary completion-handler class. It appears the class is boost::asio::detail::reactive_socket_recv_op<>. Again, this doesn't seem to be a public class, nor can I find a nice public typedef for it. Can anyone advise me on how to use Boost in this way?All of the Boost memory-pools I've seen so far either just allocate chunks of raw memory, or they allocate non-shared variants of objects.A memory-pool with a given number of spaces for the final object type seems like a defensible, traditional solution, but it doesn't seem that Boost makes that easy.Am I way off base here? Thanks for any help. -Steven

3 12

[thread] clock_gettime warning on OS X
by James Walker 13 Dec '17

13 Dec '17

I'm getting a warning in the file boost/thread/pthread/timespec.hpp pointing out that clock_gettime is only available on macOS 10.12 and later. This code is being compiled on macOS 10.13, but should be compatible with macOS versions back to 10.7. How can I fix it? Maybe change the setting of BOOST_THREAD_USEFIXES_TIMESPEC, which I don't see any documentation for?

1 0

[SmartPtr] local_weak_ptr?
by Rob Conde 11 Dec '17

11 Dec '17

How are boost::local_shared_ptr and boost::weak_ptr intended to be used together? I expected a local_weak_ptr, but it's not there so I'm wondering how you would (correctly) use local_shared_ptr and weak_ptr, or if you need local_weak_ptr and this is just still on the TODO list? Thanks, Rob Conde

2 2

boost::container::string: ambiguous overload for 'operator!='
by niXman 10 Dec '17

10 Dec '17

Hi, using gcc-7.2 in C++17 mode and boost-1.65.1 I get the "ambiguous overload for 'operator!='" error: test here: http://coliru.stacked-crooked.com/a/3fd8fb94c0d1aec2 the same error for 'operator==' -- Regards, niXman ___________________________________________________ Work for Bitcoins ___________________________________________________ Dual-target(32 & 64-bit) MinGW-W64 compilers for 32 and 64-bit Windows: https://sf.net/p/mingw-w64/

2 1

[release] Boost 1.66.0 Release Candidate 1
by Daniel James 09 Dec '17

09 Dec '17

The release candidates for the 1.66.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.66.0/source/> The in progress release notes are: <http://www.boost.org/users/history/in_progress.html> Library documentation is available at: <http://www.boost.org/doc/libs/1_66_0/> The SHA256 checksums are as follows: c9d29486dd12f19d321da65eb5f0a157ec0f0edfd4701ade48c644310c8f0676 boost_1_66_0_rc1.7z 6232f7e7873b2d1f112fb62c726f7066e9a7e0643ed2aac7d31d20bf5749fbc0 boost_1_66_0_rc1.tar.bz2 30ad6d1c7380d6e6a87ce1bc54388ab957de67a2e8fa44dd3c106eafad0f6ac2 boost_1_66_0_rc1.tar.gz cd2c64f243c89e04329e94f3b803f0744171b44fee7a8b4e3256b3a625dcbd1c boost_1_66_0_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.

2 2