March 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

Weird compilation error when using boost::geometry
by 邓尧 16 Nov '17

16 Nov '17

Hi, I have implemented my own "point" as specified by the point concept http://www.boost.org/doc/libs/1_59_0/libs/geometry/doc/html/geometry/refere… When I use it along with boost::geometry::model::polygon/multi_polygon, GCC refuses to compile, tested on GCC 4.9/5.2. What's even more weird is that CLANG 3.6 would happy accept my code. BTW, the Point implementation is part of a large project, it difficult to replace it with boost::geometry::model::point. Here is my code: Point.hpp > #ifndef RAPTOR_POINT_HPP_INCLUDED_ > > #define RAPTOR_POINT_HPP_INCLUDED_ > > >> #include <boost/mpl/int.hpp> > > #include <boost/geometry/core/access.hpp> > > #include <boost/geometry/core/cs.hpp> > > #include <boost/geometry/core/coordinate_type.hpp> > > #include <boost/geometry/core/coordinate_system.hpp> > > #include <boost/geometry/core/coordinate_dimension.hpp> > > #include <boost/geometry/geometries/polygon.hpp> > > #include <boost/geometry/multi/geometries/multi_polygon.hpp> > > >> namespace raptor { > > >> template<typename T, int tDimension = 2> > > class Point { > > public: > > Point() = default; > > >> Point(T a, T b) { > > data[0] = a; > > data[1] = b; > > } > > >> Point(T a, T b, T c) { > > data[0] = a; > > data[1] = b; > > data[2] = c; > > } > > >> T& operator [] (long index) { > > return data[index]; > > } > > >> const T& operator [] (long index) const { > > return data[index]; > > } > > >> private: > > T data[tDimension]; > > }; > > >> using CubicPoint = Point<long, 3>; > > using PlanarPoint = Point<long>; > > using SphericalPoint = Point<double>; > > >> template<typename T> > > using Polygon = boost::geometry::model::polygon<T>; > > >> template<typename T> > > using PolySet = boost::geometry::model::multi_polygon<Polygon<T>>; > > >> } // namespace raptor > > >> namespace boost { namespace geometry { namespace traits { > > >> template<typename Type, std::size_t tDimension> > > struct tag<::raptor::Point<Type, tDimension>> { > > typedef point_tag type; > > }; > > >> template<typename Type, std::size_t tDimension> > > struct coordinate_type<::raptor::Point<Type, tDimension>> { > > typedef Type type; > > }; > > >> template<typename Type, std::size_t tDimension> > > struct coordinate_system<::raptor::Point<Type, tDimension>> { > > typedef boost::geometry::cs::cartesian type; > > }; > > >> template<typename Type, std::size_t tDimension> > > struct dimension<::raptor::Point<Type, tDimension>> > > : public boost::mpl::int_<tDimension> { > > // EMPTY > > }; > > >> template<typename Type, std::size_t tDimension, std::size_t tIndex> > > struct access<::raptor::Point<Type, tDimension>, tIndex> { > > static Type get(const ::raptor::Point<Type, tDimension>& p) { > > return p[tIndex]; > > } > > >> static void set(::raptor::Point<Type, tDimension>& p, > > const Type& value) { > > p[tIndex] = value; > > } > > }; > > >> }}} // namespace boost::geometry::traits > > >> #endif // RAPTOR_POINT_HPP_INCLUDED_ > > A real simple main.cpp: > #include "Point.hpp" > > >> int main() { > > raptor::Polygon<raptor::SphericalPoint> pl; > > raptor::PolySet<raptor::SphericalPoint> set; > > return sizeof(pl) + sizeof(set); > > } > > > GCC compilation error: g++ main.cpp -std=c++14 > In file included from /usr/include/boost/geometry/core/access.hpp:20:0, from Point.hpp:5, from main.cpp:1: /usr/include/boost/geometry/core/point_type.hpp: In instantiation of > 'struct boost::geometry::traits::point_type<raptor::Point<double> >': /usr/include/boost/geometry/core/point_type.hpp:66:17: required from > 'struct boost::geometry::core_dispatch::point_type<void, > raptor::Point<double> >' /usr/include/boost/geometry/core/coordinate_type.hpp:58:62: required from > 'struct boost::geometry::core_dispatch::coordinate_type<void, > raptor::Point<double> >' /usr/include/boost/geometry/core/coordinate_type.hpp:92:25: required from > 'struct boost::geometry::coordinate_type<raptor::Point<double> >' /usr/include/boost/geometry/geometries/concepts/point_concept.hpp:90:54: > required from 'class boost::geometry::concept::Point<raptor::Point<double> > >' /usr/include/boost/concept/detail/has_constraints.hpp:32:62: required by > substitution of 'template<class Model> boost::concepts::detail::yes > boost::concepts::detail::has_constraints_(Model*, > boost::concepts::detail::wrap_constraints<Model, (& Model:: constraints)>*) > [with Model = boost::geometry::concept::Point<raptor::Point<double> >]' /usr/include/boost/concept/detail/has_constraints.hpp:42:5: required from > 'const bool > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >::value' /usr/include/boost/concept/detail/has_constraints.hpp:45:31: required > from 'struct > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >' /usr/include/boost/mpl/if.hpp:67:11: required from 'struct > boost::mpl::if_<boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >, > boost::concepts::constraint<boost::geometry::concept::Point<raptor::Point<double> > > >, boost::concepts::requirement<boost::concepts::failed************ > boost::geometry::concept::Point<raptor::Point<double> >::************> >' /usr/include/boost/concept/detail/general.hpp:50:8: required from 'struct > boost::concepts::requirement_<void > (*)(boost::geometry::concept::Point<raptor::Point<double> >)>' /usr/include/boost/geometry/geometries/ring.hpp:60:5: required from > 'class boost::geometry::model::polygon<raptor::Point<double>, true, true, > std::vector, std::vector, std::allocator, std::allocator>' main.cpp:4:42: required from here /usr/include/boost/geometry/core/point_type.hpp:45:5: error: no matching > function for call to 'assertion_failed(mpl_::failed************ > (boost::geometry::traits::point_type<raptor::Point<double> > >::NOT_IMPLEMENTED_FOR_THIS_POINT_TYPE::************)(mpl_::assert_::types<raptor::Point<double>, > mpl_::na, mpl_::na, mpl_::na>))' BOOST_MPL_ASSERT_MSG ^ /usr/include/boost/mpl/assert.hpp:82:5: note: candidate: template<bool C> > int mpl_::assertion_failed(typename mpl_::assert<C>::type) int assertion_failed( typename assert<C>::type ); ^ /usr/include/boost/mpl/assert.hpp:82:5: note: template argument > deduction/substitution failed: /usr/include/boost/geometry/core/point_type.hpp:45:5: note: cannot > convert > 'boost::geometry::traits::point_type<Geometry>::NOT_IMPLEMENTED_FOR_THIS_POINT_TYPE48::assert_arg<raptor::Point<double> > >()' (type 'mpl_::failed************ > (boost::geometry::traits::point_type<raptor::Point<double> > >::NOT_IMPLEMENTED_FOR_THIS_POINT_TYPE::************)(mpl_::assert_::types<raptor::Point<double>, > mpl_::na, mpl_::na, mpl_::na>)') to type 'mpl_::assert<false>::type {aka > mpl_::assert<false>}' BOOST_MPL_ASSERT_MSG ^ In file included from > /usr/include/boost/geometry/core/coordinate_type.hpp:21:0, from /usr/include/boost/geometry/core/access.hpp:24, from Point.hpp:5, from main.cpp:1: /usr/include/boost/geometry/core/point_type.hpp: In instantiation of > 'struct boost::geometry::core_dispatch::point_type<void, > raptor::Point<double> >': /usr/include/boost/geometry/core/coordinate_type.hpp:58:62: required from > 'struct boost::geometry::core_dispatch::coordinate_type<void, > raptor::Point<double> >' /usr/include/boost/geometry/core/coordinate_type.hpp:92:25: required from > 'struct boost::geometry::coordinate_type<raptor::Point<double> >' /usr/include/boost/geometry/geometries/concepts/point_concept.hpp:90:54: > required from 'class boost::geometry::concept::Point<raptor::Point<double> > >' /usr/include/boost/concept/detail/has_constraints.hpp:32:62: required by > substitution of 'template<class Model> boost::concepts::detail::yes > boost::concepts::detail::has_constraints_(Model*, > boost::concepts::detail::wrap_constraints<Model, (& Model:: constraints)>*) > [with Model = boost::geometry::concept::Point<raptor::Point<double> >]' /usr/include/boost/concept/detail/has_constraints.hpp:42:5: required from > 'const bool > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >::value' /usr/include/boost/concept/detail/has_constraints.hpp:45:31: required > from 'struct > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >' /usr/include/boost/mpl/if.hpp:67:11: required from 'struct > boost::mpl::if_<boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >, > boost::concepts::constraint<boost::geometry::concept::Point<raptor::Point<double> > > >, boost::concepts::requirement<boost::concepts::failed************ > boost::geometry::concept::Point<raptor::Point<double> >::************> >' /usr/include/boost/concept/detail/general.hpp:50:8: required from 'struct > boost::concepts::requirement_<void > (*)(boost::geometry::concept::Point<raptor::Point<double> >)>' /usr/include/boost/geometry/geometries/ring.hpp:60:5: required from > 'class boost::geometry::model::polygon<raptor::Point<double>, true, true, > std::vector, std::vector, std::allocator, std::allocator>' main.cpp:4:42: required from here /usr/include/boost/geometry/core/point_type.hpp:66:17: error: no type named > 'type' in 'struct boost::geometry::traits::point_type<raptor::Point<double> > >' >::type type; ^ In file included from > /usr/include/boost/geometry/geometries/polygon.hpp:26:0, from Point.hpp:10, from main.cpp:1: /usr/include/boost/geometry/geometries/concepts/point_concept.hpp: In > instantiation of 'class > boost::geometry::concept::Point<raptor::Point<double> >': /usr/include/boost/concept/detail/has_constraints.hpp:32:62: required by > substitution of 'template<class Model> boost::concepts::detail::yes > boost::concepts::detail::has_constraints_(Model*, > boost::concepts::detail::wrap_constraints<Model, (& Model:: constraints)>*) > [with Model = boost::geometry::concept::Point<raptor::Point<double> >]' /usr/include/boost/concept/detail/has_constraints.hpp:42:5: required from > 'const bool > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >::value' /usr/include/boost/concept/detail/has_constraints.hpp:45:31: required > from 'struct > boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >' /usr/include/boost/mpl/if.hpp:67:11: required from 'struct > boost::mpl::if_<boost::concepts::not_satisfied<boost::geometry::concept::Point<raptor::Point<double> > > >, > boost::concepts::constraint<boost::geometry::concept::Point<raptor::Point<double> > > >, boost::concepts::requirement<boost::concepts::failed************ > boost::geometry::concept::Point<raptor::Point<double> >::************> >' /usr/include/boost/concept/detail/general.hpp:50:8: required from 'struct > boost::concepts::requirement_<void > (*)(boost::geometry::concept::Point<raptor::Point<double> >)>' /usr/include/boost/geometry/geometries/ring.hpp:60:5: required from > 'class boost::geometry::model::polygon<raptor::Point<double>, true, true, > std::vector, std::vector, std::allocator, std::allocator>' main.cpp:4:42: required from here /usr/include/boost/geometry/geometries/concepts/point_concept.hpp:93:10: > error: 'value' is not a member of > 'boost::geometry::dimension<raptor::Point<double> >' enum { ccount = dimension<Geometry>::value }; ^ Where is the problem ? or it's a GCC bug ? Thanks

