January 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

[serialize] using virtual inheritance causes compiler error
by Douwe Gelling 02 Mar '17

02 Mar '17

Hi all, When trying to serialize a class with a virtual base class, I'm getting compilation errors. It seems to be part of a bug in type_traits, but I'm wondering if anyone knows a workaround for making it work anyhow. ultimately, the error boils down to "error: virtual function 'A::foo' has more than one final overrider in 'boost_type_traits_internal_struct_X'", using the code listing below.. It's simplified as much as possible, but obviously I need virtual inheritance due to using diamond inheritance. #include <boost/archive/text_oarchive.hpp> #include <boost/serialization/base_object.hpp> #include <boost/serialization/export.hpp> #include <boost/serialization/serialization.hpp> struct A { virtual ~A(){}; virtual void foo() = 0; template <class Archive> void serialize(Archive& ar, const unsigned int version) { } }; struct B : public virtual A { virtual void foo() { } template <class Archive> void serialize(Archive& ar, const unsigned int version) { ar& boost::serialization::base_object<A>(*this); } }; struct C : public B { template <class Archive> void serialize(Archive& ar, const unsigned int version) { ar& boost::serialization::base_object<B>(*this); } }; BOOST_CLASS_EXPORT(C); int main() { C c; return 0; }

4 7

[gsoc17] Attn: We need 2017 mentors and project ideas for Boost!
by Niall Douglas 07 Feb '17

07 Feb '17

Dear Boost community, We are now a few weeks from the beginning of Google Summer of Code 2017! Last year we had the big surprise of being rejected by Google as an org, the second time ever, on the basis that Google felt we needed a year off. Thanks to the quick actions of the Boost Steering Committee and IMC Financial Markets we managed to put together a "Boost Summer of Code" so the students with projects in progress would not be left stranded. Despite a fair few teething problems, I think that worked out okay. As part of filling in our application for 2017, we must supply to Google a list of potential GSoC mentors and potential GSoC projects for summer 2017 in order to be approved as an organisation this year. Therefore a lengthy page of awesome project ideas at https://svn.boost.org/trac/boost/wiki/SoC2017 before *February 9th* would be an enormous help to getting us approved again this year and bringing to Boost another US$35,000 of Google funding. If you think yourself able to mentor a student doing some work on Boost this summer, *please* consider adding a description of the proposed work item and your name to the list. The year before last we had more slots awarded to us by Google than we had good combinations of student and mentor, so we had to return slots which I believe has not happened here at Boost GSoC in at least a decade. That means that your project ideas have a better chance than ever of receiving funding if you can find a good student, and that is best done by getting project ideas floated *early*. If you want to know more about mentoring a Google Summer of Code funded student work before you nominate yourself, please feel free to ask on the main Boost developers mailing list boost(a)lists.boost.org or via gsoc-admin(a)boost.org. Thank you in advance for your time.

1 1

[MultiIndex] Prevent automatic re-indexing after "modify"?
by Deniz Bahadir 06 Feb '17

06 Feb '17

Hi guys, Hi Joaquín, I have a question concerning the automatic re-indexing of Boost.MultiIndex indexes. Is it somehow possible to modify a member of the element-type that is used as key for (another) index without triggering automatic re-indexing? (Of course, I want to be able to trigger manual re-indexing later.) Or is it at least possible to adjust the code so that this can be achieved? To understand my question, here is my use-case and why I need it. I have a boost::multi_index_container with multiple indexes (one hashed_unique and four hashed_non_unique). I am accessing a range of elements through a hashed_non_unique index 'A'. Then I am iterating through these elements and want to modify the value of a member 'M' of each element. However, that member is used when calculating the key for another hashed_non_unique index 'B'. Therefore, I must use the "modify" function of index 'A'. The problem is now that it takes forever to modify the entire range. (We are talking about 100 thousands if not millions of entries that need to be modified.) Probably because re-indexing is triggered after each call to "modify". However, in my case it should be perfectly fine to postpone the re-indexing after I modified the entire range, because I am not going to access any element through index 'B' until I finished modifying the entire range. As a workaround I removed index 'B' from the container and declared the element-member 'M' as mutable. This allows me to directly change the value of 'M'. The speedup is astonishing. It now finishes almost in no time. But this workaround is not really feasible as it requires reimplementing index 'B' by somehow tracking the information outside of the multi_index_container. Therefore, my question really is: Is it possible to provide an "unsafe_modify" function, which does the same as "modify" but does not trigger automatic re-indexing, and an "refresh_index" function, which (manually) triggers the re-indexing? Thanks, Deniz

3 4

context library of boost: compiling for windows 32 on ubuntu 64
by Jack Kumba 04 Feb '17

04 Feb '17

Hello, I want to compile libboost_context.a for windows 32 on my ubuntu 64. for that, I specify the following in my user-config.jam file using gcc : : "i686-w64-mingw32-g++" ; and then, I run the following: b2 --with-context toolset=gcc target-os=windows variant=release link=static address-model=32 binary-format=pe architecture=x86 this gives me the following error: libs/context/src/unsupported.cpp:7:2: error: #error "platform not supported" #error "platform not supported" ^ "i686-w64-mingw32-g++" -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -march=i686 -mthreads -m32 -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTEXT_SOURCE -DBOOST_DISABLE_ASSERTS -DNDEBUG -I"." -c -o "bin.v2/libs/context/build/gcc-mingw-5.3.1/release/binary-format-pe/build-no/link-static/target-os-windows/threading-multi/unsupported.o" "libs/context/src/unsupported.cpp" ...failed gcc.compile.c++ bin.v2/libs/context/build/gcc-mingw-5.3.1/release/binary-format-pe/build-no/link-static/target-os-windows/threading-multi/unsupported.o... full message is posted here: https://thepasteb.in/p/y8hzcR93o3XO7t2 It seems like the context library of boost is not supported to compile for windows on linux? Is it the case? Thanks, Aja

3 4

Boost iostreams for binary data
by Robert Dailey 03 Feb '17

03 Feb '17

I have my own BinaryInputStream and BinaryOutputStream classes that simply take a reference to some container that meets the requirements of random access and contiguous internal memory. It doesn't own this container, but rather serves as an adapter to the container to allow stream operators to be used for streaming out data. For example, you can stream a `std::uint32_t` to the binary stream, and it will insert 4 elements into an internal byte vector which is just `std::vector<std::uint8_t>`. I did not implement these in terms of IO streams, because those seemed a bit overkill and make a lot of assumptions on the data being text-only. Also I can't stream binary data into vectors, lists, and other containers because the data simply can't be parsed. Each stream out of a binary vector must be done so with a finite count of bytes. Would it make sense to implement these objects in terms of the IOstream facilities provided by boost? I know these were designed to make defining stream classes easier, but honestly I don't have a lot of experience with them. Any feedback on this? Thanks in advance. I can provide some example code if needed.

2 2

Cross compiling boost (context, coroutine, filesystem, and system libraries) on ubuntu 64-bit for windows 32-bit (running on intel atom e3845 that is x86-64 bit)
by Jack Kumba 31 Jan '17

31 Jan '17

Hello, I want to cross compile context, coroutine, filesystem, and system libraries of boost for windows 32-bit (running on Intel Atom E3845) on my ubuntu 64-bit. To do that, I create a user-config.jam file in my homedirecotry and put the following: using gcc : mingw : i686-w64-mingw32-g++ : <compileflags>-m32 <linkflags>-m32 ; then, I would like to run following command: b2 --with-context --with-coroutine --with-system --with-filesystem --prefix=/home/jagdish/COMMELEC/prerequisits/real_boost_installation_dir/ toolset=gcc-mingw target-os=windows variant=release link=static address-model=32 runtime-link=static threading=multi architecture=x86 instruction-set=x86 abi=ms install is it good? Specifically, the options architecture, instruction-set, address-model? thanks in advance for your help. best, jack

1 0

[thread] understanding multiple statically-linked boost::thread in same process
by Simon Haegler 31 Jan '17

31 Jan '17

hi boost users, i am debugging an application where several shared libraries contain statically-linked copies of boost::thread (and other boost components). this means the static part of boost::thread is multiple times present in the process. on macos (apple clang 7.3) we see rare (but reproducible) access violations caused by boost::thread_specific_ptr::get() unexpectedly returning nullptr. if we enable assertions we get an assert in thread.cpp:151 if we dynamically link boost the problems go away. i can superficially understand that linking only one "common" instance of boost::thread is "more safe". what could be the explanation for this observation? is this setup even supported? one theory is that the implementations in pthread/thread_heap_alloc.hpp interfere with each other... the specific line where we get an unexpected nullptr (actually a bad reference) is here: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_CGAL_cgal_b… the definition of CGAL_STATIC_THREAD_LOCAL_VARIABLE is here?: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_CGAL_cgal_b… boost version is 1.59 TIA, simon -- Simon Haegler | Software Engineer Esri R&D Center Zurich | Foerrlibuckstrasse 110 | 8005 Zurich | Switzerland T +41 44 204 60 80 | shaegler(a)esri.com