3 4

NEWBIE: Undefined references: How do I find the library that resolves an undefined reference
by JENNINGS, LYNN M NH-03 USAF AFMC 517 SMXS/MXDPB 30 May '17

30 May '17

NEWBIE question: Undefined references: How do I find the library that resolves an undefined reference. For example, the output for the gcc linker running in MinGW shows: C:/boost/boost/asio/detail/impl/winsock_init.ipp:39: Undefined reference to `WSAStartup@8' I have googled the documentation a number of ways, but I cannot find the library that will resolve this error. I am sure that this is a common problem. Please point me to the documentation so I can fix this and the undefined references. Thanks!

4 3

[Range, Phoenix] What am I missing...
by Robert Jones 25 Apr '17

25 Apr '17

Hi Folks Can anyone explain the output of this program... #include <iostream> #include <boost/range/algorithm/copy.hpp> #include <boost/range/counting_range.hpp> #include <boost/range/adaptor/reversed.hpp> #include <boost/range/adaptor/transformed.hpp> #include <boost/phoenix/bind/bind_function.hpp> #include <boost/phoenix/core/argument.hpp> int f( int i ) { return i * 2; } int main( ) { using boost::adaptors::reversed; using boost::adaptors::transformed; using boost::counting_range; using boost::copy; using boost::phoenix::arg_names::_1; copy( counting_range( 1, 5 ) | reversed | transformed( f ), std::ostream_iterator<int>( std::cout, " " ) ); std::cout << std::endl; copy( counting_range( 1, 5 ) | reversed | transformed( bind( f, _1 ) ), std::ostream_iterator<int>( std::cout, " " ) ); std::cout << std::endl; } Which is... 8 6 4 2 1768406272 1768406272 1768406272 1768406272 I'm using Gcc 4.6.2 & Boost 1.53 Thx All.

3 4

Re: [Boost-users] Issue with Boost.Test using Oracle Developer Studio 12.5
by Leo Carreon 16 Apr '17

16 Apr '17

I have not received any response on this mail therefore I have decided to report a bug via tracs. The tracs ticket# 12877. From: Leo Carreon Sent: Tuesday, February 28, 2017 6:25 PM To: Boost Users Mailing List Subject: Issue with Boost.Test using Oracle Developer Studio 12.5 Hi, This is a continuation of the issues I’ve encountered with Boost 1.63.0 using Developer Studio 12.5. I’m assuming that even with the Boost 1.63.0 build issues that libraries unaffected by the build issues are usable. Therefore, I have attempted to build one of my small projects in both C++11 and C++14 modes. The builds of this small project failed with the following error message: "/opt/boost1.63.0/include/boost/test/unit_test_log.hpp", line 218: Error: boost::unit_test::unit_test_log_t::test_unit_skipped hides the virtual function boost::unit_test::test_observer::test_unit_skipped(const boost::unit_test::test_unit&). This error was encountered compiling a source file containing the following: #define BOOST_TEST_MODULE TestImport #include <boost/test/unit_test.hpp> Is this a Boost.Test issue or is it a Developer Studio 12.5 issue? If it is a Boost.Test issue, how do I resolve it? Kind regards, Leo

2 1

[build] Unexpected static libraries in 1.63
by Gavin Lambert 16 Apr '17

16 Apr '17

I've recently rebuilt Boost 1.63 locally for both Windows and Linux, requesting dynamic libraries only (link=dynamic). However several libraries are still being built in both static and dynamic forms: - chrono - system - timer - unit_test_framework Additionally some libraries are being built only in static forms: - exception - test_exec_monitor I assume the latter is intentional, as presumably some libraries can only work as static libraries. Is the former intentional or a bug? It seems like a bug. Or do these contain symbols that the dynamic libraries do not?

4 6

Re: [Boost-users] [Boost.Test] Using intel MKL instead of ACML with the boost testing framework
by anandram sundar 16 Apr '17

16 Apr '17

Update: This doesn’t seem to have anything to do with MKL. Just linking with all the boost libraries is enough to cause this. I was able to repro this with just a few files. I am fairly certain this is because of some issue with linking incorrect libraries. Please let me know. I realize that I don’t need all these libraries for the simple test cases I have written. My g++ version is 4.4.6 Boost version 1.63 File1: // cat mklmain.cpp #define BOOST_ALL_DYN_LINK #define BOOST_TEST_MAIN #include <boost/test/included/unit_test.hpp> File2: // cat mkl1.cpp #include <boost/test/unit_test.hpp> #include "logging-helper.h" BOOST_FIXTURE_TEST_SUITE(mkltest1, Fixture) BOOST_AUTO_TEST_CASE(math_test_functions1) { BOOST_LOG_SEV(lg, trace) << "Starting test case for mkl test 1"; float dot = 3; BOOST_TEST(dot == 3); BOOST_LOG_SEV(lg, trace) << "Ending test case for mkl test 1"; } BOOST_AUTO_TEST_SUITE_END() File3: // cat mkl2.cpp #include <boost/test/unit_test.hpp> #include "logging-helper.h" BOOST_FIXTURE_TEST_SUITE(mkltest2, Fixture) BOOST_AUTO_TEST_CASE(math_test_functions2) { BOOST_LOG_SEV(lg, trace) << "Starting test case for mkl test 2"; float dot = 3; BOOST_TEST(dot == 3); BOOST_LOG_SEV(lg, trace) << "Ending test case for mkl test 2"; } BOOST_AUTO_TEST_SUITE_END() File4: // cat logging-helper.h // I realize that not all these headers are necessary. Was trying out different things. #pragma once #define BOOST_LOG_DYN_LINK 1 #include <boost/move/utility_core.hpp> #include <boost/log/sources/logger.hpp> #include <boost/log/sources/record_ostream.hpp> #include <boost/log/sources/global_logger_storage.hpp> #include <boost/log/utility/setup/file.hpp> #include <boost/log/utility/setup/console.hpp> #include <boost/log/utility/setup/common_attributes.hpp> #include <boost/log/trivial.hpp> #include <boost/log/expressions.hpp> #include <boost/log/sinks/text_file_backend.hpp> #include <boost/log/sources/severity_logger.hpp> namespace logging = boost::log; namespace src = boost::log::sources; namespace sinks = boost::log::sinks; namespace keywords = boost::log::keywords; using namespace logging::trivial; class Fixture { public: src::severity_logger<severity_level> lg; Fixture(){ logging::core::get()->remove_all_sinks(); logging::add_console_log ( std::cout, keywords::format = "[%TimeStamp%]: %Message%" ); logging::add_common_attributes(); } }; My compile/link line is this g++ -I/home/anandrs/Downloads/boost_1_63_0 -L/home/anandrs/Downloads/boost_1_63_0/stage/lib mkl1.cpp mkl2.cpp mklmain.cpp -lboost_prg_exec_monitor -lboost_unit_test_framework -lboost_context -lboost_locale -lboost_log -lboost_log_setup -lboost_timer -lboost_type_erasure -lboost_wave -lboost_chrono -lboost_filesystem -lboost_graph -lboost_random -lboost_thread -lboost_wserialization -lboost_atomic -lboost_container -lboost_date_time -lboost_iostreams -lboost_math_c99 -lboost_math_c99f -lboost_math_c99l -lboost_math_tr1 -lboost_math_tr1f -lboost_math_tr1l -lboost_program_options -lboost_regex -lboost_serialization -lboost_signals -lboost_system -lboost_exception -lboost_test_exec_monitor -o BoostMKL valgrind ./BoostMKL ==83998== Memcheck, a memory error detector ==83998== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al. ==83998== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info ==83998== Command: ./BoostMKL ==83998== Running 2 test cases... [2017-02-23 10:11:04.603945]: Starting test case for mkl test 2 [2017-02-23 10:11:04.759958]: Ending test case for mkl test 2 [2017-02-23 10:11:04.824863]: Starting test case for mkl test 1 [2017-02-23 10:11:04.830820]: Ending test case for mkl test 1 *** No errors detected ==83998== Invalid read of size 4 ==83998== at 0x93124B6: std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() (in /usr/lib64/libstdc++.so.6.0.13) ==83998== by 0x9A4AEBC: __cxa_finalize (in /lib64/libc-2.12.so) ==83998== by 0x5083745: ??? (in /local/home/anandrs/Downloads/boost_1_63_0/stage/lib/libboost_unit_test_framework.so.1.63.0) ==83998== by 0x50DBE00: ??? (in /local/home/anandrs/Downloads/boost_1_63_0/stage/lib/libboost_unit_test_framework.so.1.63.0) ==83998== by 0x9A4AB21: exit (in /lib64/libc-2.12.so) ==83998== by 0x9A33D63: (below main) (in /lib64/libc-2.12.so) ==83998== Address 0xa1d4cd0 is 16 bytes inside a block of size 32 free'd ==83998== at 0x4C26FD6: operator delete(void*) (vg_replace_malloc.c:480) ==83998== by 0x93124C8: std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() (in /usr/lib64/libstdc++.so.6.0.13) ==83998== by 0x9A4AB21: exit (in /lib64/libc-2.12.so) ==83998== by 0x9A33D63: (below main) (in /lib64/libc-2.12.so) ==83998== ==83998== Invalid free() / delete / delete[] / realloc() ==83998== at 0x4C26FD6: operator delete(void*) (vg_replace_malloc.c:480) ==83998== by 0x93124C8: std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() (in /usr/lib64/libstdc++.so.6.0.13) ==83998== by 0x9A4AEBC: __cxa_finalize (in /lib64/libc-2.12.so) ==83998== by 0x5083745: ??? (in /local/home/anandrs/Downloads/boost_1_63_0/stage/lib/libboost_unit_test_framework.so.1.63.0) ==83998== by 0x50DBE00: ??? (in /local/home/anandrs/Downloads/boost_1_63_0/stage/lib/libboost_unit_test_framework.so.1.63.0) ==83998== by 0x9A4AB21: exit (in /lib64/libc-2.12.so) ==83998== by 0x9A33D63: (below main) (in /lib64/libc-2.12.so) ==83998== Address 0xa1d4cc0 is 0 bytes inside a block of size 32 free'd ==83998== at 0x4C26FD6: operator delete(void*) (vg_replace_malloc.c:480) ==83998== by 0x93124C8: std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() (in /usr/lib64/libstdc++.so.6.0.13) ==83998== by 0x9A4AB21: exit (in /lib64/libc-2.12.so) ==83998== by 0x9A33D63: (below main) (in /lib64/libc-2.12.so) ==83998== ==83998== ==83998== HEAP SUMMARY: ==83998== in use at exit: 1,552 bytes in 34 blocks ==83998== total heap usage: 3,704 allocs, 3,698 frees, 221,397 bytes allocated ==83998== ==83998== LEAK SUMMARY: ==83998== definitely lost: 1,032 bytes in 28 blocks ==83998== indirectly lost: 0 bytes in 0 blocks ==83998== possibly lost: 0 bytes in 0 blocks ==83998== still reachable: 520 bytes in 6 blocks ==83998== suppressed: 0 bytes in 0 blocks ==83998== Rerun with --leak-check=full to see details of leaked memory ==83998== ==83998== For counts of detected and suppressed errors, rerun with: -v ==83998== ERROR SUMMARY: 112 errors from 2 contexts (suppressed: 6 from 6) Thanks, Anand On Tue, Feb 21, 2017 at 2:03 PM, anandram sundar <sundaranandram(a)gmail.com> wrote: > Hi, > I recently wrote some tests using the Boost testing framework and > everything was working fine until I used the intel MKL with my project. As > soon as I started linking these libraries, the tests started failing with a > segmentation fault. This happens after the test execution is done and when > the cleanup is happening. Looking at what valgrind outputs, it seems like > there is some memory being released which is invalid(not sure if it is > because of calling free on already freed memory). This actually happens > even if none of the code depends on the MKL. Just adding them to the linked > libraries is enough to cause this. > > GCC 4.9.3 > Boost ver 1.62 > > *==85160== Invalid read of size 4* > *==85160== at 0x10916C57: std::basic_string<char, > std::char_traits<char>, std::allocator<char> >::~basic_string() (in > /lib/libstdc++.so.6.0.20)* > *==85160== by 0x1104AEBC: __cxa_finalize (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x41981E2: ??? (in > /lib/libboost_unit_test_framework.so.1.62.0)* > *==85160== by 0x400EC5B: _dl_fini (in /lib64/ld-2.12.so > <http://ld-2.12.so>)* > *==85160== by 0x1104AB21: exit (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x11033D63: (below main) (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== Address 0x1262fab0 is 16 bytes inside a block of size 30 > free'd* > *==85160== at 0x4C26FD6: operator delete(void*) > (vg_replace_malloc.c:480)* > *==85160== by 0x1104AB21: exit (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x11033D63: (below main) (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > > > *==85160== Invalid free() / delete / delete[] / realloc()* > *==85160== at 0x4C26FD6: operator delete(void*) > (vg_replace_malloc.c:480)* > *==85160== by 0x1104AEBC: __cxa_finalize (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x41981E2: ??? (in > /lib/libboost_unit_test_framework.so.1.62.0)* > *==85160== by 0x400EC5B: _dl_fini (in /lib64/ld-2.12.so > <http://ld-2.12.so>)* > *==85160== by 0x1104AB21: exit (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x11033D63: (below main) (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== Address 0x1262faa0 is 0 bytes inside a block of size 30 free'd* > *==85160== at 0x4C26FD6: operator delete(void*) > (vg_replace_malloc.c:480)* > *==85160== by 0x1104AB21: exit (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x11033D63: (below main) (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > > > I am not sure why this is happening. Are there any known compatibility > issues between MKL and Boost testing framework. I was using ACML before > this and the tests were working fine with them. > > > Thanks, > Anand >

2 1

[Stacktrace] Review 2 Manager report
by Niall Douglas 31 Mar '17

31 Mar '17

Many thanks to all those who participated in the second review of proposed Boost.Stacktrace. I received the following formal reviews: 1. Peter Dimov (ACCEPT) 2. Vladimir Batov (ACCEPT) 3. Artyom Bellis (CONDITIONAL ACCEPT) 4. Bjorn Reese (ACCEPT) 5. Edward Diener (ACCEPT) Extensive comments without a formal recommendation were also made by: 1. Mark Bartosik 2. Florian Weimer Some of the more important conditions for acceptance as judged by the review manager are: * Problems on FreeBSD (and by inference OS X?). * Per frame execution of addr2line rather than calling it once. * Throw-with-trace was asked for by a lot of people. * One reviewer suggested that the addr2line backend was async signal unsafe. My reading of the code is that it is async signal unsafe to parse a stacktrace (and unavoidably so on any platform), but the capture of backtraces is now fully async signal safe. * Some disliked the bringing in of windows.h and the COM headers on Windows. For a header only library I consider this acceptable, Stacktrace when configured in non-header only mode does not inject windows.h into everything including stacktrace. Congratulations to Antony on getting yet another library of his into Boost! Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

2 1

Problem statically linking Boost 1.63
by Balázs Bámer 31 Mar '17

31 Mar '17

Hi All, I have asked it on Stackoverflow, but know one seems to know the answer who saw it. I post it here, too, because 1.55 (which works for me) is quite old and has problems in logging: writing logfiles stops whithin a day every time. So 1.63 would be important for me to try. Link to the Stackoverflow post: http://stackoverflow.com/questions/42978843/boost-inner-function-argument-m… Thank you in advance. Best regards: Balazs PS: I copy the post here, but its formatting will break in plain text. I have a strange problem during linking Boost 1.63.0. I use the following cmake lines to configure Boost: add_compile_options(-std=c++14 -DBOOST_LOG_DYN_LINK)set(BOOST_ROOT "/usr/local/alk/boost_1_63_0/") SET(Boost_USE_STATIC_LIBS OFF) find_package(Boost 1.63 REQUIRED COMPONENTS log_setup log regex thread date_time filesystem system) Then the sources compile, and the linker tells me similar messages: CMakeFiles/dsmip.dir/main.cpp.o: In function `boost::log::v2_mt_posix::sources::aux::logger_singleton<dataLogger>::init_instance()': /home/balazs/munka/neovoltaic/aufgaben/dsmip/main.cpp:(.text._ZN5boost3log11v2_mt_posix7sources3aux16logger_singletonI10dataLoggerE13init_instanceEv[_ZN5boost3log11v2_mt_posix7sources3aux16logger_singletonI10dataLoggerE13init_instanceEv]+0x2d): undefined reference to `boost::log::v2_mt_posix::sources::aux::global_storage::get_or_init(std::type_info const&, boost::shared_ptr<boost::log::v2_mt_posix::sources::aux::logger_holder_base> (*)())' Here the following function is missing: *boost::log::v2_mt_posix::sources::aux::global_storage::get_or_init(std::type_info const&, boost::shared_ptr (*)())* Going into the freshly compiled Boost stage directory: balazs@balazs:/usr/local/alk/boost_1_63_0/stage/lib$ grep get_or_init *Binary file libboost_log.so matchesBinary file libboost_log.so.1.63.0 matches balazs@balazs:/usr/local/alk/boost_1_63_0/stage/lib$ strings libboost_log.so |grep get_or_init _ZN5boost3log11v2_mt_posix7sources3aux14global_storage11get_or_initENS_9typeindex14stl_type_indexEPFNS_10shared_ptrINS3_18logger_holder_baseEEEvE Demangling it yields: *boost::log::v2_mt_posix::sources::aux::global_storage::get_or_init(boost::typeindex::stl_type_index, boost::shared_ptr (*)())* which are not identical, the first function argument type differs. I used these commands to compile Boost: ./bootstrap.sh --with-toolset=clang./b2 --build-type=minimal --layout=system toolset=clang variant=release link=shared threading=multi runtime-link=shared stage How can this happen? Actually, this dynamically linked Boost is my second experiment. Originally I wanted to link it statically. Thank you in advance. Best regards: Balázs Bámer EDIT Now I have tried the Boost libraries I get with apt-get, and the situation is the same. However, I have found my old settings. They do work: add_compile_options(-std=c++14) SET(Boost_USE_STATIC_LIBS ON) find_package(Boost 1.55 REQUIRED COMPONENTS log_setup log thread date_time filesystem system) find_package(Threads REQUIRED)

2 1

Aliased parameters in boost::bind
by Evgeny Fraimovitch 30 Mar '17

30 Mar '17

Hello, The tutorial for Boost.Bind library contains the following sample code: bind can handle functions with more than two arguments, and its argument substitution mechanism is more general: bind(f, _2, _1)(x, y); // f(y, x) bind(g, _1, 9, _1)(x); // g(x, 9, x) bind(g, _3, _3, _3)(x, y, z); // g(z, z, z) bind(g, _1, _1, _1)(x, y, z); // g(x, x, x) As can be seen, all but the first of those samples alias the placeholder parameters, substituting a single passed argument several times. What is not mentioned in the tutorial (http://www.boost.org/doc/libs/1_63_0/libs/bind/doc/html/bind.html#bind.purp ose.using_bind_with_functions_and_fu) is the fact that such aliasing for any parameter with nontrivial move behavior is unexpected and possibly dangerous. For instance, given the function: void f(std::string x, std::string y, std::string z) { std::cout << x << y << z; } One could following the tutorial naively write: auto triple = boost::bind(f, _1, _1, _1); and this would even work for: std::string x = "a pretty long string"; triple(x); printing the string thrice, as expected. However the result of triple(std::string("a pretty long string")) would be the string only printed once, which is hardly what the user would expect. In fact, any bind expression produced with aliasing would be sensitive to the type of the reference passed, violating the functor abstraction badly. So, the question is: 1. This behavior seems to match the std::bind behavior documented in the standard. However, would it not be wise to warn against parameter aliasing in the tutorial then? (instead of demonstrating it as one of the first samples) 2. Maybe we can actually check if a parameter is aliased in boost::bind and copy it if it is - I have not tried it, but I think it can be done. Would it be a more sensible thing to do? The sample above might seem contrived, but I've actually encountered this bug in production code when porting it to boost 1.63 (the boost.signals code implicitly does boost::forward, so it was not outwardly apparent what was happening) Sincerely yours, Evgeny