3 3

C++Now 2017 Registration is Open
by Jon Kalb 31 Jan '17

31 Jan '17

Boost Users, Registration for C++Now 2017 is now open: http://bit.ly/CppNow2017IsOpen The conference will be in Aspen, Colorado from May 15th to 20th. The deadline for submissions is this Friday: http://cppnow.org/2017-conference/announcements/2017/01/06/call-for-submiss… Jon

1 0

Re: [Boost-users] [boost::asio] Wait for multiple async_read()'s
by Marat Abrarov 30 Jan '17

30 Jan '17

Hi Adam, > I'd like to write data to these streams then wait for everyone to reply before performing computation on the resulting data. What about Chris's coinvoke (http://blog.think-async.com/2008/10/asynchronous-forkjoin-using-asio.html)? Could it help for you case? Regards, Marat Abrarov.

1 0

[preprocessor]how to compute include with .hpp in name?
by Larry Evans 28 Jan '17

28 Jan '17

With the attached, I get the error: g++ computed_include.hpp.cpp -o a.out In file included from computed_include.hpp.cpp:4:0: computed_include.hpp.cpp:5:22: error: pasting "computed_include" and "." does not give a valid preprocessing token #define FILENAME_INC computed_include ^ computed_include.hpp.cpp:7:58: note: in expansion of macro ‘FILENAME_INC’ #define FILENAME_CAT_STR BOOST_PP_STRINGIZE(BOOST_PP_CAT(FILENAME_INC,HPP_EXT)) ^ computed_include.hpp.cpp:8:10: note: in expansion of macro ‘FILENAME_CAT_STR’ #include FILENAME_CAT_STR ^ Is there some other way this can be done? TIA. -regards, Larry

1 0

[boost::asio] Wait for multiple async_read()'s
by Adam Zegelin 28 Jan '17

28 Jan '17

Hi, I'm writing a boost::asio application that communicates with multiple streams. I'd like to write data to these streams then wait for everyone to reply before performing computation on the resulting data. What is the best way to implement this? The route I've ventured down involves me calling async_write() on each stream, with the callback hander executing async_read(). But this where I'm stuck. What is the best way to execute one final hander once all read operations have completed? One solution I've found, though it feels "un-asio" is to pass the use_future option as the hander for the reads. The result is futures for each read, which I can then place into a list<future>, and have an additional io_service.post()'ed handler call get() on these futures. The only issue with this is that I must call io_service.run() from more than one thread, since the handler calling get() blocks — otherwise I can potentially deadlock the whole application. Another alternative I can think of is that the function that schedules all the async_writes knows ahead-of-time the number of reads that need to be completed. Each async_read() handler would put its results into a shared list and then, if the list's size is equal to the expected number of results, fires the "completion" handler. While easy enough to implement, this seems fraught with issues. If there is more than one thread calling io_service.run(), then access to the shared list has to be synchronised. Also, it doesn't seem very generic — I have a number of places where this write n, read n, execute (or is it map, reduce?) pattern needs to happen, and I'd prefer a solution that was write one, worked everywhere. Any help would be appreciated. - Adam

7 9

[Parameter] Warnings from Preprocessor
by Phillip Seaver 27 Jan '17

27 Jan '17

I recently updated to 1.63 from 1.57, and I'm now getting warnings from usages of BOOST_PARAMETER_MEMBER_FUNCTION on Windows (msvc-12.0) like: warning C4003: not enough actual parameters for macro 'BOOST_PP_SEQ_DETAIL_EMPTY_SIZE' warning C4003: not enough actual parameters for macro 'BOOST_PP_SEQ_DETAIL_IS_NOT_EMPTY' The code appears to be working, but since it's used in headers, I get a lot of warnings. Here's one of the usages: BOOST_PARAMETER_MEMBER_FUNCTION((Revision_t), CreateForegroundWhite, tag, (optional (imgclass, (Class_t), ClassPrint) (fromimage, (bool), true) (blackasgray, (bool), false) )) Should I be concerned about the warnings? Any way to get rid of them? Thanks, Phillip

2 2

Fwd: compiling boost for windows 32 on ubuntu 64 machine
by Jack Kumba 27 Jan '17

27 Jan '17

Hello, I'm trying to compile boost for windows 32-bit on my ubuntu-64 but I'm not able to. what I do is as follows: - I created a file called user-config.jam in my ubuntu home directory and had put the below in it using gcc : : "i686-w64-mingw32-g++" - then, i run ./bootstrap.sh --with-libraries=filesystem --prefix=/home/jagdish/ commelec_api/installation_dirs/boost - and then, b2 toolset=gcc target-os=windows - finally, i see the following error messages: https://thepasteb.in/p/ y8h6q5Qq1yzcO Did someone encounter the same error messages or can tell me why I'm seeing them? Thanks, Kja

1 0

Re: [Boost-users] NEWBIE: Undefined references: How do I find the library that resolves an undefined reference - Expanded with log example and hope for a general solution
by JENNINGS, LYNN M NH-03 USAF AFMC 517 SMXS/MXDPB 26 Jan '17

26 Jan '17

Thanks again Andy! I am sending this note to thank Andy for his gracious help and to document the resolution for future newbies. Andy's suggestion to "nm -Cg" the boost.log directories was just what I needed! (Sorry, I should have remembered the -C option when I got nothing but garbage.) What I found was that the header files I use, generate a reference to ...::v2s_mt_nt5::..., while the libraries only define the namespace with ...::v2_mt_nt5::... For example, my code has the following: #include <boost\log\core.hpp> #include <boost\log\trivial.hpp> #include <boost\log\expressions.hpp> #include <boost\log\utility\setup\file.hpp> #include <boost\log\utility\setup\common_attributes.hpp> namespace logging = boost::log ; namespace src = boost::log::sources ; namespace keywords= logging::keywords ; namespace sinks = boost::log::sinks ; void init_logger() { logging::add_file_log( "sample.log", keywords::rotation_size = 10 * 1024 * 1024, keywords::time_based_rotation = sinks::file::rotation_at_time_point(0,0,0), keywords::format = "[%TimeStamp%]: %Message%", keywords::auto_flush=true ) ; logging::core::get()->set_filter (logging::trivial::severity >= logging::trivial::info ) ; logging::core::get()->add_global_attribute("TimeStamp", boost::log::attributes::local_clock()); } ... I compiled with the following command from my makefile: cc -g -DCPU=PENTIUM -DMC68000 -DDoing2VxWorks -IC:\boost -I../source -I../include -MMD -MP -c -o obj\logLib.o logLib.cpp Which I built with the following command from my makefile: cc -g -DCPU=PENTIUM -DMC68000 -DDoing2VxWorks -IC:\boost -I../source -I../include -MMD -MP -c -o obj\logLib.o logLib.cpp gfortran -o unit01test.exe obj\unit01test.o ..\mcpmain\obj\rtinit.o ..\mcpmain\obj\bite2.o ..\mcpmain\obj\bmain.o ..\mcpmain\obj\keypm2.o ..\mcpmain\obj\ksvc.o ..\mcpmain\obj\scen1.o ..\mcpmain\obj\disup.o ..\mcpmain\obj\idisup.o ..\mcpmain\obj\keyin.o ..\mcpmain\obj\disdr.o ..\mcpmain\obj\led_task.o ..\mcpmain\obj\spip_task.o ..\mcpmain\obj\iff_task.o ..\mcpmain\obj\inmsgmgr.o ..\mcpmain\obj\cppmainUnit01Test.o ..\runhistory\obj\rhlog_api.o ..\utilities\obj\main2aux.o ../../vxWorksLib/vxWorksLib/vxWorks/source/obj\logLib.o ../../vxWorksLib/vxWorksLib/vxWorks/source/obj\msgQlib.o ../../vxWorksLib/vxWorksLib/vxWorks/source/obj\pciConfigLib.o ../../vxWorksLib/vxWorksLib/vxWorks/source/obj\semLib.o ../../vxWorksLib/vxWorksLib/vxWorks/source/obj\sharedMemLib.o ../../vxWorksLib/vxWorksLib/vxWorks/source/obj\sockLib.o ../../vxWorksLib/vxWorksLib/vxWorks/source/obj\sysLib.o ../../vxWorksLib/vxWorksLib/vxWorks/source/obj\taskLib.o ../../vxWorksLib/vxWorksLib/vxWorks/source/obj\wdLib.o -LC:\boost\stage\lib -lboost_log_setup-mgw48-mt-d-1_61 -lboost_log-mgw48-mt-d-1_61 -lboost_thread-mgw48-mt-d-1_61 -lboost_system-mgw48-mt-d-1_61 -LC:\Windows\SysWOW\en-US -lws2_32 -lstdc++ -lboost_log_setup-mgw48-mt-d-1_61 -lboost_log-mgw48-mt-d-1_61 which gives me the error: ../../vxWorksLib/vxWorksLib/vxWorks/source/obj\logLib.o: In function `Z11init_loggerv': c:\1PortMUTES2MinGW\ProjectRepository-Build\vxWorksLib\vxWorksLib\vxWorks\source/logLib.cpp:16: undefined reference to `boost::log::v2s_mt_nt5::sinks::file::rotation_at_time_point::rotation_at_time_point(unsigned char, unsigned char, unsigned char)' But when I check the nm output, I find the following ::v2_mt_nt5:: namespace defined in all of the various forms of the Boost log libraries: d000608.o: U _head_libboost_log_mgw48_mt_d_1_61_dll 00000000 I _imp___ZNK5boost3log9v2_mt_nt55sinks4file25rotation_at_time_intervalclEv 00000000 T boost::log::v2_mt_nt5::sinks::file::rotation_at_time_interval::operator()() const I built my boost libraries using the directions for a MinGW build. I built my code using the same MinGW framework. However, I found the reason for the two conflicting name spaces, v2_mt_nt5 and v2s_mt_nt5 at: http://www.boost.org/doc/libs/1_56_0/libs/log/doc/html/log/rationale/namesp… The magic key is to recognize the <linkage> name space. I resolved most of my Boost log problem by adding -DBOOST_ALL_DYN_LINK to the compile operation. The correct compile command is: cc -g -DCPU=PENTIUM -DMC68000 -DDoing2VxWorks - DBOOST_ALL_DYN_LINK -IC:\boost -I../source -I../include -MMD -MP -c -o obj\logLib.o logLib.cpp Note that I was able to resolve my remaining errors where gcc just listed the mangled symbol by grep'ing the library file.

1 0

boostcpp.jam: No such file or directory
by JIA Pei 26 Jan '17

26 Jan '17

Hi, all: It seems boost has changed a lot in building? I strictly followed boost *Getting Started on Windows* but when I tried to install boost using command *b2 *. I got the following error messages: D:\boost_1_63_0>C:\boost\bin\b2.exe --build-dir=C:\boost toolset=msvc > --build-type=complete stage > *boostcpp.jam: No such file or directory* > Jamroot:137: in modules.load > ERROR: rule "boostcpp.set-version" unknown in module > "Jamfile<D:\boost_1_63_0>". > D:/boost_1_63_0/tools/build/src/build\project.jam:325: in load-jamfile > D:/boost_1_63_0/tools/build/src/build\project.jam:64: in load > D:/boost_1_63_0/tools/build/src/build\project.jam:145: in project.find > D:/boost_1_63_0/tools/build/src\build-system.jam:535: in load > D:\boost_1_63_0\tools\build\src/kernel\modules.jam:295: in import > D:\boost_1_63_0\tools\build\src/kernel/bootstrap.jam:139: in boost-build > D:\boost_1_63_0\boost-build.jam:17: in module scope > D:\boost_1_63_0> Did anybody meet this issue as well? Most of the time, I work under Linux, which seems to be more convenient.... Cheers -- Pei JIA, Ph.D. Email: jp4work(a)gmail.com cell in Canada: +1 778-863-5816 cell in China: +86 186-8244-3503 Welcome to Vision Open http://www.visionopen.com

1 0

Re: [Boost-users] NEWBIE: Undefined references: How do I find the library that resolves an undefined reference - Expanded with log example and hope for a general solution
by JENNINGS, LYNN M NH-03 USAF AFMC 517 SMXS/MXDPB 26 Jan '17

26 Jan '17

Thanks Richard and Andy for the timely response! Andy's answers provides the perfect example of my dilemma. When Andy said to check the MSDN documentation for ms742213, I quickly found that I needed the Ws2_32.lib library, which I was able to solve my issue. However, I also have the following: 1. boost::log::add_log_file(...) with a sinks::file::rotation_at_time_point(...) 2. boost::random::random_device range; I made a guess with the log and added boost_log_setup_mgw48-mt-d-1_61 and boost_log_ mgw48-mt-d-1_61, but these libraries didn't resolve my issue. When I check the boost documentation (I realize that many of the boost additions just require header files, which the examples are careful to specify. I figure this must require a library because I am getting an undefined error.), there were many mentions of a library, but I couldn't find where the name of the library was specified! So I hope there is a general way to determine the name of the boost library so I do not need to keeping asking about particular undefined errors. In the past, I have been able to google the undefined error and find the library reference, but Thanks again for all of your help! -----Original Message----- On 1/24/2017 3:44 PM, Richard Hodges wrote: > That would be the winsock library. > > https://msdn.microsoft.com/en-us/library/ms740673.aspx > > > > On 24 January 2017 at 20:33, JENNINGS, LYNN M NH-03 USAF AFMC 517 > SMXS/MXDPB <lynn.jennings_at_[hidden]> wrote: > >> 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_at_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! In the future, you can check Microsoft's documentation [1] for info on their functions. I searched for "WSAStartup", and found [2]. At the bottom of that page is a "Requirements" box, which tells you the library it's in. Andy 1. http://msdn.microsoft.com 2. https://msdn.microsoft.com/en-us/library/windows/desktop/ms742213(v=vs.85).…

2 1

circular_buffer: rotate() vs erase_begin() for scalars
by Robert Dailey 25 Jan '17

25 Jan '17

I'm using circular_buffer to represent a FIFO queue of bytes: boost::circular_buffer<std::uint8_t> m_queue; When I read bytes from the "front", I simply do: m_queue.erase_begin(num_read_bytes); I do so because the documentation for erase_begin() specifically mentions constant time performance for scalar types since no destructor needs to be called. However, I feel that rotate() better expresses what I'm trying to do. Is there a reason to prefer one over the other for scalar types?

2 3

C++Now / BoostCon 2017 -- Call For Submissions
by Michael Caisse 23 Jan '17

23 Jan '17

This is a quick reminder that the C++Now 2017 Call For Submissions is *open*. All submissions must be made by February 3rd. For more information, see http://cppnow.org/

1 0

How to build Boost with Clang/libc++ and NOT link against libstdc++?
by Deniz Bahadir 20 Jan '17

20 Jan '17

Hi guys, I am struggling with building the Boost (1.58.0) libraries with Clang (3.8) and libc++ (on Ubuntu 16.04). I am able to build the Boost libraries using Clang and flags "-std=c++14 -stdlib=libc++", however, I noticed that several libraries are still linked against GCC's standard-library "libstdc++". I then tried adding the flag "-lc++abi" (later I tried "-Wl,-lc++abi") to Boost.Build options "cxxflags" and "linkflags" to explicitly link against "libc++abi". With no luck. Several boost-libraries are still linked against "libstdc++". Does anyone know how and why this link-dependency gets added and how to get rid of them? Does it come in through some other link-dependencies? At least none of them seem to link to "libstdc++"? The Boost shared-libraries that link to "libstdc++" are: libboost_chrono-clang38-mt-1_58_0.so.1.58.0 libboost_context-clang38-mt-1_58_0.so.1.58.0 libboost_coroutine-clang38-mt-1_58_0.so.1.58.0 libboost_date_time-clang38-mt-1_58_0.so.1.58.0 libboost_filesystem-clang38-mt-1_58_0.so.1.58.0 libboost_graph-clang38-mt-1_58_1.so.0.58.0 libboost_iostreams-clang38-mt-1_58_0.so.1.58.0 libboost_locale-clang38-mt-1_58_0.so.1.58.0 libboost_log-clang38-mt-1_58_0.so.1.58.0 libboost_log_setup-clang38-mt-1_58_0.so.1.58.0 libboost_math_tr1-clang38-mt-1_58_0.so.1.58.0 libboost_math_tr1f-clang38-mt-1_58_0.so.1.58.0 libboost_math_tr1l-clang38-mt-1_58_0.so.1.58.0 libboost_program_options-clang38-mt-1_58_0.so.1.58.0 libboost_python-clang38-mt-1_58_0.so.1.58.0 libboost_random-clang38-mt-1_58_0.so.1.58.0 libboost_regex-clang38-mt-1_58_0.so.1.58.0 libboost_signals-clang38-mt-1_58_0.so.1.58.0 libboost_thread-clang38-mt-1_58_0.so.1.58.0 libboost_timer-clang38-mt-1_58_0.so.1.58.0 libboost_unit_test_framework-clang38-mt-1_58_0.so.1.58.0 libboost_wave-clang38-mt-1_58_0.so.1.58.0 The once that are fine and do not link against "libstdc++" are: libboost_atomic-clang38-mt-1_58_0.so.1.58.0 libboost_container-clang38-mt-1_58_0.so.1.58.0 libboost_math_c99-clang38-mt-1_58_0.so.1.58.0 libboost_math_c99f-clang38-mt-1_58_0.so.1.58.0 libboost_math_c99l-clang38-mt-1_58_0.so.1.58.0 libboost_serialization-clang38-mt-1_58_0.so.1.58.0 libboost_system-clang38-mt-1_58_0.so.1.58.0 libboost_wserialization-clang38-mt-1_58_0.so.1.58.0 Interestingly, all libraries are also linked against "libc++abi" except for: libboost_atomic-clang38-mt-1_58_0.so.1.58.0 libboost_container-clang38-mt-1_58_0.so.1.5 For completeness, my build-command is this: cd /home/jenkins/workspace/Pipeline_Boost/sources/boost_1_58_0 LINK_LIBCXXABI="-Wl,-lc++abi" COMMON_COMPILER_FLAGS="-m64 -fpic -fdiagnostics-color=always -O3" CFLAGS="$COMMON_COMPILER_FLAGS" CXXFLAGS="$COMMON_COMPILER_FLAGS -std=c++14 -stdlib=libc++ -isystem/usr/include/libcxxabi $LINK_LIBCXXABI" CC=/usr/bin/clang-3.8 CXX=/usr/bin/clang++-3.8 /home/jenkins/workspace/Pipeline_Boost@3/clang38/build/boost-build/b2 -j1 -q \ --build-dir=/home/jenkins/workspace/Pipeline_Boost@3/clang38/build/boost \ --build-type=minimal --layout=versioned address-model=64 install \ --prefix=/home/jenkins/workspace/Pipeline_Boost@3/clang38/installed/opt/BENOCS/clang38 \ --libdir=/home/jenkins/workspace/Pipeline_Boost@3/clang38/installed/opt/BENOCS/clang38/lib/x86_64-linux-gnu \ dll-path==/opt/BENOCS/clang38/lib/x86_64-linux-gnu \ toolset=clang-3.8 \ cflags="$CFLAGS" CXXFLAGS="$CXXFLAGS" \ linkflags="-Wl,--as-needed $LINK_LIBCXXABI" For the environment-variable LINK_LIBCXXABI I tried "-lc++abi" as well and also tried providing it only in the cxxflags or the linkflags or both (as above). I would be happy, if anyone could explain that behavior or could even provide a workaround/fix for me, so that "libstdc++" is no longer linked. Thanks, Deniz PS: BTW, does anyone know if it is correct, that shared libraries (in general) that are linked against "libc++abi" do always also link to "libgcc_s"? (What is it for?) -- BENOCS GmbH Dipl.-Inform. Deniz Bahadir Winterfeldtstr. 21 10781 Berlin Germany Phone: +49 - 30 / 577 0004-22 Email: deniz.bahadir(a)benocs.com www.benocs.com Board of Management: Michael Wolz, Dr.-Ing. Oliver Holschke, Dr.-Ing. Ingmar Poese Commercial Register: Amtsgericht Bonn HRB 19378

2 2

Fwd: Boost coroutine/context libraries
by Gregory Laird 20 Jan '17

20 Jan '17

--------------- Forwarded message (begin) Subject: Boost coroutine/context libraries From: Gregory Laird <glaird(a)northgatebowl.com> Date: Tue, 17 Jan 2017 17:10:57 -0800 Newsgroup: gmane.comp.lib.boost.user I am trying to write a cooperative task scheduler in c++ and I have discovered the boost context and coroutine libraries. I have written these sorts of schedulers many times in assembly language so I appreciate the issues in the methodology. I have written lots of c code but am less versed in c++. I have been trying to find some straightforward examples of the libraries use without a lot of extraneous c++ language elements (e.g. binds, lambdas, etc.). I did find one example http://stackoverflow.com/questions/11716291/boost-context-class that is very nice, but it will not compile now with the current boost library. I get an error saying that boost::context::fcontext_t has been removed from the public api. Could someone direct me to some examples that demonstrate the context or coroutine functionality that would be easier to understand. I want to write a scheduler that is very similar to the example listed above where coroutines yeild back to a main caller which then chooses the next coroutine to continue its processing. Thanks. --------------- Forwarded message (end)

5 6

Program abort at canonical()
by Andy 20 Jan '17

20 Jan '17

I have: #include <boost/filesystem/path.hpp> #include <boost/filesystem/operations.hpp> boostPath = canonical(boostPath); While I debug it is OK, but when I run debug or release x64 program standalone from cmd - it abort at canonical without any info.

4 6

Multiprecision -- cubing a number gives unexpected result
by Craig Henderson 19 Jan '17

19 Jan '17

Hello, I am new to Boost.Multiprecision and have come across a result that I cannot understand. I have the following code to calculate the sum of three cubes, using bigint_t = boost::multiprecision::mpz_int; bigint_t a = 2220422932; bigint_t b = 2218888517; b = -b; bigint_t c = 283059965; c = -c; std::cout << '(' << a << ")^3+(" << b << ")^3+(" << c << ")^3 = "; bigint_t a1 = a * a * a; bigint_t b1 = b * b * b; bigint_t c1 = c * c * c; std::cout << '(' << a1 << ")+(" << b1 << ")+(" << c1 << ") = "; std::cout << bigint_t(a1+b1+c1) << '\n'; and it produces the correct result (2220422932)^3+(-2218888517)^3+(-283059965)^3 = (10947302325566084787191541568)+(-10924622727902378924946084413)+(-22679597663705862245457125) = 30 However, if I use this implementation, with a,b and c assigned the result of the multiplication, a = a * a * a; b = b * b * b; c = c * c * c; std::cout << '(' << a << ")+(" << b << ")+(" << c << ") = "; std::cout << bigint_t(a+b+c) << '\n'; ... I get a very strange result: (24307641127223864542936438774018437376)+(24240519923499804093545671548118385521)+(6419686120902663137493915211500625) = 48554580736844571299619604237348323522 What is going on? Is this an invalid use of the multiplication that I have missed? I get the same result with cpp_int and gmp; using bigint_t = boost::multiprecision::cpp_int; using bigint_t = boost::multiprecision::mpz_int; I'm using g++ (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609, Boost 1.58 Many thanks Craig

2 1

[Boost.Math] Weird compiler-error with Clang 3.8
by Deniz Bahadir 19 Jan '17

19 Jan '17

Hi guys, Our build-server (Jenkins) tried to build Boost 1.58 with Clang 3.8 and libc++ and tripped over an error that I do not understand. Maybe someone can shed some light on it? The specific error is this: clang-linux.compile.c++.pch /home/jenkins/workspace/Pipeline_Boost@3/clang38/build/boost/boost/bin.v2/libs/math/build/clang-linux-3.8/release/threading-multi/../src/tr1/pch.hpp.pth clang: error: cannot specify -o when generating multiple output files Does this look familiar to anyone? My build-environment is Ubuntu 16.04 x86_64 and I invoked Boost.Build like this: cd /home/jenkins/workspace/Pipeline_Boost/sources/boost_1_58_0 COMMON_COMPILER_FLAGS="-m64 -fpic -fdiagnostics-color=always -O3" CFLAGS="$COMMON_COMPILER_FLAGS" CXXFLAGS="$COMMON_COMPILER_FLAGS -std=c++14 -stdlib=libc++ -isystem/usr/include/libcxxabi -lc++abi" CC=/usr/bin/clang-3.8 CXX=/usr/bin/clang++-3.8 /home/jenkins/workspace/Pipeline_Boost@3/clang38/build/boost-build/b2 -j1 -q \ --build-dir=/home/jenkins/workspace/Pipeline_Boost@3/clang38/build/boost \ --build-type=minimal --layout=versioned address-model=64 install \ --prefix=/home/jenkins/workspace/Pipeline_Boost@3/clang38/installed/opt/BENOCS/clang38 \ --libdir=/home/jenkins/workspace/Pipeline_Boost@3/clang38/installed/opt/BENOCS/clang38/lib/x86_64-linux-gnu \ dll-path==/opt/BENOCS/clang38/lib/x86_64-linux-gnu \ toolset=clang-3.8 \ cflags="$CFLAGS" CXXFLAGS="$CXXFLAGS" linkflags="-Wl,--as-needed" The more detailed error-message is the following: common.mkdir /home/jenkins/workspace/Pipeline_Boost(a)3/clang38/build/boost/boost/bin.v2/libs/math/build common.mkdir /home/jenkins/workspace/Pipeline_Boost@3/clang38/build/boost/boost/bin.v2/libs/math/build/clang-linux-3.8 common.mkdir /home/jenkins/workspace/Pipeline_Boost@3/clang38/build/boost/boost/bin.v2/libs/math/build/clang-linux-3.8/release common.mkdir /home/jenkins/workspace/Pipeline_Boost@3/clang38/build/boost/boost/bin.v2/libs/math/build/clang-linux-3.8/release/threading-multi common.mkdir /home/jenkins/workspace/Pipeline_Boost@3/clang38/build/boost/boost/bin.v2/libs/math/build/clang-linux-3.8/release/threading-multi/.. common.mkdir /home/jenkins/workspace/Pipeline_Boost@3/clang38/build/boost/boost/bin.v2/libs/math/build/clang-linux-3.8/release/threading-multi/../src common.mkdir /home/jenkins/workspace/Pipeline_Boost@3/clang38/build/boost/boost/bin.v2/libs/math/build/clang-linux-3.8/release/threading-multi/../src/tr1 clang-linux.compile.c++.pch /home/jenkins/workspace/Pipeline_Boost@3/clang38/build/boost/boost/bin.v2/libs/math/build/clang-linux-3.8/release/threading-multi/../src/tr1/pch.hpp.pth clang: error: cannot specify -o when generating multiple output files rm -f "/home/jenkins/workspace/Pipeline_Boost@3/clang38/build/boost/boost/bin.v2/libs/math/build/clang-linux-3.8/release/threading-multi/../src/tr1/pch.hpp.pth" && "clang++" -x c++-header -m64 -fpic -fdiagnostics-color=always -O3 -std=c++14 -stdlib=libc++ -isystem/usr/include/libcxxabi -lc++abi -m64 -fpic -fdiagnostics-color=always -O3 -O3 -Wno-inline -Wall -pthread -fPIC -m64 -m64 -fpic -fdiagnostics-color=always -O3 -std=c++14 -stdlib=libc++ -isystem/usr/include/libcxxabi -lc++abi -m64 -fpic -fdiagnostics-color=always -O3 -DBOOST_ALL_NO_LIB=1 -DBOOST_BUILD_PCH_ENABLED -DBOOST_MATH_TR1_DYN_LINK=1 -DNDEBUG -I"." -I"libs/math/src/tr1" -Xclang -emit-pth -o "/home/jenkins/workspace/Pipeline_Boost@3/clang38/build/boost/boost/bin.v2/libs/math/build/clang-linux-3.8/release/threading-multi/../src/tr1/pch.hpp.pth" "libs/math/build/../src/tr1/pch.hpp" ...failed clang-linux.compile.c++.pch /home/jenkins/workspace/Pipeline_Boost@3/clang38/build/boost/boost/bin.v2/libs/math/build/clang-linux-3.8/release/threading-multi/../src/tr1/pch.hpp.pth... ...skipped <p/home/jenkins/workspace/Pipeline_Boost@3/clang38/build/boost/boost/bin.v2/libs/math/build/clang-linux-3.8/release/threading-multi>assoc_laguerre.o for lack of <p/home/jenkins/workspace/Pipeline_Boost@3/clang38/build/boost/boost/bin.v2/libs/math/build/clang-linux-3.8/release/threading-multi>../src/tr1/pch.hpp.pth... ...failed updating 1 target... ...skipped 1 target... ...updated 11871 targets... Can someone tell me what is going on and how to fix or work around this problem? Thanks, Deniz -- BENOCS GmbH Dipl.-Inform. Deniz Bahadir Winterfeldtstr. 21 10781 Berlin Germany Phone: +49 - 30 / 577 0004-22 Email: deniz.bahadir(a)benocs.com www.benocs.com Board of Management: Michael Wolz, Dr.-Ing. Oliver Holschke, Dr.-Ing. Ingmar Poese Commercial Register: Amtsgericht Bonn HRB 19378

3 4

Re: [Boost-users] Fwd: Boost coroutine/context libraries
by Nat Goodspeed 19 Jan '17

19 Jan '17

On Jan 18, 2017 2:39 PM, "Gregory Laird" <glaird(a)northgatebowl.com> wrote: Question: If I allocate too small of a stack, and something gets written outside of the allocation, is there any way to know that this has occurred? http://www.boost.org/doc/libs/1_63_0/libs/context/doc/html/context/stack/pr…

1 0

1.63.0: diffenre package with the same version
by Ivan Kabaivanov 15 Jan '17

15 Jan '17

Hi, first time poster here. I've been compiling boost from source for about 8 years now. I download the packages from sourceforge.net (https://sourceforge.net/projects/boost/files/boost/1.63.0/) Lately (last few releases) I notice a troubling trend -- the same package, say boost_1_63_0.tar.bz2 will have a different md5 hash if downloaded again a few weeks after being downloaded for the first time. Case in point: boost_1_63_0.tar.bz2, downloaded around Fri Dec 30 17:11:50 2016 +0200 (GMT+2) had md5 hash d17537e28aa2131fa192ce2870ce72a3. The very same file, dowloaded today (January 15, 2017) has a new md5 hash: 1c837ecd990bb022d07e7aab32b09847. What's more troubling is that a cursory comparison of the two files' contents reveals differences. To begin with, the old package had 53599 files, while the new one has 53655. Further, files that are present in both packages have small differences. $ diff -Naur ../../OLD/boost_1_63_0/./libs/numeric/odeint/doc/html/boost/numeric/odeint/base_tag.html ../../NEW/boost_1_63_0/./libs/numeric/odeint/doc/html/boost/numeric/odeint/base_tag.html--- ../../OLD/boost_1_63_0/./libs/numeric/odeint/doc/html/boost/numeric/odeint/base_tag.html 2016-12-29 17:12:21.000000000 +0200+++ ../../NEW/boost_1_63_0/./libs/numeric/odeint/doc/html/boost/numeric/odeint/base_tag.html 2016-12-22 14:47:46.000000000 +0200@@ -7,7 +7,7 @@ <link rel="home" href="../../../index.html" title="Chapter 1. Boost.Numeric.Odeint"> <link rel="up" href="../../../header/boost/numeric/odeint/stepper/stepper_categories_hpp.html" title="Header <boost/numeric/odeint/stepper/stepper_categories.hpp>"> <link rel="prev" href="dense_output_stepper_tag.html" title="Struct dense_output_stepper_tag">-<link rel="next" href="base_tag_stepp_idp64335824.html" title="Struct base_tag<stepper_tag>">+<link rel="next" href="base_tag_stepp_idp34699008.html" title="Struct base_tag<stepper_tag>"> </head> <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> <table cellpadding="2" width="100%"><tr>@@ -20,7 +20,7 @@ </tr></table> <hr> <div class="spirit-nav">-<a accesskey="p" href="dense_output_stepper_tag.html"><img src="../../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../../../header/boost/numeric/odeint/stepper/stepper_categories_hpp.html"><img src="../../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="base_tag_stepp_idp64335824.html"><img src="../../../../../../../../doc/src/images/next.png" alt="Next"></a>+<a accesskey="p" href="dense_output_stepper_tag.html"><img src="../../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../../../header/boost/numeric/odeint/stepper/stepper_categories_hpp.html"><img src="../../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="base_tag_stepp_idp34699008.html"><img src="../../../../../../../../doc/src/images/next.png" alt="Next"></a> </div> <div class="refentry"> <a name="boost.numeric.odeint.base_tag"></a><div class="titlepage"></div>@@ -45,7 +45,7 @@ </tr></table> <hr> <div class="spirit-nav">-<a accesskey="p" href="dense_output_stepper_tag.html"><img src="../../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../../../header/boost/numeric/odeint/stepper/stepper_categories_hpp.html"><img src="../../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="base_tag_stepp_idp64335824.html"><img src="../../../../../../../../doc/src/images/next.png" alt="Next"></a>+<a accesskey="p" href="dense_output_stepper_tag.html"><img src="../../../../../../../../doc/src/images/prev.png" alt="Prev"></a><a accesskey="u" href="../../../header/boost/numeric/odeint/stepper/stepper_categories_hpp.html"><img src="../../../../../../../../doc/src/images/up.png" alt="Up"></a><a accesskey="h" href="../../../index.html"><img src="../../../../../../../../doc/src/images/home.png" alt="Home"></a><a accesskey="n" href="base_tag_stepp_idp34699008.html"><img src="../../../../../../../../doc/src/images/next.png" alt="Next"></a> </div> </body> </html> I know, these are trivial differences. But they are differences nevertheless and this is not acceptable for package maintainers. I've heard stories of how SourceForge is (or used to be ?) modifying packages to include crapware and sponsored content. So my first reaction was to suspect SF.net of pulling some stupid/shady stuff. But I'm beginning to wonder it it was SF.net really. Please, investigate what's happening and please fix it. As a package maintainer I can no longer vouchsafe for the integrity of the upstream package. Thanks,IvanK.

2 1

Problems Building Boost 1.63 on Solaris 11.3 x86 with Oracle Developer Studio12.5
by Shawn Firth 14 Jan '17

14 Jan '17

Ladies and Gentlemen, We have been using Boost on Windows and HP-UX for over five years. Recently I have been attempting to build Boost 1.63 on Solaris 11.3 x86 with Oracle Developer Studio12.5. I started with: ./bootstrap.sh --prefix=/export/home/me/boost_1_63_0 -libdir=/export/home/me/boost_1_63_0/lib --with-toolset=sun ...and that is where I still am. I have been trying every b2 option/configuration that I can file via Google to get Boost 1.63, both with and without C++11, and I am striking out. The Boost documentation is very terse on Sun builds, however the Boost 1.63 release notes say it has been tested for SunOS: Oracle Solaris Studio 12.5 and Oracle Solaris Studio, C++11 12.5. Here's all that the Boost 1.64 doco has to say about Sun builds: sun Oracle Only very recent versions are known to work well with Boost. Note that the Oracle/Sun compiler has a large number of options which effect binary compatibility: it is vital that the libraries are built with the same options that your appliction will use. In particular be aware that the default standard library may not work well with Boost, unless you are building for C++11. The particular compiler options you need can be injected with the b2 command line options cxxflags=``and ``linkflags=. For example to build with the Apache standard library in C++03 mode use b2 cxxflags=-library=stdcxx4 linkflags=-library=stdcxx4. http://www.boost.org/doc/libs/1_63_0/more/getting_started/unix-variants.html Sun Studio The sun module supports the Sun Studio<http://developers.sun.com/sunstudio/index.jsp> C++ compilers for the Solaris OS. The module is initialized using the following syntax: using sun : [version] : [c++-compile-command] : [compiler options] ; This statement may be repeated several times, if you want to configure several versions of the compiler. If the command is not specified, Boost.Build will search for a binary named CC in /opt/SUNWspro/bin and in PATH. When using this compiler on complex C++ code, such as the Boost C++ library<http://boost.org/>, it is recommended to specify the following options when intializing the sun module: -library=stlport4 -features=tmplife -features=tmplrefstatic See the Sun C++ Frontend Tales<http://blogs.sun.com/sga/entry/command_line_options> for details. The following options can be provided, using <option-name>option-value syntax: cflags Specifies additional compiler flags that will be used when compiling C sources. cxxflags Specifies additional compiler flags that will be used when compiling C++ sources. compileflags Specifies additional compiler flags that will be used when compiling both C and C++ sources. linkflags Specifies additional command line options that will be passed to the linker. Starting with Sun Studio 12, you can create 64-bit applications by using the address-model=64 property. http://www.boost.org/build/doc/html/bbv2/reference/tools.html#bbv2.referenc… Can someone provide me with the user-config.jam and b2 options so that I can successfully build Boost 1.63 on Solaris 11.3 x86 with Oracle Developer Studio12. 3, 4, or 5? Failing user-config.jam and b2 options for Solaris 11 on x86, can you provide me with user-config.jam and b2 options for Solaris 11 on SPARC with Oracle Developer Studio12.3, 4, or 5? Thank you for your time... Shawn Firth RG Technology Senior Systems Architect shawn.firth(a)robbinsgioia.com<mailto:shawn.firth@robbinsgioia.com> [Description: Description: RGG] www.robbinsgioia.com<http://www.robbinsgioia.com/> ________________________________ CONFIDENTIALITY NOTICE: The information contained in this electronic mail and its attachments are privileged and confidential information and are intended for the use of the individual(s) or entity named above and those who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any use, copying or distribution of this communication is strictly prohibited.

2 4

boost 1.63 fails to build with zlib and bzip2 in different directories
by Andrea Bocci 14 Jan '17

14 Jan '17

Hi, I'm trying to build custom binaries for boost 1.63 using zlib and bzip2 from a local installation rather than the system ones, following the instructions at http://www.boost.org/doc/libs/1_63_0/more/getting_started/unix-variants.htm… and http://www.boost.org/doc/libs/1_63_0/libs/iostreams/doc/installation.html but it looks like the build system does not like having the zlib and bzip2 libraries in different folders. Here's what I'm doing to set up the build environment: # create a common directory for zlib and bzip2 mkdir common # build zlib wget http://downloads.sourceforge.net/project/libpng/zlib/1.2.10/zlib-1.2.10.tar… tar xaf zlib-1.2.10.tar.xz cd zlib-1.2.10/ ./configure make test make install prefix=../common cd .. # build bzip2 wget http://www.bzip.org/1.0.6/bzip2-1.0.6.tar.gz tar xaf bzip2-1.0.6.tar.gz cd bzip2-1.0.6/ make -f Makefile-libbz2_so make test make install PREFIX=../common cp -ar libbz2.so.* ../common/lib/ cd .. # build boost wget https://sourceforge.net/projects/boost/files/boost/1.63.0/boost_1_63_0.tar.… tar xaf boost_1_63_0.tar.bz2 cd boost_1_63_0/ mkdir boost-build cd tools/build/ ./bootstrap.sh gcc ./b2 install --prefix=../../boost-build cd ../../ export PATH=$PWD/boost-build/bin:$PATH Now, if I tell boost to pick zlib and bzip2 from the common directory with b2 -q \ -d+2 \ --build-dir=build \ --stage-dir=stage \ --disable-icu \ --without-atomic \ --without-chrono \ --without-container \ --without-context \ --without-coroutine \ --without-exception \ --without-graph \ --without-graph_parallel \ --without-locale \ --without-log \ --without-math \ --without-mpi \ --without-random \ --without-wave \ toolset=gcc \ link=shared \ threading=multi \ variant=release \ cxxflags="-std=c++11 -O2" \ -sBZIP2_INCLUDE=../common/include \ -sBZIP2_LIBPATH=../common/lib \ -sZLIB_INCLUDE=../common/include \ -sZLIB_LIBPATH=../common/lib \ stage it works just fine. However, if I try to build boost using two separate directories for bip2 and zlib, with b2 -q \ -d+2 \ --build-dir=build \ --stage-dir=stage \ --disable-icu \ --without-atomic \ --without-chrono \ --without-container \ --without-context \ --without-coroutine \ --without-exception \ --without-graph \ --without-graph_parallel \ --without-locale \ --without-log \ --without-math \ --without-mpi \ --without-random \ --without-wave \ toolset=gcc \ link=shared \ threading=multi \ variant=release \ cxxflags="-std=c++11 -O2" \ -sBZIP2_INCLUDE=../bzip2-1.0.6 \ -sBZIP2_LIBPATH=../bzip2-1.0.6 \ -sZLIB_INCLUDE=../zlib-1.2.10 \ -sZLIB_LIBPATH=../zlib-1.2.10 \ stage the build fails with Performing configuration checks - 32-bit : no - 64-bit : yes - arm : no - mips1 : no - power : no - sparc : no - x86 : yes - symlinks supported : yes - C++11 mutex : yes - Boost.Config Feature Check: cxx11_auto_declarations : yes - Boost.Config Feature Check: cxx11_constexpr : yes - Boost.Config Feature Check: cxx11_defaulted_functions : yes - Boost.Config Feature Check: cxx11_final : yes - Boost.Config Feature Check: cxx11_hdr_mutex : yes - Boost.Config Feature Check: cxx11_hdr_tuple : yes - Boost.Config Feature Check: cxx11_lambdas : yes - Boost.Config Feature Check: cxx11_noexcept : yes - Boost.Config Feature Check: cxx11_nullptr : yes - Boost.Config Feature Check: cxx11_rvalue_references : yes - Boost.Config Feature Check: cxx11_template_aliases : yes - Boost.Config Feature Check: cxx11_thread_local : yes - Boost.Config Feature Check: cxx11_variadic_templates : yes - zlib : yes error: at /home/fwyzard/src/boost/boost_1_63_0/tools/build/src/kernel/modules.jam:107 error: Name clash for '<pbuild/boost/bin.v2/standalone/ac/gcc-5.4.1/release/threading-multi>main.o' error: error: Tried to build the target twice, with property sets having error: these incompatible properties: error: error: - <dll-path>../zlib-1.2.10 <library-path>../zlib-1.2.10 <xdll-path>../zlib-1.2.10 error: - <dll-path>../bzip2-1.0.6 <library-path>../bzip2-1.0.6 <xdll-path>../bzip2-1.0.6 error: error: Please make sure to have consistent requirements for these error: properties everywhere in your project, especially for install error: targets. I get a similar error if I specify only one of bzip and bzip2. For example Now, if I tell boost to pick zlib and bzip2 from the common directory with b2 -q \ -d+2 \ --build-dir=build \ --stage-dir=stage \ --disable-icu \ --without-atomic \ --without-chrono \ --without-container \ --without-context \ --without-coroutine \ --without-exception \ --without-graph \ --without-graph_parallel \ --without-locale \ --without-log \ --without-math \ --without-mpi \ --without-random \ --without-wave \ toolset=gcc \ link=shared \ threading=multi \ variant=release \ cxxflags="-std=c++11 -O2" \ -sZLIB_INCLUDE=../common/include \ -sZLIB_LIBPATH=../common/lib \ stage results in Performing configuration checks - 32-bit : no - 64-bit : yes - arm : no - mips1 : no - power : no - sparc : no - x86 : yes - symlinks supported : yes - C++11 mutex : yes - Boost.Config Feature Check: cxx11_auto_declarations : yes - Boost.Config Feature Check: cxx11_constexpr : yes - Boost.Config Feature Check: cxx11_defaulted_functions : yes - Boost.Config Feature Check: cxx11_final : yes - Boost.Config Feature Check: cxx11_hdr_mutex : yes - Boost.Config Feature Check: cxx11_hdr_tuple : yes - Boost.Config Feature Check: cxx11_lambdas : yes - Boost.Config Feature Check: cxx11_noexcept : yes - Boost.Config Feature Check: cxx11_nullptr : yes - Boost.Config Feature Check: cxx11_rvalue_references : yes - Boost.Config Feature Check: cxx11_template_aliases : yes - Boost.Config Feature Check: cxx11_thread_local : yes - Boost.Config Feature Check: cxx11_variadic_templates : yes - zlib : yes error: at /home/fwyzard/src/boost/boost_1_63_0/tools/build/src/kernel/modules.jam:107 error: Name clash for '<pbuild/boost/bin.v2/standalone/ac/gcc-5.4.1/release/threading-multi>main.o' error: error: Tried to build the target twice, with property sets having error: these incompatible properties: error: error: - <dll-path>../common/lib <library-path>../common/lib <xdll-path>../common/lib error: - none error: error: Please make sure to have consistent requirements for these error: properties everywhere in your project, especially for install error: targets. As far as I can tell, this used to work with boost 1.57 - I haven't tried any version in between. Anybody has any suggestions ? Thank you, .Andrea -- Strategy is a system of expedients. Generalfeldmarschall Helmuth Karl Bernhard Graf von Moltke

4 11

Boost 1.63.0 with VS 2017 RC
by csiga.biga＠aol.com 09 Jan '17

09 Jan '17

Hi there! There were attempts at building 1.62.0 with the new v141 toolset of MSVC and some success. Did 1.63 make any progress in this regard? I see that the final release still builds libraries labeled v140 even when using a dev cmd prompt with the new compiler. Cheers, Máté

1 0

msvc-14.0 xp support
by Li Sheng 06 Jan '17

06 Jan '17

Hello Boost community, I'm trying to compile boost *1.61.0* with following command on Windows 10 machine: bootstrap.bat b2 headers b2 -a -j9 --stagedir=./stage/boost-xp *toolset=msvc-11.0,msvc-14.0* threading=multi link=static runtime-link=static address-model=64 *define=_USING_V110_SDK71_ define=BOOST_USE_WINAPI_VERSION=0x0501* -d+2 --debug-building As described above, my chosen compilers are MSVC 11 and 14, and I want to enable xp support on produced libraries. Library files compiled by VC11 work fine, but VC14 files are not. Then I added "--debug-building" to see what's actually going on. My console log shows "Command line free features: _USING_V110_SDK71_, BOOST_USE_WINAPI_VERSION=0x0501" when toolset is "msvc-14.0". This does not occur when toolset is "msvc-11.0". After all, can anyone kindly help me with compile boost on msvc-14.0 with xp support? Please forgive me for asking this weird usage. Warmest regards and gratitude, ZD

1 0

[operators] Move Semantics
by Helmut Zeisel 05 Jan '17

05 Jan '17

1 0

[Python] Custom __getattr__ with different CallPolicy for different return values
by H Krishnan 04 Jan '17

04 Jan '17

Hi, I would like to custom __getattr__ for my class such that for some attributes, an internal reference is returned, and for others, a new object is returned. I cannot hardcode the attributes as they are dynamic. I started writing something like: boost::python::object myGetAttr(boost::python::object obj, std::string const& attr) { MyObj* mobj = boost::python::extract<MyObj*>(obj)(); if (attr == "internal_ref") { MyRef* refObj = mobj->getInternalRef(); // how do I return this? } else { MyValueObj obj = mobj->getValueObj(); // how do I return this? } } class_<MyObj, boost::noncopyable> ("MyObj", no_init) .def ("__getattr__", &myGetAttr, ???what_should_I_put_here???) ; However, I am not able to get this to work. Any suggestions? Regards, Krishnan

1 0

How to reuse system_timer of boost::asio with async_wait?
by Bruce 03 Jan '17

03 Jan '17

Hi, I am doing a program that use asio to construct a timer thread. The thread use asio to async_wait many timers. These timers are constructed by boost::asio::system_timer. These timers are mostly designed to fire only once. When they are fired or canceled, I put them to a free queue to reuse. But when I reuse these times, I called expire_from_now() and async_wait() again on the timer, I got the timer fired immediately with error_code set to "ec == boost::asio::error::operation_aborted". And the timer are not fired after like 5 seconds late as I set to expire_from_now(seconds(5)). How to reuse the timer correctly? My codes basically are as follows: m_timer.cancel(); // I tried to cancel the timer first, but no use, I still get the timer fired at once m_timer.expires_from_now(std::chrono::seconds(nInterval)); m_timer.async_wait(boost::bind(&qmInnerTimer::Fire, this, _1)); Thanks. -Bruce

1 0

Boost.Context: SIGSEGV when switch a thread within a catch block
by Александр Пронченков 02 Jan '17

02 Jan '17

Hi, I get SIGSEGV on macOS when I switch an execution_context from a catch block with one thread and than switch back with another thread. Segmentation fault happens in libc++abi.dylib`__cxa_end_catch Does anyone have any ideas, what it could be? Is it legal to switch thread under an excecution_context while it's within a catch block? A minimal example is here: #include <boost/context/all.hpp> #include <future> using Context = boost::context::execution_context<void>; Context Main(Context context) { try { throw std::runtime_error("123"); } catch (const std::exception& ex) { context = context(); } return context(); } int main() { Context context(&Main); context = context(); std::thread([&] { context = context(); }).join(); return 0; } I see the problem on macOS with clang++ but can't reproduce on a linux with g++. $ uname -ap Darwin air.local 16.3.0 Darwin Kernel Version 16.3.0: Thu Nov 17 20:23:58 PST 2016; root:xnu-3789.31.2~1/RELEASE_X86_64 x86_64 i386 $ clang++ --version Apple LLVM version 8.0.0 (clang-800.0.42.1) Target: x86_64-apple-darwin16.3.0 Thread model: posix InstalledDir: /Library/Developer/CommandLineTools/usr/bin -- Thanks, Alexander Pronchenkov

3 4

[Stacktrace] Review Manager report
by Niall Douglas 02 Jan '17

02 Jan '17

Firstly happy new year to everyone, and many thanks to all those who participated in the peer review of proposed Boost.Stacktrace before Christmas. I received the following formal reviews: 1. Vladimir Batov (YES) 2. Klemens Morgenstern (YES) 3. Andrey Semashev (NO) 4. Nat Goodspeed (YES) 5. Artyom Beilis (NO) 6. Barrett Adair (YES) Extensive comments without a formal acceptance recommendation were also made by: 1. Peter Dimov 2. Edward Diener There was a very noticeable lack of consensus on the strengths and weaknesses of the proposed library which has made summarising all these reviews into a coherent report with concrete conditions for acceptance very difficult. Antony also responded to many of the concerns throughout the review, agreeing with some points, disagreeing with others. I think this lack of consensus stemmed from multiple opinions on what a stacktrace library ought to provide: Minimum viable product: A portable backtrace() and backtrace_symbols() implementation with a C++ STL idiomatic API. The stack backtrace capture implementation must not allocate memory and be "fast". Note that backtrace_symbols() does NOT symbolise into strings containing source file name and line number. It also allocates memory (backtrace_symbols_fd() does not). Opinion 1: Portable serialisation of the stacktrace with instruction pointers converted to offsets into SO/DLL binary paths so a later external process can use those in combination with their debug symbols to retrieve source file names and line numbers. Ideally the serialisation formats supported would include those consumable by well known tooling for this purpose e.g. addr2line or llvm-symbolizer. Opinion 2: That Stacktrace can in process use debug symbols to retrieve source file names and line numbers. This could be implemented by invoking addr2line or equivalent as a child process which has the enormous advantage of being async safe, but has disadvantages in almost every other area. Or it could be implemented by one's own DWARF parser but with the huge caveat that memory could be badly corrupted by now. Opinion 3: That Stacktrace be "async safe" in that backtraces can be safely captured and parsed from a signal handler or SEH/TEH handler callback or point of C++ exception throw. *This implies no memory allocation during the execution of the handler*. >From the reviews, I think there is consensus that the minimum viable product is achieved in Stacktrace though many mentioned that improvements are needed to the documentation and most of the negative feedback was on features not in the minimum viable product described above. I therefore recommend the ACCEPTANCE of proposed Boost.Stacktrace into Boost with the following conditions: 1. That the documentation more clearly set out what Stacktrace does and especially does not do, and that the default facilities provided are those of the Minimum Viable Product described above i.e. no source file nor line number discovery, no external dependencies on libraries not always provided on the target platform, no invocation of child processes, no async safety during stacktrace parsing. Stacktrace ought to be pared back to the minimum viable product featureset with no external dependencies at all. 2. That suitable predefined macros opt in to additional functionality such as serialisation of offset translated backtraces, retrieval of source code path and line number etc. Enabling these may introduce dependencies on third party libraries not always present on a system such as libunwind, or on third party helper utilities such as addr2line. I would recommend that the APIs the use of which are dependent on such third party items are entirely compiled out of Stacktrace when the macro enabling them is not defined. 3. That the documentation describe ONLY the default minimum viable product functionality in its tutorial and quick start. All extra functionality enabled by macros is to be relocated into a separate documentation section away from the main documentation e.g. "Advanced/optional features". 4. That APIs made available only when a given macro has turned them on are documented as such in the API reference docs. I'd like to congratulate Antony on getting yet another library of his into Boost. I hope some of his magic rubs off on me when I bring Outcome to review later this year! Regards, Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

2 1

[log] disabling logging at compile-time
by Igor R 02 Jan '17

02 Jan '17

Is it possible to completely eliminate the logging code (i.e. the run-time overhead) using some macro? Thanks.

2 1

Problems with nesting boost::container::small_vector and C++98
by Daniel Trstenjak 02 Jan '17

02 Jan '17

Hi, first the used versions: boost 1.63.0 gcc 5.4.0 20160609 Ubuntu 16.04.1 the example I've problems with is: #include <map> #include <boost/container/small_vector.hpp> using boost::container::small_vector; typedef std::pair<int, small_vector<float, 8> > mypair; typedef std::map<int, mypair> mymap; typedef std::map<int, small_vector<mypair, 8> > mymap2; typedef std::map<int, small_vector<small_vector<float, 8>, 8> > mymap3; int main() { mymap m; mypair& sv = m[0]; mymap2 m2; small_vector<mypair, 8>& sv2 = m2[0]; mymap3 m3; small_vector<small_vector<float, 8>, 8>& sv3 = m3[0]; } I can compile it without errors with 'g++ -std=c++11', but without '-std=c++11' I'm getting an error for the 'operator[]' on mymap2: dan@octa ~> g++ -Iboost_1_63_0/ small_vector_test.cpp In file included from boost_1_63_0/boost/container/small_vector.hpp:27:0, from small_vector_test.cpp:2: boost_1_63_0/boost/container/vector.hpp: In instantiation of ‘void boost::container::vector<T, Allocator>::assign(FwdIt, FwdIt, typename boost::move_detail::disable_if_or<void, boost::move_detail::is_same<typename boost::container::container_detail::version<Allocator>::type, boost::move_detail::integral_constant<unsigned int, 0u> >, boost::move_detail::is_convertible<InIt, typename boost::container::allocator_traits<Allocator>::size_type>, boost::container::container_detail::is_input_iterator<FwdIt> >::type*) [with FwdIt = boost::container::container_detail::vec_iterator<std::pair<int, boost::container::small_vector<float, 8ul> >*, true>; T = std::pair<int, boost::container::small_vector<float, 8ul> >; Allocator = boost::container::small_vector_allocator<boost::container::new_allocator<std::pair<int, boost::container::small_vector<float, 8ul> > > >; typename boost::move_detail::disable_if_or<void, boost::move_detail::is_same<typename boost::container::container_detail::version<Allocator>::type, boost::move_detail::integral_constant<unsigned int, 0u> >, boost::move_detail::is_convertible<InIt, typename boost::container::allocator_traits<Allocator>::size_type>, boost::container::container_detail::is_input_iterator<FwdIt> >::type = void]’: boost_1_63_0/boost/container/small_vector.hpp:563:7: required from ‘boost::container::small_vector<T, N, Allocator>::small_vector(const boost::container::small_vector<T, N, Allocator>&) [with T = std::pair<int, boost::container::small_vector<float, 8ul> >; long unsigned int N = 8ul; Allocator = boost::container::new_allocator<std::pair<int, boost::container::small_vector<float, 8ul> > >]’ /usr/include/c++/5/bits/stl_pair.h:113:31: required from ‘std::pair<_T1, _T2>::pair(const _T1&, const _T2&) [with _T1 = const int; _T2 = boost::container::small_vector<std::pair<int, boost::container::small_vector<float, 8ul> >, 8ul>]’ /usr/include/c++/5/bits/stl_map.h:487:23: required from ‘std::map<_Key, _Tp, _Compare, _Alloc>::mapped_type& std::map<_Key, _Tp, _Compare, _Alloc>::operator[](const key_type&) [with _Key = int; _Tp = boost::container::small_vector<std::pair<int, boost::container::small_vector<float, 8ul> >, 8ul>; _Compare = std::less<int>; _Alloc = std::allocator<std::pair<const int, boost::container::small_vector<std::pair<int, boost::container::small_vector<float, 8ul> >, 8ul> > >; std::map<_Key, _Tp, _Compare, _Alloc>::mapped_type = boost::container::small_vector<std::pair<int, boost::container::small_vector<float, 8ul> >, 8ul>; std::map<_Key, _Tp, _Compare, _Alloc>::key_type = int]’ small_vector_test.cpp:18:39: required from here boost_1_63_0/boost/container/vector.hpp:1261:15: error: binding ‘const std::pair<int, boost::container::small_vector<float, 8ul> >’ to reference of type ‘std::pair<int, boost::container::small_vector<float, 8ul> >&’ discards qualifiers *cur = *first; ^ In file included from /usr/include/c++/5/bits/stl_algobase.h:64:0, from /usr/include/c++/5/bits/stl_tree.h:63, from /usr/include/c++/5/map:60, from small_vector_test.cpp:1: /usr/include/c++/5/bits/stl_pair.h:96:12: note: initializing argument 1 of ‘std::pair<int, boost::container::small_vector<float, 8ul> >& std::pair<int, boost::container::small_vector<float, 8ul> >::operator=(std::pair<int, boost::container::small_vector<float, 8ul> >&)’ struct pair ^ Any ideas? Is 'boost:container::small_vector' supposed to work without C++11 support? Thanks! Greetings, Daniel

2 4

How to use Boost libs from projects?
by Andy 01 Jan '17

01 Jan '17

I have project compiled as Debug,x64. And boost 1.63 compiled by: - bootstrap.bat - b2 variant=debug,release link=static runtime-link=static address-model=64 In project I have cpp files with #include "boost/filesystem.hpp" and when compile project I have error: cannot open file 'libboost_filesystem-vc140-mt-gd-1_61.lib' whereas in c:\boost\stage\lib\ I have libboost_filesystem-vc140-mt-sgd-1_63.lib but not libboost_filesystem-vc140-mt-gd-1_61.lib and in VS2015 project I have no Boost lib. (sorry for my English)

4 13