3 6

[asio] sslv3 handshake
by Jim Gallogly 30 Mar '17

30 Mar '17

I want to do a simple C++ web get similar to what is done by this curl command. I must use boost 1.49 > curl https://mysite.dev/api/v1/search?q=test -k --cert > C:\work\testCert.pem The server is requiring the client certificate. I started by using this as an example http://www.boost.org/doc/libs/1_49_0/doc/html/boost_asio/example/ssl/client… and I added modifications by adding calls to the context like ctx.set_options(boost::asio::ssl::context::default_workarounds); ctx.use_certificate_file("C:\\work\\testCert.pem", boost::asio::ssl::context_base::pem); My Request Looks like this: > GET /api/v1/search?q=test HTTP/1.0<br> > Host: mysite.dev <br> > Accept: \*/* but I keep getting messages like this > Error: sslv3 alert handshake failure Does any one know what other steps I need to do? Is this possible in boost 1.49? Thanks, Jim

3 3

[release] Boost 1.64.0 Beta 2
by Rene Rivera 30 Mar '17

30 Mar '17

Boost release 1.64.0 beta 2 is now available at: <https://dl.bintray.com/boostorg/beta/1.64.0.beta.2/source/> The SHA256 checksums are as follows: 49c9339b9d8e7b2610ef84c80cd10b2252c119ebcc3222450beb0e94c1da1522 boost_1_64_0_b2.7z 92ec7cbf1e77c5979e381dd8104f9e96c0471c276e566272751a981d806db94b boost_1_64_0_b2.tar.bz2 da5670892b7b572808491b13a7b9421c3c18e6f395d6a5ec822466db466eda01 boost_1_64_0_b2.tar.gz 61d6e29e8a1d7503fe13a9d916842f0ec2e625f733b98b29ce563f8cbdb482bf boost_1_64_0_b2.zip The notable difference from Beta 1 is the inclusion of the missing Boost Process library. For details of what's in the release, see < http://www.boost.org/users/history/version_1_64_0.html>. Note that the links to files on this web page are for the final release - use the link above to get the beta files. There are also pre-built libraries provided by Tom Kent here: <https://dl.bintray.com/boostorg/beta/1.64.0.beta.2/binaries/> Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

2 1

[statechart] process_event vs post_event confusion
by Robert Dailey 30 Mar '17

30 Mar '17

I'm seeing a usability issue between post_event and process_event. Basically, depending on where in the state itself I'm executing an event, I need to know which to invoke. My understanding is that if I'm calling within the context of the constructor of the state, I need to use post_event. Anywhere else (outside of construction, but still within a member function of the state subclass itself), you invoke "context<MyMachine>().process_event()". Why can't post_event() automatically query the state machine to see if it is "busy" constructing a state, and if it isn't, forward the event to process_event() for me instead? Is there really a reason to have to make a logical decision between the two in code? I'm using boost::statechart in my code at $DAYJOB and this is a reasonable complaint I get in my code reviews, especially from those not very familiar with boost itself. They have an expectation for the implementation of the state machine to be intuitive and easy to understand.

2 2

Re: [Boost-users] [boost] Going insane trying to build boost for android
by Robert Dailey 29 Mar '17

29 Mar '17

On Wed, Mar 29, 2017 at 2:16 PM, John Maddock <jz.maddock(a)googlemail.com> wrote: > >> >> I'm still not able to build boost though. I did try switching to API >> 21 but I get a different set of errors: >> >> >> In file included from libs\atomic\src\lockpool.cpp:16: >> In file included from .\boost/config.hpp:57: >> In file included from .\boost/config/platform/linux.hpp:74: >> In file included from .\boost/config/posix_features.hpp:18: >> In file included from >> C:/android/ndk/platforms/android-21/arch-arm/usr/include\unistd.h:34: >> In file included from >> C:/android/ndk/platforms/android-21/arch-arm/usr/include\sys/select.h:35: >> C:/android/ndk/platforms/android-21/arch-arm/usr/include\signal.h:86:18: >> error: expected ';' at end of declaration list >> sighandler_t sa_handler; >> ^ >> >> C:/android/ndk/platforms/android-21/arch-arm/usr/include\asm/signal.h:101:22: >> note: expanded from macro 'sa_handler' >> #define sa_handler _u._sa_handler >> ^ > > > OK, so you suckered me into this.... just installed Android NDK and it's a > quoting problem, but what the issue is I'm not sure. For example b2 invokes > the compiler inside quotes like this: > > "clang++" <options> file.cpp > > Which produces: > > 'M:\data\boost\boost\\clang38++.exe' is not recognized as an internal or > external command, > operable program or batch file. > > So then you go into clang++cmd and maybe edit it so the %~dp0\ prefix is > removed from the clang38 invocation (that's what I did anyway). Now you > get: > > .\boost/config/stdlib/libstdcpp3.hpp:78:12: fatal error: 'unistd.h' file not > found > # include <unistd.h> > > Even though if you search the toolset it clearly does have several copies of > unistd.h there. > > And I'm wondering if you tried to fix that by editing the .cmd file and it's > further messed up clang's include paths? > > Note that at any time, invoking clang via: > > clang++ <options> file.cpp > > Will work just fine. > > So in effect Boost.Build has been broken by trying to do the right thing and > always quote the compiler invocation (and I'm pretty sure not quoting would > break a bunch of other toolsets). > > So... which libraries do you require.... since most of them are "just a > bunch of source files" the easiest solution would be to build what you need > manually with something like: > > clang++ -c -I. -O3 -shared libs/boost-library-you-want/src/*.cpp > mylibraryname.so > > which worked for me with a cursory test on Boost.System and Regex > > Hopefully someone can suggest a better long term fix, John. +boost again Yeah, you are running into the exact same set of issues I am. First I ran into the %~dp0 issue, removed that, then the next thing is it can't find any files. I started using the boost cmake build process here: https://github.com/Orphis/boost-cmake This works perfectly once I specify a toolchain file to CMake for the android NDK. Note that this solution means boost builds with the rest of my targets, which isn't ideal, but at least boost builds properly... I really hate bjam/b2 with a passion. For as great as boost is as a library, it's completely out of left field that they deal with this garbage build system.

1 0

boost::asio::asyn_accept handler
by Christopher Pisz 29 Mar '17

29 Mar '17

I am looking at the example source at http://www.boost.org/doc/libs/1_62_0/doc/html/boost_asio/tutorial/tutdaytim… It passes their own connection class to the accept handler as an argument: acceptor_.async_accept(new_connection->socket(), boost::bind(&tcp_server::handle_accept, this, new_connection, boost::asio::placeholders::error)); I tried to implement a class method that would do the same: void ServerSocketASIO::Listen(boost::asio::ip::tcp::acceptor & acceptor, std::function<void(ServerSocketASIO *, const boost::system::error_code &)> callback) { acceptor.async_accept(m_socket, callback); m_connectionState = LISTENING; } but when I compile, I get errors that say AcceptHandler type requirements not met If I implement it this way: void ServerSocketASIO::Listen(boost::asio::ip::tcp::acceptor & acceptor, std::function<void(const boost::system::error_code &)> callback) { acceptor.async_accept(m_socket, callback); m_connectionState = LISTENING; } It compiles, but I would need the actual connection to put into a collection of some kind, in order to keep track of connected clients. The documentation I found at http://www.boost.org/doc/libs/1_62_0/doc/html/boost_asio/reference/AcceptHa… Only shows the accept callback with a boost::system::error_code argument. So, my question is, is the example source wrong? and How do I pass my own connection class to the callback? -- View this message in context: http://boost.2283326.n4.nabble.com/boost-asio-asyn-accept-handler-tp4693107… Sent from the Boost - Users mailing list archive at Nabble.com.

4 13

[asio] Using ASIO to connect to https: using client certificate
by Jim Gallogly 29 Mar '17

29 Mar '17

I want to do a simple C++ web get, similar to what is done by this curl command. I must use boost 1.49 curl https://mysite.dev -k --cert C:\work\testCert.pem The server is requiring the client certificate. I started by using this example http://www.boost.org/doc/libs/1_49_0/doc/html/boost_asio/example/ssl/client… and I added modifications by adding calls to the context like ctx.set_verify_mode(boost::asio::ssl::verify_peer); ctx.set_options(boost::asio::ssl::context::default_workarounds); ctx.use_certificate_file("C:\\work\\testCert.pem", boost::asio::ssl::context_base::pem); ctx.use_private_key_file("C:\\work\\testKey.pem", boost::asio::ssl::context_base::pem); but I keep getting messages like Connect failed: No connection could be made because the target machine actively refused it Any help or direction would be very appreciated, Thanks, Jim

1 0

[crc] Current status of this library
by Bill Somerville 29 Mar '17

29 Mar '17

Hi all, I have a compile error using the Boost 1.63.0 CRC library with the g++ v6.3 compiler with the following usage: #include <boost/crc.hpp> extern "C" { short crc12 (unsigned char const * data, int length); bool crc12_check (unsigned char const * data, int length); } // assumes CRC is last 16 bits of the data and is set to zero // caller should assign the returned CRC into the message in big endian byte order short crc12 (unsigned char const * data, int length) { return boost::augmented_crc<12, 0xc06> (data, length); } bool crc12_check (unsigned char const * data, int length) { return !boost::augmented_crc<12, 0xc06> (data, length); } The error I get with g++ v6.3 is: In file included from /home/bill/wsjtx-prefix/src/boost/boost/config.hpp:61:0, from /home/bill/wsjtx-prefix/src/boost/boost/crc.hpp:12, from /home/bill/wsjtx-prefix/src/lib/crc12.cpp:1: /home/bill/wsjtx-prefix/src/boost/boost/crc.hpp: In instantiation of ‘const least boost::detail::mask_uint_t<12ul>::sig_bits’: /home/bill/wsjtx-prefix/src/boost/boost/crc.hpp:356:9: required from ‘const fast boost::detail::mask_uint_t<12ul>::sig_bits_fast’ /home/bill/wsjtx-prefix/src/boost/boost/crc.hpp:1075:16: required from ‘typename boost::uint_t<Bits>::fast boost::augmented_crc(const void*, std::size_t, typename boost::uint_t<Bits>::fast) [with long unsigned int Bits = 12ul; typename boost::uint_t<Bits>::fast TruncPoly = 3078u; typename boost::uint_t<Bits>::fast = short unsigned int; std::size_t = long unsigned int]’ /home/bill/wsjtx-prefix/src/boost/boost/crc.hpp:1092:41: required from ‘typename boost::uint_t<Bits>::fast boost::augmented_crc(const void*, std::size_t) [with long unsigned int Bits = 12ul; typename boost::uint_t<Bits>::fast TruncPoly = 3078u; typename boost::uint_t<Bits>::fast = short unsigned int; std::size_t = long unsigned int]’ /home/bill/wsjtx-prefix/src/lib/crc12.cpp:14:57: required from here /home/bill/wsjtx-prefix/src/boost/boost/crc.hpp:350:69: warning: left shift of negative value [-Wshift-negative-value] BOOST_STATIC_CONSTANT( least, sig_bits = (~( ~(least( 0u )) << Bits )) ); ~~~~~~~~~~~~~~~~~^~~~~~~~~ /home/bill/wsjtx-prefix/src/boost/boost/crc.hpp:350:69: error: left operand of shift expression ‘(-1 << 12ul)’ is negative [-fpermissive] I note that the develop branch of the CRC library has many changes since Boost 1.63.0 but none are in Boost 1.64.0-beta1. So far I have only tried the new library (devlop branch) with my code and it compiles ok but I need to test it further. Does anyone know why the latest CRC library is not in 1.64 and also does anyone know if the develop branch code is ok and usable by substitution into a 1.63 Boost? Regards Bill Somerville.

1 0

Re: [Boost-users] [boost] Going insane trying to build boost for android
by Robert Dailey 28 Mar '17

28 Mar '17

On Tue, Mar 28, 2017 at 3:10 AM, John Maddock <jz.maddock(a)googlemail.com> wrote: > > Right, but that built with g++ not clang++. Doh!!! I didn't even notice this. Crap. I'll fix it when I get home and try again. > I don't think Boost.Build does anything "different" here: it basically just > invokes clang++. > > Note that clang is not particular "bright" in the way it creates it's > wrapper headers around <cstdlib> etc. Last time I had an issue like this, > the missing symbol was present in the system headers, but guarded by a > #ifdef that clang didn't define (where as GCC did)..... OK had a quick > Google, and that symbol is protected by a clang "availability" macro: > > longdoublestrtold(constchar*,char**)__INTRODUCED_IN(21); > > So it seems to me that this error will be generated by any attempt to > compile with clang unless you specify some "magic" command line option to > tell it to use the latest android API? No idea what that would be, but > perhaps you do? > > Hopefully getting closer, John. Thanks for the help. Looks like it is expecting API 21 to be used. Which is strange because the NDK documentation says to use the minimum supported API you intend to use. Which is 15 for me. But just grepping the NDK source directories, I see that certain files/symbols are only defined starting at API 21. I think a lot of the C library headers are provided by the target API directory, and they change it with each version. I'll try 21 and see if I get different results, and hopefully it won't break when running on Android Ice Cream Sandwich (API 15)

1 1

Re: [Boost-users] [boost] Going insane trying to build boost for android
by Robert Dailey 28 Mar '17

28 Mar '17

On Sun, Mar 26, 2017 at 12:04 PM, John Maddock <jz.maddock(a)googlemail.com> wrote: > >> So outside of what I'm already doing, how do I properly tell boost >> about C++14? I'm sending down a cxxflag for it in my jam file right >> now, but that's the only way I've been able to find out how to do it >> from my Google searching. > > > Nod. As far as I know that's the only way, two questions: > > * If you build something with the -d2 option do you see all the -std= > compiler flags you expect to see? > * If you do so, can you build and *run* libs/config/test/config_info and > report the output? (Re-included the boost ML) With the -d2 option added, this is what I see: clang-linux.compile.c++.without-pth bin.v2\libs\atomic\build\clang-linux-android\release\link-static\target-os-android\threadapi-pthread\threading-multi\lockpool.o "C:/android/ndk/toolchains/llvm/prebuilt/windows-x86_64/bin/clang++" -c -x c++ -O3 -Wno-inline -Wall --sysroot=C:/android/ndk/platforms/android-15/arch-arm -IC:/android/ndk/sources/cxx-stl/llvm-libc++abi/include -IC:/android/ndk/sources/cxx-stl/llvm-libc++/include -IC:/android/ndk/sources/android/support/include -std=c++14 -fno-strict-aliasing -D__GLIBC__ -DANDROID -D__ANDROID__ -D_GLIBCXX__PTHREADS -D__arm__ -D_REENTRANT -O2 -DNDEBUG -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_SOURCE -DBOOST_ATOMIC_STATIC_LINK=1 -DNDEBUG -I"." -o "bin.v2\libs\atomic\build\clang-linux-android\release\link-static\target-os-android\threadapi-pthread\threading-multi\lockpool.o" "libs\atomic\src\lockpool.cpp" In file included from libs\atomic\src\lockpool.cpp:16: In file included from .\boost/config.hpp:57: In file included from .\boost/config/platform/linux.hpp:15: C:/android/ndk/sources/cxx-stl/llvm-libc++/include\cstdlib:108:9: error: no member named 'strtold' in the global namespace using ::strtold; ~~^ C:/android/ndk/sources/cxx-stl/llvm-libc++/include\cstdlib:126:9: error: no member named '_Exit' in the global namespace using ::_Exit; ~~^ C:/android/ndk/sources/cxx-stl/llvm-libc++/include\cstdlib:149:9: error: no member named 'at_quick_exit' in the global namespace using ::at_quick_exit; ~~^ C:/android/ndk/sources/cxx-stl/llvm-libc++/include\cstdlib:150:9: error: no member named 'quick_exit' in the global namespace using ::quick_exit; ~~^ 4 errors generated. I do see -std=c++14 in there. As for your second question, why would building and running config_info help? I'm cross compiling, so I can't run this on Windows. If you could provide explicit instructions so I properly understand what you want me to do, that would be ideal. Thanks.

4 5

Re: [Boost-users] [boost] Going insane trying to build boost for android
by Robert Dailey 28 Mar '17

28 Mar '17

On Mon, Mar 27, 2017 at 11:54 AM, John Maddock <jz.maddock(a)googlemail.com> wrote: > >> That won't do me any good because I'm already using this toolchain >> perfectly fine via CMake and ndk-build. bjam isn't working, maybe >> because I haven't set up the config.jam file properly. I'm not sure at >> this point. Boost is the only thing not working here. > > > Then if you compare the compilation command line generated when building > under b2 and when building under cmake the error should be obvious? I took your advice and compared a real build that worked using CMake (using a simple test cpp file) and what I got from b2. Here is the command line used to build the sample app using CMake. Note that the compilation succeeded: C:\android\ndk\toolchains\arm-linux-androideabi-4.9\prebuilt\windows-x86_64\bin\arm-linux-androideabi-g++.exe --sysroot=C:/android/ndk/platforms/android-15/arch-arm -Dndk_test_EXPORTS -isystem C:/android/ndk/sources/cxx-stl/llvm-libc++/include -isystem C:/android/ndk/sources/android/support/include -isystem C:/android/ndk/sources/cxx-stl/llvm-libc++abi/include -isystem C:/android/ndk/platforms/android-15/arch-arm/usr/include -march=armv7-a -mthumb -mfpu=vfpv3-d16 -mfloat-abi=softfp -funwind-tables -no-canonical-prefixes -fexceptions -frtti -g -fPIC -std=gnu++14 -MD -MT CMakeFiles/ndk_test.dir/main.cpp.o -MF CMakeFiles\ndk_test.dir\main.cpp.o.d -o CMakeFiles/ndk_test.dir/main.cpp.o -c ../main.cpp And here is the command line from b2: "C:/android/ndk/toolchains/llvm/prebuilt/windows-x86_64/bin/clang++" -c -x c++ -O3 -Wno-inline -Wall --sysroot=C:/android/ndk/platforms/android-15/arch-arm -isystem C:/android/ndk/sources/cxx-stl/llvm-libc++/include -isystem C:/android/ndk/sources/android/support/include -isystem C:/android/ndk/sources/cxx-stl/llvm-libc++abi/include -isystem C:/android/ndk/platforms/android-15/arch-arm/usr/include -std=c++14 -fno-strict-aliasing -D__GLIBC__ -DANDROID -D__ANDROID__ -D_GLIBCXX__PTHREADS -D__arm__ -D_REENTRANT -O2 -DNDEBUG -H -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_SOURCE -DBOOST_ATOMIC_STATIC_LINK=1 -DNDEBUG -I"." -o "bin.v2\libs\atomic\build\clang-linux-android\release\link-static\target-os-android\threadapi-pthread\threading-multi\lockpool.o" "libs\atomic\src\lockpool.cpp" The build for boost still fails. Note I also passed the -H option, so I could see the include searches performed by clang as it was building boost. The output is long, but I've included it below. Can anyone help me identify why boost still won't build? clang-linux.compile.c++.without-pth bin.v2\libs\atomic\build\clang-linux-android\release\link-static\target-os-android\threadapi-pthread\threading-multi\lockpool.o "C:/android/ndk/toolchains/llvm/prebuilt/windows-x86_64/bin/clang++" -c -x c++ -O3 -Wno-inline -Wall --sysroot=C:/android/ndk/platforms/android-15/arch-arm -isystem C:/android/ndk/sources/cxx-stl/llvm-libc++/include -isystem C:/android/ndk/sources/android/support/include -isystem C:/android/ndk/sources/cxx-stl/llvm-libc++abi/include -isystem C:/android/ndk/platforms/android-15/arch-arm/usr/include -std=c++14 -fno-strict-aliasing -D__GLIBC__ -DANDROID -D__ANDROID__ -D_GLIBCXX__PTHREADS -D__arm__ -D_REENTRANT -O2 -DNDEBUG -H -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_SOURCE -DBOOST_ATOMIC_STATIC_LINK=1 -DNDEBUG -I"." -o "bin.v2\libs\atomic\build\clang-linux-android\release\link-static\target-os-android\threadapi-pthread\threading-multi\lockpool.o" "libs\atomic\src\lockpool.cpp" . C:/android/ndk/sources/cxx-stl/llvm-libc++/include\\cstddef .. C:/android/ndk/sources/cxx-stl/llvm-libc++/include\\__config .. C:\\android\\ndk\\toolchains\\llvm\\prebuilt\\windows-x86_64\\bin\\..\\lib64\\clang\\3.8.275480\\include\\stddef.h ... C:\\android\\ndk\\toolchains\\llvm\\prebuilt\\windows-x86_64\\bin\\..\\lib64\\clang\\3.8.275480\\include/__stddef_max_align_t.h .. C:/android/ndk/sources/cxx-stl/llvm-libc++/include\\__nullptr . .\\boost/config.hpp .. .\\boost/config/user.hpp .. .\\boost/config/select_compiler_config.hpp .. .\\boost/config/compiler/clang.hpp .. .\\boost/config/select_stdlib_config.hpp .. .\\boost/config/stdlib/libcpp.hpp .. .\\boost/config/select_platform_config.hpp .. .\\boost/config/platform/linux.hpp ... C:/android/ndk/sources/cxx-stl/llvm-libc++/include\\cstdlib .... C:/android/ndk/sources/cxx-stl/llvm-libc++/include\\stdlib.h ..... C:/android/ndk/sources/android/support/include\\stdlib.h ...... C:/android/ndk/platforms/android-15/arch-arm/usr/include\\stdlib.h ....... C:/android/ndk/platforms/android-15/arch-arm/usr/include\\sys/cdefs.h ........ C:/android/ndk/platforms/android-15/arch-arm/usr/include\\sys/cdefs_elf.h ........ C:/android/ndk/platforms/android-15/arch-arm/usr/include\\android/api-level.h ....... C:/android/ndk/sources/cxx-stl/llvm-libc++/include\\stddef.h ........ C:\\android\\ndk\\toolchains\\llvm\\prebuilt\\windows-x86_64\\bin\\..\\lib64\\clang\\3.8.275480\\include\\stddef.h ....... C:/android/ndk/sources/cxx-stl/llvm-libc++/include\\stddef.h ........ C:\\android\\ndk\\toolchains\\llvm\\prebuilt\\windows-x86_64\\bin\\..\\lib64\\clang\\3.8.275480\\include\\stddef.h ....... C:/android/ndk/sources/cxx-stl/llvm-libc++/include\\string.h ........ C:/android/ndk/sources/android/support/include\\string.h ......... C:/android/ndk/platforms/android-15/arch-arm/usr/include\\string.h .......... C:/android/ndk/sources/cxx-stl/llvm-libc++/include\\stddef.h .......... C:/android/ndk/platforms/android-15/arch-arm/usr/include\\malloc.h ........... C:/android/ndk/sources/cxx-stl/llvm-libc++/include\\stddef.h ....... C:/android/ndk/platforms/android-15/arch-arm/usr/include\\alloca.h ....... C:/android/ndk/platforms/android-15/arch-arm/usr/include\\strings.h ........ C:/android/ndk/platforms/android-15/arch-arm/usr/include\\sys/types.h ......... C:/android/ndk/sources/cxx-stl/llvm-libc++/include\\stddef.h .......... C:\\android\\ndk\\toolchains\\llvm\\prebuilt\\windows-x86_64\\bin\\..\\lib64\\clang\\3.8.275480\\include\\stddef.h ......... C:/android/ndk/sources/android/support/include\\stdint.h .......... C:/android/ndk/platforms/android-15/arch-arm/usr/include\\stdint.h ........... C:/android/ndk/sources/cxx-stl/llvm-libc++/include\\stddef.h ........... C:/android/ndk/platforms/android-15/arch-arm/usr/include\\sys/_types.h ............ C:/android/ndk/platforms/android-15/arch-arm/usr/include\\machine/_types.h ......... C:/android/ndk/platforms/android-15/arch-arm/usr/include\\linux/posix_types.h .......... C:/android/ndk/platforms/android-15/arch-arm/usr/include\\linux/stddef.h ........... C:/android/ndk/platforms/android-15/arch-arm/usr/include\\linux/compiler.h .......... C:/android/ndk/platforms/android-15/arch-arm/usr/include\\asm/posix_types.h ......... C:/android/ndk/platforms/android-15/arch-arm/usr/include\\asm/types.h ......... C:/android/ndk/platforms/android-15/arch-arm/usr/include\\linux/types.h ......... C:/android/ndk/platforms/android-15/arch-arm/usr/include\\machine/kernel.h ......... C:/android/ndk/platforms/android-15/arch-arm/usr/include\\sys/sysmacros.h ....... C:/android/ndk/platforms/android-15/arch-arm/usr/include\\memory.h In file included from libs\atomic\src\lockpool.cpp:16: In file included from .\boost/config.hpp:57: In file included from .\boost/config/platform/linux.hpp:15: C:/android/ndk/sources/cxx-stl/llvm-libc++/include\cstdlib:108:9: error: no member named 'strtold' in the global namespace using ::strtold; ~~^ C:/android/ndk/sources/cxx-stl/llvm-libc++/include\cstdlib:126:9: error: no member named '_Exit' in the global namespace using ::_Exit; ~~^ C:/android/ndk/sources/cxx-stl/llvm-libc++/include\cstdlib:149:9: error: no member named 'at_quick_exit' in the global namespace using ::at_quick_exit; ~~^ C:/android/ndk/sources/cxx-stl/llvm-libc++/include\cstdlib:150:9: error: no member named 'quick_exit' in the global namespace using ::quick_exit; ~~^

1 0

Compare boost::system::error_category
by Christopher Pisz 27 Mar '17

27 Mar '17

The following comparison fails for an error whom outputs "asio.misc" for errorCode.category().name() and "end of file" for errorCode.message() If it claims to be in category asio.misc, then why does the if condition of (errorCode.category() == boost::asio::error::misc_category ) evaluate to false? Googling says that a boost::system::error_code can have the same value in more than one category, so I assume that in order to get the proper message and meaning we must compare boost::system::error_category as well as boost::system::error_code::value. How do we properly compare the category if this fails to work? Code in question: //-------------------------------------------------------------------------------------------------- std::string ClientSocketASIO::ErrorCodeToString(const boost::system::error_code & errorCode) { std::ostringstream debugMsg; debugMsg << " Error Category: " << errorCode.category().name() << ". " << " Error Message: " << errorCode.message() << ". "; if( errorCode.category() == boost::asio::error::misc_category ) { switch (errorCode.value()) { case boost::asio::error::eof: debugMsg << ". Server has disconnected."; break; case boost::asio::error::connection_refused: debugMsg << ". Connection Refused"; break; default: debugMsg << ". Unknown Error."; break; } } else { debugMsg << ". Unknown Error category."; } return debugMsg.str(); } -- View this message in context: http://boost.2283326.n4.nabble.com/Compare-boost-system-error-category-tp46… Sent from the Boost - Users mailing list archive at Nabble.com.

7 20

Compile error with low_bits_mask_t
by Michael Kaes 27 Mar '17

27 Mar '17

Hi, I discovered a compile issue when using boosts integer_mask. The following simple program compiles fine with clang but fails with gcc. #include <iostream> #include <boost/integer.hpp> #include <boost/integer/integer_mask.hpp> int main() { typedef boost::low_bits_mask_t<2> mask_type_t; std::cout << mask_type_t::sig_bits << std::endl; return 0; } I took both clang and gcc from the svn trunk and boost in version 1.63. I did not have the time yet to dig through the boost implementation but I could not find anything in the issue tracker. So is this a compiler error of gcc or is this a bug in boost. I was able to find a stackoverflow question: http://stackoverflow.com/questions/40291949/boostinteger-mask-gcc-compiler-… And the answer sounds reasonable to me that this is a bug in boost. Can anyone confirm this? And why does clang accept this? Thanks, Michael

1 0

Re: [Boost-users] Going insane trying to build boost for android
by Robert Dailey 26 Mar '17

26 Mar '17

On Thu, Mar 23, 2017 at 9:14 PM, Robert Dailey <rcdailey.lists(a)gmail.com> wrote: > How many months has it been of lost google searching, trying to beat > b2 into submission. I have no idea at this point how to build boost > for Android. Really hoping I get some help here... > > So to start, here are the versions I'm using: > > - Android NDK r14b > - Boost 1.63.0 > > I'm doing all of this on Windows 10, through command prompt. > > I want to use clang and libc++ to build boost for API 15. I figure the > easiest way is to generate a standalone toolchain using the NDK, so I > did that first: > >> %ANDROID_NDK%\build\tools\make_standalone_toolchain.py --arch arm --api 15 --stl libc++ "C:\android\_toolchains\arm-api-15" > > This generated the appropriate toolchain (I think). > > I then temporarily added this location to PATH: > >> set PATH=C:\android\_toolchains\arm-api-15\bin;%PATH% > > Then I ran bootstrap: > >> bootstrap.bat --with-toolset=clang > > Then I tried to build boost itself: > >> b2 --toolset=clang cxxflags="-stdlib=libc++ -std=c++14" threadapi=pthread --prefix=..\boost_android_arm --builddir=./ target-os=linux define=BOOST_FILESYSTEM_VERSION=3 --without-python link=static runtime-link=shared threading=multi variant=release install -j8 > > However I get failures when it tries to run the clang command: > > 'C:\code\_third_party\boost_1_63_0\\clang38++.exe' is not recognized > as an internal or external command > > I'm not sure why it's appending that absolute path (that's where my > current directory is set to, and where boost source is). It should > just be trying to use "clang++" but doesn't look like it is. > > From the output, it looks like it's trying to use clang correctly I think: > > "clang++" -c -x c++ -stdlib=libc++ -std=c++14 -O3 -Wno-inline -Wall > -pthread -stdlib=libc++ -std=c++14 -DBOOST_ALL_NO_LIB=1 > -DBOOST_FILESYSTEM_VERSION=3 -DBOOST_THREAD_USE_LIB=1 -DNDEBUG -I"." > -o "bin.v2\libs\wave\build\clang-linux-android\release\link-static\target-os-linux\threadapi-pthread\threading-multi\cpplexer\re2clex\aq.o" > "libs\wave\src\cpplexer\re2clex\aq.cpp" > > Am I going about this all wrong? How in the heck can I build boost for > android using the settings I specified above? So I beat on this a bit more and I'm past the clang path issue (it was some %~dp0/clang38++.exe stuff the batch file was doing which didn't resolve the right base path) What are the actual include directories I need to use for clang? I think that's the difficulty I'm running into now... errors like: clang-linux.compile.c++.without-pth bin.v2\libs\atomic\build\clang-linux-android\release\link-static\target-os-android\threadapi-pthread\threading-multi\lockpool.o In file included from libs\atomic\src\lockpool.cpp:16: In file included from .\boost/config.hpp:57: In file included from .\boost/config/platform/linux.hpp:15: C:/android/ndk/sources/cxx-stl/llvm-libc++/include\cstdlib:108:9: error: no member named 'strtold' in the global namespace using ::strtold; ~~^ My config jam: import common ; import configure ; import build-system ; import generate ; import modules ; import option ; import os ; import package ; import path ; import project ; import regex ; import set ; import targets ; import feature ; import property ; local androidNDKRoot = C:/android/ndk ; # put the relevant path using clang : android : $(androidNDKRoot)/toolchains/llvm/prebuilt/windows-x86_64/bin/clang++ : <compileflags>-std=c++14 <compileflags>-stdlib=libc++ <compileflags>--sysroot=$(androidNDKRoot)/platforms/android-15/arch-arm <compileflags>-I$(androidNDKRoot)/sources/android/support/include <compileflags>-I$(androidNDKRoot)/sources/cxx-stl/llvm-libc++abi/include <compileflags>-I$(androidNDKRoot)/sources/cxx-stl/llvm-libc++/include <compileflags>-fno-strict-aliasing <compileflags>-D__GLIBC__ <compileflags>-DANDROID <compileflags>-D__ANDROID__ <compileflags>-D_GLIBCXX__PTHREADS <compileflags>-D__arm__ <compileflags>-D_REENTRANT <compileflags>-O2 <compileflags>-DNDEBUG ; And I'm running this command: b2 ^ --user-config=clang-android.jam ^ target-os=android ^ toolset=clang-android ^ threadapi=pthread ^ link=static ^ runtime-link=shared ^ threading=multi ^ variant=release ^ --prefix=..\boost_android_arm ^ --builddir=./ ^ --without-python ^ -j1 ^ install

1 1

[release] Boost 1.64.0 Beta 1
by Rene Rivera 26 Mar '17

26 Mar '17

Boost release 1.64.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.64.0.beta.1/source/> The SHA256 checksums are as follows: 8f0ba6b73fad15115049f9b3e7e27eae43be10a94b51a57142f3a27e55ef4beb boost_1_64_0_b1.7z b5c5abf127a3f723dafcc7cf55876c1bda9f014fb1b117f6a7f769e3cc407c4f boost_1_64_0_b1.tar.bz2 a7fe98a9a9f615f6fa68d8ea09ce725d19e3a4fe4719c21c9db29dff88b3b6e3 boost_1_64_0_b1.tar.gz 593005661af8dfe132b2b16bc2cd41339e6acd58456913f353d765090d7868f7 boost_1_64_0_b1.zip For details of what's in the release, see < http://www.boost.org/users/history/version_1_64_0.html>. Note that the links to files on this web page are for the final release - use the link above to get the beta files. There are also pre-built libraries provided by Tom Kent here: <https://dl.bintray.com/boostorg/beta/1.64.0.beta.1/binaries/> Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

5 5

License questions
by Julian D. 25 Mar '17

25 Mar '17

I am making a confidential commercial closed-source program, and Boost's libraries seem useful for me. I can't tell if the Boost license allows me to include it in closed-source. Would anybody know?

3 2