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

[format] warning...warning...warning
by Arnaud RICHARD 24 Mar '17

24 Mar '17

Hello, I'm a complete Boost newbie. I've been told very often that boost is the way to go for serious C++ coding, and I was not surprised to see such emphasis on the home page: "We aim to establish "existing practice" and provide reference implementations so that Boost libraries are suitable for eventual standardization" So when I used the format library on my existing (non-trivial) project and first compiled... I was very very surprised to get my neat compilation console flooded with hundreds of warnings ! I acknowledge I activate many many warnings: CXXFLAGS+=-Wall -Wextra -Wcast-qual -Wctor-dtor-privacy -Wdisabled-optimization \ -Wformat=2 -Winit-self -Wlogical-op -Wmissing-include-dirs \ -Wnoexcept -Woverloaded-virtual -Wredundant-decls -Wshadow \ -Wsign-conversion -Wsign-promo -Wstrict-null-sentinel -Wstrict-overflow=5 \ -Wswitch-default -Wundef -Wunused The warnings were as trivial as (for example): ../ext/boost/boost/type_traits/is_default_constructible.hpp:16:22: warning: "BOOST_GCC_VERSION_WORKAROUND_GUARD" is not defined [-Wundef] #if BOOST_WORKAROUND(BOOST_GCC_VERSION, < 40700) ../ext/boost/boost/format/parsing.hpp:435:67: warning: conversion to 'std::vector<boost::io::detail::format_item<char, std::char_traits<char>, std::allocator<char> >, std::allocator<boost::io::detail::format_item<char, std::char_traits<char>, std::allocator<char> > > >::size_type {aka unsigned int}' from 'int' may change the sign of the result [-Wsign-conversion] string_type & piece = (cur_item==0) ? prefix_ : items_[cur_item-1].appendix_; I understand they are only warning and the code is functionally correct and standard-wise correct. Personally when I face such false warnings in my code, I change the code to remove the warning so that if a warning does make sense, I can notice it. I thought a reference implementation would be written with such policy. There's no way I'm gonna read each of the hundreds of messages to understand if it is a mistake in my source code or a "shortcut" in boost library. So this is my first user experience. Not impressed at all. Boost will not be my reference.

6 8

boost asio client socket connection to servers behind a public IP address
by jupiter 24 Mar '17

24 Mar '17

Hi, I need to run boost asio client socket connections to remote servers via a remote proxy server, the remote proxy server has a public IP address, but none of remote servers have public IP addresses. Appreciate any clues or samples. Thank you.

1 0

[TypeErasure] efficiency problem
by Mikhail Strelnikov 24 Mar '17

24 Mar '17

Hello! In following code TypeErasure creates two copies of s, while Boost.Any creates no copies at all. any x{ s{} }; any y{ std::move(x) }; any z; z = std::move(y); There is move constructor for type_erasure::any, but it does allocate memory and calls copy constructor for s. Why? And why there is no move assignment operator in type_erasure::any? Thanks. Full source: https://wandbox.org/permlink/iHs5a0bjzXsBtpwC

3 3

Re: [Boost-users] [boost] [release] Boost 1.64.0 Beta 1
by Rene Rivera 23 Mar '17

23 Mar '17

On Thu, Mar 23, 2017 at 11:04 AM, Olaf van der Spek <ml(a)vdspek.org> wrote: > VS2015 / W10: > > boost_1_64_0>bootstrap.bat > > Building Boost.Build engine > HRESULT was unexpected at this time. > Could you try building b2.exe directly: === cd tools\build\src\engine built.bat === And posting the output? -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

1 0

Re: [Boost-users] [boost] [release] Boost 1.64.0 Beta 1
by Mateusz Loskot 23 Mar '17

23 Mar '17

On 23 March 2017 at 17:04, Olaf van der Spek via Boost <boost(a)lists.boost.org> wrote: > VS2015 / W10: > > boost_1_64_0>bootstrap.bat > > Building Boost.Build engine > HRESULT was unexpected at this time. bootstrap.bat bootstrap.bat vc14 bootstrap.bat vc141 All succeed for me on W10 w/ VS2015 and VS2017 Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 0

[Iterator] zip iterator with std::tuple or std::pair
by Matthias Wohlgemuth 23 Mar '17

23 Mar '17

Hello, as far as I understand the zip_iterator is compatible also with STL tuple and pair. However, when I try to create a zip_iterator with std::pair it fails to compile. Here, a simple test code: #include <vector> #include <utility> #include <boost/iterator/zip_iterator.hpp> int main () { std::vector<int> v(4); boost::make_zip_iterator(std::make_pair(v.begin(), v.begin())); return 0; } compiled with gcc 4.9.2 and boost 1.62 returns me (tested also with 1.63): In file included from /software/boost-1.62/include/boost/iterator/zip_iterator.hpp:26:0, from test.cpp:3: /software/boost-1.62/include/boost/mpl/at.hpp: In instantiation of ‘struct boost::mpl::at_c<std::pair<__gnu_cxx::__normal_iterator<int*, std::vector<int> >, __gnu_cxx::__normal_iterator<int*, std::vector<int> > >, 0l>’: /software/boost-1.62/include/boost/iterator/zip_iterator.hpp:180:17: required from ‘struct boost::iterators::detail::zip_iterator_base<std::pair<__gnu_cxx::__normal_iterator<int*, std::vector<int> >, __gnu_cxx::__normal_iterator<int*, std::vector<int> > > >’ /software/boost-1.62/include/boost/iterator/zip_iterator.hpp:237:9: required from ‘class boost::iterators::zip_iterator<std::pair<__gnu_cxx::__normal_iterator<int*, std::vector<int> >, __gnu_cxx::__normal_iterator<int*, std::vector<int> > > >’ test.cpp:8:64: required from here /software/boost-1.62/include/boost/mpl/at.hpp:42:8: error: no class template named ‘apply’ in ‘struct boost::mpl::at_impl<boost::mpl::non_sequence_tag>’ struct at_c ^ In file included from test.cpp:3:0: /software/boost-1.62/include/boost/iterator/zip_iterator.hpp: In instantiation of ‘struct boost::iterators::detail::zip_iterator_base<std::pair<__gnu_cxx::__normal_iterator<int*, std::vector<int> >, __gnu_cxx::__normal_iterator<int*, std::vector<int> > > >’: /software/boost-1.62/include/boost/iterator/zip_iterator.hpp:237:9: required from ‘class boost::iterators::zip_iterator<std::pair<__gnu_cxx::__normal_iterator<int*, std::vector<int> >, __gnu_cxx::__normal_iterator<int*, std::vector<int> > > >’ test.cpp:8:64: required from here /software/boost-1.62/include/boost/iterator/zip_iterator.hpp:180:17: error: no type named ‘type’ in ‘struct boost::mpl::at_c<std::pair<__gnu_cxx::__normal_iterator<int*, std::vector<int> >, __gnu_cxx::__normal_iterator<int*, std::vector<int> > >, 0l>’ >::type difference_type; ^ /software/boost-1.62/include/boost/iterator/zip_iterator.hpp:198:11: error: no type named ‘type’ in ‘struct boost::mpl::at_c<std::pair<__gnu_cxx::__normal_iterator<int*, std::vector<int> >, __gnu_cxx::__normal_iterator<int*, std::vector<int> > >, 0l>’ > type; I get a similar results for std::tuple compiled c++11 enabled gcc. I did not find any solution, except a 3 year old patch, which is said to be applied to the boost::iterator library. Any suggestions? Best regards, Matthias

3 3

Is Boost API 32Bit only?
by Andrej Georgi 19 Mar '17

19 Mar '17

I try to build Boost on MSYS2-64Bit which includes 64-Bit headers of windows. Boost is calling a 32-Bit variant of windows API even when Boost is configured to build 64-Bit. There is a 64Bit pre build variant of Boost on sourceforge. That seems to run only in visual studio? Does it use a 32 Bit API as well? Is there any reason for this design? I personaly prefer any variant of GCC over visual studio due to time consuming experiences with visual studio. Kind regards Andrej

4 4

[Stacktrace] Second review begins today 17th Mar ends 26th Mar
by Niall Douglas 17 Mar '17

17 Mar '17

I am pleased to announce the second review of the proposed Boost.Stacktrace library running from today until Sunday 26th. Stacktrace is an optionally header-only library providing multiple implementation backends. At its very simplest it lets you capture the stack backtrace for the calling thread and to print it to a std::ostream& of your choice. The basic_stacktrace<> class quacks like a STL container of frame object instances. The rest of the API pretty much follows STL design principles for the most part. Use is therefore unsurprising. You can find the documentation at http://apolukhin.github.io/stacktrace/index.html and the github repo at https://github.com/apolukhin/stacktrace. Review guidelines ================= This is a second review of this library with many changes implemented in response to feedback from the previous review. My previous review report can be found at http://lists.boost.org/boost-announce/2017/01/0486.php where I made the following conditions for acceptance: 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. Antony hasn't entirely met my conditions, hence this second review. He has instead implemented this changelog: * Reimplemented boost::stacktrace::basic_stacktrace class to accept allocators and to have a small size * Added outputting of the path to the binary object into the stacktrace, when source location is not available * Allowed to use `libbacktrace` - a defacto standard for GCC/CLANG backtracing that does not fork and has a permissive license * Optimized stacktrace and frames ostreaming * Removed backends and made the default tracing to have only platform basic functionality. Added macros to enable additional functionality. * Fixed (theoretically) MinGW compilation * Added functions for async-safe dumping into memory or descriptor * Changed signal handling example to be async-signal-safe * Allowed users to choose how many frames to skip during stack capture * Removed `boost::stacktrace::stacktrace` functions and other internals from printed stack traces * Updated docs: * examples now use Boost.Exception * removed all the references to "backend" * reduced macro count * "Build, Macros and Backends" section was rewritten and became "Configuration and Build" * added note that library is C++03 * added examples on storing traces into shared memory * updated all the human readable dumps It is up to the Boost community as to whether this revised library is now acceptable without any conditions, or with conditions. Reviews should be submitted to the developer list (boost_at_[hidden]), preferably with '[stacktrace]' in the subject. Or if you don't wish to for some reason or are not subscribed to the developer list you can send them privately to me at 's_sourceforge at nedprod dot com'. If so, please let me know whether or not you'd like your review to be forwarded to the list. For your review you may wish to consider the following questions: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? And finally, every review should attempt to answer this question: - Do you think the library should be accepted as a Boost library? Be sure to say this explicitly so that your other comments don't obscure your overall opinion. Even if you do not wish to give a full review any technical comment regarding the library is welcome as part of the review period and will help me as the review manager decide whether the library should be accepted as a Boost library. Any questions about the use of the library are also welcome. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

1 0

Compiling Boost on MSYS2
by Andrej Georgi 15 Mar '17

15 Mar '17

Hello Boost Users, why does Boost use a 32-Bit API for multithreading on a 64 bit system? The Win32 API header on MSYS2 uses 64-Bit Windows API and the Boost implementation (win32_api.hpp) uses 32-Bit which makes my compiler (gcc 6.3.0) complain. Do I have to configure Boost to be 64-Bit? Regards Andrej

1 0

compilation failed with error due to boost thread library
by Jack Kumba 11 Mar '17

11 Mar '17

Hello, the compilation of my library failed with the following error: make[1]: *** Waiting for unfinished jobs.... /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libboost_coroutine.a(stack_traits.o): undefined reference to symbol '_ZN5boost13thread_detail18commit_once_regionERNS_9once_flagE' /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.58.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status What do you think can be the source of error? It used to compile well before... Cheers, Jack

2 1

SSL client boost::asio::ssl::stream handshake hang up in reconnection
by jupiter 09 Mar '17

09 Mar '17

Hi, When it was the first time to connect to server, the following code works fine. s.lowest_layer().connect(*endpoint_iterator++, error); s.handshake(boost::asio::ssl::stream_base::client, error); When the server connection lost then resumed, the client try to run above code again, the s.lowest_layer().connect(*endpoint_iterator++, error); returned no error of success, but the s.handshake(boost::asio::ssl::stream_base::client, error); hang up. Appreciate any helps? Thank you. - j

1 0

[type_erasure] member function return any
by Mikhail Strelnikov 06 Mar '17

06 Mar '17

Hello! I want to return type_erasure::any from a member function of a struct adapted by that same any. How can I do this? #include <boost/type_erasure/any.hpp> #include <boost/type_erasure/callable.hpp> using my_any = boost::type_erasure::any< boost::mpl::vector< boost::type_erasure::copy_constructible<>, boost::type_erasure::assignable<>, boost::type_erasure::callable<? ? ?> > >; struct s { my_any operator()(my_any v) { return v; } }; int main() { my_any t = s{}; t = t(t); } Thanks.

2 1

[boost] Unbounded integers and shared memory
by Antony Polukhin 04 Mar '17

04 Mar '17

Hello, One of the ISO WG21 C++ Study Groups is investigating the usecases of shared memory usage with wide arithmetics (Boost.Interprocess, Boost.Multiprecision, in-house solutions?). Particularly interesting: * Are there users that store unbounded numbers in shared memory? * Will bounded integers satisfy need of those users? Informal glossary: * "unbounded numbers" - numbers (integral, relational, floating point and others) that can store and operate on any huge value by dynamically allocating memory as necessary to maintain a representation of operation results. * "bounded types" - Numbers (integral, relational, floating point and others) which bounds are specified in number of bytes/bits/words at compile time and that do not allocate memory. Please, response if you are one of such users. Great thanks in advance! -- Best regards, Antony Polukhin

1 0

[spirit-qi] [attr] Invalid static_cast error
by 含露月含露月 03 Mar '17

03 Mar '17

Hi, I try to generate a string using qi::attr, and the following is the code. #include <boost/spirit/include/qi.hpp> namespace qi = boost::spirit::qi; int main(){ // ok qi::rule<char const *, std::string()> world = qi::attr("world"); qi::rule<char const *, std::string()> rule = qi::eps > world; // error: invalid static_cast from type 'const char [6]' to type 'char' // qi::rule<char const *, std::string()> rule = qi::eps > qi::attr("world"); } Do I miss something or it is a bug? How can I fix it without using extra rules or semantic actions. Platform: win7 64bit Compiler: gcc 4.9.1 Boost 1.63 Since I typed on my phone, forgive me if there are errors. Best regards, Yuan Yao

1 0

error running boost book
by Clark Sims 02 Mar '17

02 Mar '17

I get the following error when I cd to BOOST_ROOT/doc and run ../bjam My ~/user-config.jam looks fine. I pasted it bellow the error. Does anyone know how to fix this? I have spent a great deal of time trying to fix this. It looks like the doxygen.jam in the boost_1_63_0/tools/build/src/tools directory does not like the syngax of the doxygen rule in ~/user-config.jam. ---------------------------------------------------------------------------------------------------------------------------------- Building the tti docs with automatic index generation disabled. Try building with --enable-index. /home/csims/boost_1_63_0/libs/dll/doc/Jamfile.v2:66: in modules.load *** argument error * rule doxygen ( target : sources + : requirements * : default-build * : usage-requirements * ) * called with: ( autodoc_shared_library_core : : <doxygen:param>HIDE_UNDOC_MEMBERS=YES <doxygen:param>HIDE_UNDOC_CLASSES=YES <doxygen:param>HIDE_SCOPE_NAMES=YES <doxygen:param>EXTRACT_ALL=NO <doxygen:param>EXTRACT_PRIVATE=NO <doxygen:param>BUILTIN_STL_SUPPORT=YES <doxygen:param>ENABLE_PREPROCESSING=YES <doxygen:param>MACRO_EXPANSION=YES <doxygen:param>ALIASES= \ "forcedlink{1}=\xmlonly<link linkend='boost.dll.\1'>boost::dll::\1</link>\endxmlonly" \ "forcedmacrolink{1}=\xmlonly<link linkend='\1'>\1</link>\endxmlonly" <doxygen:param>PREDEFINED= \ "BOOST_RV_REF(T)=T&&" \ "BOOST_RV_REF(shared_library)=shared_library&&" \ "BOOST_COPY_ASSIGN_REF(shared_library)=const shared_library&" \ "BOOST_MOVABLE_BUT_NOT_COPYABLE(shared_library)= \ shared_library(const shared_library&) = delete; \ shared_library& operator=(const shared_library&) = delete; " \ "BOOST_DLL_IMPORT_RESULT_TYPE=result_type" \ "BOOST_DLL_MANGLED_IMPORT_RESULT_TYPE=result_type" \ "BOOST_EXPLICIT_OPERATOR_BOOL()=explicit operator bool() const noexcept;" \ "BOOST_DLL_DOXYGEN" <xsl:param>boost.doxygen.reftitle=Shared Library Reference ) * missing argument sources /home/csims/boost_1_63_0/tools/build/src/tools/doxygen.jam:622:see definition of rule 'doxygen' being called /home/csims/boost_1_63_0/tools/build/src/build/project.jam:325: in load-jamfile /home/csims/boost_1_63_0/tools/build/src/build/project.jam:64: in load /home/csims/boost_1_63_0/tools/build/src/build/project.jam:145: in project.find Jamfile.v2:96: in modules.load /home/csims/boost_1_63_0/tools/build/src/build/project.jam:325: in load-jamfile /home/csims/boost_1_63_0/tools/build/src/build/project.jam:64: in load /home/csims/boost_1_63_0/tools/build/src/build/project.jam:145: in project.find /home/csims/boost_1_63_0/tools/build/src/build-system.jam:535: in load /home/csims/boost_1_63_0/tools/build/src/kernel/modules.jam:295: in import /home/csims/boost_1_63_0/tools/build/src/kernel/bootstrap.jam:139: in boost-build /home/csims/boost_1_63_0/boost-build.jam:17: in module scope ---------------------------------------------------------------------------------------------------------------------

2 1

[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

How compile with clang ?
by Andy 02 Mar '17

02 Mar '17

I have installed Clang at "c:\Program Files\LLVM" try: b2 clean b2 toolset=clang cxxflags="-std=c++1y -stdlib=libc++" linkflags="-stdlib=libc++" --prefix=c:\boost -j 4 stage release b2 install toolset=clang cxxflags="-std=c++1y -stdlib=libc++" linkflags="-stdlib=libc++" --prefix=c:\boost but is error: fatal error: 'corecrt.h' file not found #include <corecrt.h>

2 1

Re: [Boost-users] Fw: error running boost book
by Clark Sims 02 Mar '17

02 Mar '17

I attached my user-config.jam I also attached the output of ../b2 --debug-configuration, as the file, debug.txt. I went to the BOOST_ROOT directory and rebuilt the headers. Initially ./b2 headers, caused errors, because I had initially run b2 as "sudo ./b2 install". I chowned back to my user, and reran. After I reran I still got the same errors. Thanks again for your help, Clark -------------------------------------------- On Mon, 2/27/17, Rene Rivera <grafikrobot(a)gmail.com> wrote: Subject: Re: Fw: error running boost book To: "Clark Sims" <clark_sims_boost(a)yahoo.com> Date: Monday, February 27, 2017, 10:18 AM On Mon, Feb 27, 2017 at 9:01 AM, Clark Sims <clark_sims_boost(a)yahoo.com> wrote: Hi Rene, I saw you were one of the developers on this project. Do you know how to solve this? Sorry I missed the email firs time around. Perhaps.. But need more info.. --- On Sat, 2/25/17, Clark Sims <clark_sims_boost(a)yahoo.com> wrote: > From: Clark Sims <clark_sims_boost(a)yahoo.com> > Subject: error running boost book > To: boost-users(a)lists.boost.org > Date: Saturday, February 25, 2017, 6:53 PM > I get the following error when I cd > to BOOST_ROOT/doc and run ../bjam > My ~/user-config.jam looks fine. I pasted it bellow the > error. Does anyone know how to fix this? It seems you forgot to paste the user-config. ALso try running with --debug-configuration and paste the header output for that. > I have spent a great deal of time trying to fix this. > It looks like the doxygen.jam in the > boost_1_63_0/tools/build/src/ tools directory does not like > the syngax of the doxygen rule in ~/user-config.jam. > > ------------------------------ ------------------------------ ------------------------------ ------------------------------ ---------- > > Building the tti docs with automatic index generation > disabled. Try building with --enable-index. > /home/csims/boost_1_63_0/libs/ dll/doc/Jamfile.v2:66: in > modules.load > *** argument error > * rule doxygen ( target : sources + : requirements * : > default-build * : usage-requirements * ) > * called with: ( autodoc_shared_library_core : : At this level it looks like it's missing aources. Looking at Boost DLL doc build file <https://github.com/boostorg/dll/blob/boost-1.63.0/doc/Jamfile.v2> it does globs for filling header files for the sources. Which would suggest that the headers aren't there. And hence you should try running "b2 headers" first. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

1 0

[thread] Feature request: set_value/exception with deferred notification (not at_thread_exit)
by TONGARI J 28 Feb '17

28 Feb '17

boost::promise (so does std::promise) only supports set_value/exception and their at_thread_exit variants, while the at_thread_exit variants support deferred notification, but the point to trigger the notification is restricted to thread-exit. This is not sufficient for, e.g. coroutine usage. This is the same problem as shown in this post: https://www.reddit.com/r/cpp/comments/4ctj2a/visual_studio_2015_update_2_co… If you want to write a "correct" adaptor for boost::future, currently you have to use extra storage when you get the return-value from the coroutine, and set the promise until final_suspend is reached. To efficiently address the problem, we need something like: * promise::set_value_deferred * promise::set_exception_deferred * promise::notify_deferred Thoughts?

2 3

libc++-5 doesn't know auto_ptr anymore
by bebuch 28 Feb '17

28 Feb '17

I just tried to compile one of my projects with LLVM-TOT and got a lot of error massages in boost's shared_ptr implementation because libc++ removes std::auto_ptr. (I don't use boost::shared_ptr directly, but via parts of boost::dll and boost:spirit::x3.) Is there a workaround? -- View this message in context: http://boost.2283326.n4.nabble.com/libc-5-doesn-t-know-auto-ptr-anymore-tp4… Sent from the Boost - Users mailing list archive at Nabble.com.

4 6

serialization support for gcc ?
by Alain Miniussi 28 Feb '17

28 Feb '17

Hi, In the serialization jam file (master), I see: <toolset>gcc:<cxxflags>"-fvisibility=hidden -fvisibility-inlines-hidden" with no mention of gcc version number. gcc-3.4.4, for one, does not support that option. Does that mean that the serialization library does not support the gcc-3.x serie ? Thanks Alain

4 8

Issues building Boost 1.63.0 on Solaris 11.3 x86 using Developer Studio 12.5
by Leo Carreon 28 Feb '17

28 Feb '17

Hi, According to the Boost 1.63.0 release notes, Solaris Studio 12.5 and Solaris Studio 12.5 C++11 are supported. However, when I build in C++11 and C++14 modes I get the following errors during the configuration check stage of the build: a.. Possible issue with threading even when I am building with the option – threading=multi: error: No best alternative for libs/context/build/asm/make_x86_64_sysv_elf_gas.o next alternative: required properties: <threading>multi matched next alternative: required properties: <threading>multi matched error: No best alternative for libs/context/build/asm/jump_x86_64_sysv_elf_gas.o next alternative: required properties: <threading>multi matched next alternative: required properties: <threading>multi matched error: No best alternative for libs/context/build/asm/ontop_x86_64_sysv_elf_gas.o next alternative: required properties: <threading>multi matched next alternative: required properties: <threading>multi matched b.. Issue with ICU library detection even when I have installed the developer/icu and library/icu packages: - icu : no - icu (lib64) : no - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. I also get the following errors during the build stage: a.. Issue with Boost.Fiber: "./boost/fiber/detail/spinlock_ttas.hpp", line 73: Error: Could not find a match for std::chrono::duration<long, std::ratio<1, 1000000>>::duration({initializer list}) needed in boost::fibers::detail::spinlock_ttas::lock(). "./boost/fiber/detail/spinlock_ttas.hpp", line 73: Error: Initializer for constexpr variable us0 must be a constant expression. "./boost/fiber/detail/spinlock_ttas_adaptive.hpp", line 77: Error: Could not find a match for std::chrono::duration<long, std::ratio<1, 1000000>>::duration({initializer list}) needed in boost::fibers::detail::spinlock_ttas_adaptive::lock(). "./boost/fiber/detail/spinlock_ttas_adaptive.hpp", line 77: Error: Initializer for constexpr variable us0 must be a constant expression. "./boost/fiber/context.hpp", line 341: Error: A declaration does not specify a tag or an identifier. "./boost/fiber/context.hpp", line 341: Error: Only non-static data members may be mutable. "./boost/fiber/context.hpp", line 341: Error: Use ";" to terminate declarations. "./boost/fiber/context.hpp", line 341: Error: "}" expected instead of "noexcept". "./boost/fiber/context.hpp", line 341: Error: Use ";" to terminate declarations. "./boost/fiber/context.hpp", line 341: Error: A declaration was expected instead of "noexcept". "./boost/fiber/context.hpp", line 342: Error: run_ is not defined. "./boost/fiber/context.hpp", line 342: Error: A template name was expected instead of 'forward'. "./boost/fiber/context.hpp", line 342: Error: ctx is not defined. "./boost/fiber/context.hpp", line 342: Error: Unexpected ")" -- Check for matching parenthesis. "./boost/fiber/context.hpp", line 342: Error: Operand expected instead of ",". "./boost/fiber/context.hpp", line 342: Error: The function "std::forward()" cannot be defined in the current scope. "./boost/fiber/context.hpp", line 343: Error: A declaration was expected instead of ",". "./boost/fiber/context.hpp", line 344: Error: Fn is not defined. "./boost/fiber/context.hpp", line 344: Error: A template name was expected instead of 'forward'. "./boost/fiber/context.hpp", line 344: Error: fn is not defined. "./boost/fiber/context.hpp", line 345: Error: Unexpected ")" -- Check for matching parenthesis. "./boost/fiber/context.hpp", line 345: Error: Operand expected instead of "}". "./boost/fiber/context.hpp", line 345: Error: The function "std::forward()" cannot be defined in the current scope. "./boost/fiber/context.hpp", line 355: Error: A declaration was expected instead of "{". "./boost/fiber/context.hpp", line 357: Error: No direct declarator preceding "(". b.. Issue with libs/log which happens in C++11 mode only: "libs/log/src/named_scope.cpp", line 118: Error: Overloading ambiguity between "boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)" and "boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)". 1 Error(s) detected. "CC" -std=c++11 -xO4 -mt -erroff=%none -m64 -KPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_DYN_LINK=1 -DBOOST_CHRONO_DYN_LINK=1 -DBOOST_DATE_TIME_DYN_LINK=1 -DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_LOG_BUILDING_THE_LIB=1 -DBOOST_LOG_DLL -DBOOST_LOG_HAS_PTHREAD_MUTEX_ROBUST -DBOOST_LOG_USE_NATIVE_SYSLOG -DBOOST_LOG_WITHOUT_DEBUG_OUTPUT -DBOOST_LOG_WITHOUT_EVENT_LOG -DBOOST_SPIRIT_USE_PHOENIX_V3=1 -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_SYSTEM_NO_DEPRECATED -DBOOST_THREAD_BUILD_DLL=1 -DBOOST_THREAD_DONT_USE_CHRONO=1 -DBOOST_THREAD_POSIX -DBOOST_THREAD_USE_DLL=1 -DDATE_TIME_INLINE -DNDEBUG -D_XOPEN_SOURCE=500 -D__EXTENSIONS__ -D__STDC_CONSTANT_MACROS -D__typeof__=__typeof__ -I"." -I"libs/log/src" -c -o "bin.v2/libs/log/build/sun/release/address-model-64/threading-multi/named_scope.o" "libs/log/src/named_scope.cpp" ...failed sun.compile.c++ bin.v2/libs/log/build/sun/release/address-model-64/threading-multi/named_scope.o... c.. Issue with libs/python: "libs/python/src/numpy/dtype.cpp", line 61: Error: NPY_FLOAT16 is not defined. 1 Error(s) detected. "CC" -std=c++11 -xO4 -mt -erroff=%none -m64 -KPIC -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -I"/usr/include/python2.7" -I"/usr/lib/python2.7/vendor-packages/numpy/core/include" -c -o "bin.v2/libs/python/build/sun/release/address-model-64/threading-multi/numpy/dtype.o" "libs/python/src/numpy/dtype.cpp" ...failed sun.compile.c++ bin.v2/libs/python/build/sun/release/address-model-64/threading-multi/numpy/dtype.o... Has anyone found solutions to these issues? FYI, a set of libraries are still generated even after the above issues have occurred. I’m not sure how reliable are these libraries which I assume are unaffected by the above issues. Kinds regards, Leo

2 2

Issue with Boost.Test using Oracle Developer Studio 12.5
by Leo Carreon 28 Feb '17

28 Feb '17

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

1 0

[gsoc17] Boost will be participating in Google Summer of Code in 2017
by Niall Douglas 27 Feb '17

27 Feb '17

I am very pleased to inform the Boost community that Google accepted us into their Summer of Code programme this year. This was especially welcome after we were given "a year off" last year which could have caused substantial disruption to the multi year student projects had it not been due to the timely action of the steering committee and generous sponsorship of a stop gap Boost Summer of Code in 2016 by IMC Financial Markets. Last year Google completely rebuilt the Summer of Code website so it no longer is anything like it was before. Now we must individually invite those who vote on student projects, so *anyone willing to rank student project proposals* can you please email us with your details: 1. Your email address matching your Google Account so we can invite you onto the GSoC programme. 2. (Optional) your email address matching your Github Account so we can invite you onto the Boost GSoC github org for 2017 as a potential mentor. Our thanks to those who have already added project ideas to https://svn.boost.org/trac/boost/wiki/SoC2017, but we need MORE ideas and MORE potential project mentors. Follow the project idea template at https://svn.boost.org/trac/boost/wiki/GSoCIdeaTemplate and either add it straight to the wiki page or email it to us so we can add it for you. Our thanks to all in advance.

1 0

Generate SSL certificate, chain file, dh and key for boost::asio::ssl::context
by jupiter 27 Feb '17

27 Feb '17

Hi, I think I can use openssl to generate those self signed files, correct? I saw some programs use 4 use_certificate_chain_file, use_certificate_file, use_private_key_file and use_tmp_dh_file in both server and client sites, but I also saw some test program only use one ca.pem in client site and 3 use_certificate_chain_file, use_private_key_file and use_tmp_dh_file in server site, which is correct or better? Any guideline? Thank you.

2 4

Monitor lost client data connections
by jupiter 27 Feb '17

27 Feb '17

Hi, I have a server socket connected by many clients using boost::asio::ip::tcp::socket to set up server socket connection and to use boost::asio::ip::tcp::acceptor async_accept for new client connections. The client may come and go, so I need to check if the connection is still valid or not before sending message to clients. How can I check if a client connection is no longer valid? My server does not seem get any indication when a client terminate the connection. Thank you. Kind regards, - j

2 4

[context/coroutine] DLL link errors in VS2015
by Gavin Lambert 26 Feb '17

26 Feb '17

I'm migrating some existing code that uses Boost.Coroutine from VS2013 to VS2015 and from Boost 1.55 to Boost 1.60. (Minor aside: coroutine<T>::push_type had an empty() method in 1.55 which has vanished in 1.60. This was mildly annoying but easily fixed by using operator! instead.) The code builds and runs fine as-is in VS2015 with Boost 1.60. However I wanted to try migrating to Boost.Coroutine2 as well, since Coroutine is deprecated. This however gives me the following errors: t:\boost\boost_1_60_0\boost\context\execution_context.ipp(209): warning C4251: 'boost::context::execution_context::ptr_': class 'boost::intrusive_ptr<boost::context::detail::activation_record>' needs to have dll-interface to be used by clients of class 'boost::context::execution_context' t:\boost\boost_1_60_0\boost\context\execution_context.ipp(54): note: see declaration of 'boost::intrusive_ptr<boost::context::detail::activation_record>' error LNK2001: unresolved external symbol "public: static class boost::intrusive_ptr<struct boost::context::detail::activation_record> boost::context::detail::activation_record::current_rec" (?current_rec@activation_record@detail@context@boost@@2V?$intrusive_ptr@Uactivation_record@detail@context@boost@@@4@A) I'm building with BOOST_ALL_DYN_LINK, in case that makes a difference. Is this a known issue? Is it fixed in a later Boost release? (FWIW, Boost.Coroutine also generates C4251 with a different symbol but does not generate LNK2001, so the application still works.)

2 6

Re: [Boost-users] Building Boost 1.63.0 with Oracle Developer Studio 12.5
by Leo Carreon 26 Feb '17

26 Feb '17

These are the issues I have discovered after examining the build log: a.. Error message during configuration check: error: No best alternative for libs/context/build/asm/make_x86_64_sysv_elf_gas.o next alternative: required properties: <threading>multi b.. Warning message during configuration check even after installing developer/icu and library/icu packages: - Boost.Locale needs either iconv or ICU library to be built. c.. Lots of error messages during Boost.Fiber build. d.. Error message during Boost.Python build. I am attaching a copy of the build log for your perusal. I have also adjusted the build command to include “threading=multi”. From: Leo Carreon Sent: Sunday, February 26, 2017 12:40 PM To: Boost Users Mailing List Subject: Building Boost 1.63.0 with Oracle Developer Studio 12.5 Hi, Is building Boost 1.63.0 with Oracle Developer Studio 12.5 supported? I tried building it using the following commands but I get a lot of errors: ./bootstrap.sh --with-toolset=sun ./b2 link=shared runtime-link=shared address-model=64 threading=multi variant=release cxxflags="-std=c++14" linkflags="-std=c++14" FYI, I’m building on Oracle Solaris 11.3 running on a x86-64 virtual machine. Am I missing something? Kind regards, Leo

1 0

Building Boost 1.63.0 with Oracle Developer Studio 12.5
by Leo Carreon 26 Feb '17

26 Feb '17

Hi, Is building Boost 1.63.0 with Oracle Developer Studio 12.5 supported? I tried building it using the following commands but I get a lot of errors: ./bootstrap.sh --with-toolset=sun ./b2 link=shared runtime-link=shared address-model=64 variant=release cxxflags="-std=c++14" linkflags="-std=c++14" FYI, I’m building on Oracle Solaris 11.3 running on a x86-64 virtual machine. Am I missing something? Kind regards, Leo

1 0

[Boost.Build, Coroutine2] /usr/bin/ld: cannot find -lboost_coroutine2
by Mikhail Strelnikov 24 Feb '17

24 Feb '17

Hello. My Jamroot looks like this: local BOOST_ROOT = [ modules.peek : BOOST_ROOT ] ; project my_project : requirements <define>BOOST_ALL_NO_LIB=1 : build-dir bin.v2 ; use-project /boost : $(BOOST_ROOT) ; exe my : my_source.cpp /boost//thread /boost//coroutine2 ; Command line: b2 --build-dir=whatever -sBOOST_ROOT=/path/to/boost_1_63_0 I'm getting the following error: /usr/bin/ld: cannot find -lboost_coroutine2 This happens because a library without sources: https://github.com/boostorg/coroutine2/blob/develop/build/Jamfile.v2#L29 is a pre-built library. Header-only library should use alias - http://www.boost.org/build/doc/html/bbv2/faq/header-only-libraries.html After changing "lib boost_coroutine2..." to "alias boost_coroutine2 ;" I had to add <library>/boost//context to usage-requirements of boost/coroutine2 project. Apparently reference to Context from "requirements" (at line 13) is not enough in this case. Can this be a bug in Boost.Build? But the problem with alias is that "b2 --with-coroutine2" does not build anything at all. My question: is it supported scenario by Boost.Build - header-only library depending on not-header-only library? Bonus question: can those BOOST_DISABLE_ASSERTS be removed from Jamfiles building Context, Coroutine2 and Fiber? Thanks.

1 0

quick question about macro
by Peter Gusev 24 Feb '17

24 Feb '17

hi there! I'm using boost library occasionally and have this simpleton question to ask. i need to debug *boost::asio::io_service* by enabling *BOOST_ASIO_ENABLE_HANDLER_TRACKING* macro. so, do I have to rebuild the library like * ./b2 cxxflags="-DBOOST_ASIO_ENABLE_HANDLER_TRACKING"...* or adding * #define BOOST_ASIO_ENABLE_HANDLER_TRACKING* to my source file is enough? (this doesn't work for me, so i suspect I should go with the first option) thanks, -- Peter Gusev

2 1

[bip] alignment/padding differs
by Jan Boehme 23 Feb '17

23 Feb '17

Hi, I'm using interprocess to share mem between different processes. Unfortunately these processes were built using different compiler version (gcc3, gcc4, gcc5) and we're seeing different alignment or padding dependent on which run-time was in charge of creating the mapped files. Of course we used the same boost version (1.60) while creating the binaries. Obviously ip can't handle these different layouts and mostly runs in indefinite loops while traversing an rb-tree not finding the first shm object. Are there any template parameters that enable the code to be accessed using different run times through forcing the same layout? Thanks a lot, Jan.

2 2

Using Boost 1.63 on Windows with FindBoost.cmake
by csiga.biga＠aol.com 22 Feb '17

22 Feb '17

Does anyone have a working installation of Boost 1.63 on Windows that FindBoost.cmake can be instructed to find? I tried with both a custom build (for MSMPI mostly) that it failed to find the libraries of, and after reading through FindBoost.cmake, I saw it is dominantly tailored towards the prebuilt binaries (at least on Windows), so I grabbed that, I set BOOSTROOT to the installation root, but it still fails to find Boost::chrono I got find_package(Boost 1.63 REQUIRED COMPONENTS chrono) include_directories(${Boost_INCLUDE_DIRS}) in my top-level CMakeLists.txt file, as all of my targets depend on chrono, and after that I use target_link_libraries (${declare_trisycl_test_TARGET} $<$<BOOL:USES_OPENCL>:${OpenCL_LIBRARIES}> $<$<NOT:$<BOOL:WIN32>>:Threads::Threads> Boost::chrono) On the command-line this is what I get at configure time: CMake Error at C:/Kellekek/Kitware/CMake/3.8.0/share/cmake-3.8/Modules/FindBoost.cmake:1812 (message): Unable to find the requested Boost libraries. Boost version: 1.63.0 Boost include path: C:/Kellekek/Boost/1.63.0-prebuilt Could not find the following Boost libraries: boost_chrono Some (but not all) of the required Boost libraries were found. You may need to install these additional Boost libraries. Alternatively, set BOOST_LIBRARYDIR to the directory containing Boost libraries or BOOST_ROOT to the location of Boost. Call Stack (most recent call first): CMakeLists.txt:26 (find_package) As far as FindBoost.cmake goes, it seems to know chrono for 1.63. So how should this work?

2 1

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

21 Feb '17

Sending this again, since I hadnt subscribed before sending this email. One suspicious candidate from further debugging is the results_collector singleton(just because it appears in the stack and because its a singleton) 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 >

1 0

[iostreams] filtering streams in a chain are continually writing the same bytes
by Andrew Ames 21 Feb '17

21 Feb '17

Perhaps someone can clarify that my use of multichar_output_filter is valid. When I debug this, even though my write method is returning 4 bytes for every write, the caller of my output filter keeps providing me the same four bytes after the first sequence of 4 bytes. This is boot version 1.62. Here is compiling code that illustrates: class fixed_size_output_filter : public boost::iostreams::multichar_output_filter { public: fixed_size_output_filter(std::streamsize size = 4) : mSize(size) {} template<typename Sink> std::streamsize write(Sink &sink, const char *s, std::streamsize n) { std::streamsize bytesAttempted = std::min(mSize, n); std::streamsize bytesActual = boost::iostreams::write(sink, s, bytesAttempted); return bytesActual; } private: std::streamsize mSize; }; BOOST_AUTO_TEST_CASE(FixedSizeOutputFilter) { #define BYTES 500 char sink_buffer[BYTES]; array_sink array_sink(sink_buffer, sizeof(sink_buffer)); std::streampos os_pos; { filtering_ostream os; os.push(fixed_size_output_filter()); os.push(array_sink); char buffer[BYTES]; for(char i = 0; i < sizeof(buffer); i++) buffer[i] = i; os.write(buffer, sizeof(buffer)); } for(char i = 0; i < sizeof(sink_buffer); i++) BOOST_CHECK(i == sink_buffer[i]); } The actual bytes that end up in the sink_buffer are as follows: 0, 1, 2, 3, 4, 5, 6, 7, 4, 5, 6, 7, 4, 5, 6, 7, 4, 5, 6, 7, ....uninitialized bytes follow through the rest of the buffer. It would appear that the indirect_streambuf in use by the filter chain is incorrectly flushing the bytes. Is my understanding of the library flawed? Does this appear to be a bug? Any help is greatly appreciated. -- Andrew Ames aames(a)tanzle.com

1 1

[thread] Ambiguity in variadic wait_for_all
by Gavin Lambert 18 Feb '17

18 Feb '17

A colleague recently ran into an interesting issue when upgrading some working code from Boost 1.55 to 1.60/1.63 (and from C++03 to C++11). The exact details are unimportant, but it was trying to get the address of boost::wait_for_all(Iterator, Iterator), for use in a Boost.Bind call. In 1.55, this worked fine, although of course it had to supply template parameters that proved the parameters were not futures (thus causing enable_if<is_future_type<F1>> to fail, disabling the two-future-args overload of the function. In 1.60/1.63, the variadic method is encountered instead, which lacks any enable_if condition and thus the ambiguity between the two remains and the compiler errors out. (When calling it directly, the variadic one manages to get disabled as long as the iterator type lacks a wait() method, but this doesn't apply when just getting the method address, as it's not part of the signature.) Should the variadic form also have enable_if? Or is this considered user error for trying to use Bind in a variadic-compatible compiler instead of using a lambda?

2 3

Scheduled Outage : Web sites / Trac
by Michael Caisse 17 Feb '17

17 Feb '17

We are planning the final move of services from IU this week. Expect service outages for all web sites including Trac on 17-February-2017 between 16:00 UTC - 00:00 UTC. The mail lists will continue to operate during this time; however, all other sub-domains for boost.org will be affected. Sync'ing bandwidth with IU has been low recently and has caused us to increase the outage window. We will notify these lists when services are available again. Thank you for your patience during the move. -- Michael Caisse Ciere Consulting ciere.com

1 1

type() Segmentation Fault
by Samuel Jiménez Gil 16 Feb '17

16 Feb '17

Hi, I've got a very strange segmentation error that stems from calling type() method in any class. Surprisingly, this only occurs in another compilation that I have where I link with other gnu libraries. In both cases I am compiling with -std=c++11 and cygwin32. Is anybody aware of type() method conflicting with other libraries? Many thanks. Best regards. -- Samuel Jiménez Gil. Ph.D. Student Real-Time Systems Group, Department of Computer Science University of York Heslington York, UK YO10 5GH Email disclaimer: http://www.york.ac.uk/docs/disclaimer/email.htm

1 0

[test] bitwise checks for non-integer types
by Norbert Wenzel 14 Feb '17

14 Feb '17

I was just surprised that BOOST_CHECK_BITWISE_EQUAL does not simply take two memory ranges and compares them bitwise, but requires integers (or types that support bit shifting). I wanted to compare two floats after binary deserialization and wanted to make sure all bits had been placed correctly, before doing value comparison. What I came up with now is a reinterpret_cast to uint8_t* and then using bitwise comparison byte for byte. I would have expected the test framework to do exactly that internally. Is comparing anything besides integers bitwise considered a bad practice or is there another reason for this limitation of BITWISE_EQUAL? If there is a rationale could that be documented at [0], since the documentation currently only speaks of unconstrained "values". thanks, Norbert [0] http://www.boost.org/doc/libs/1_63_0/libs/test/doc/html/boost_test/utf_refe…

2 2

[serialization]: Possible to not escape double quotes
by Forumer 4umer 14 Feb '17

14 Feb '17

Hello, I am using boost serialization to save some parameteres into an xml file but this xml file is parsed through gettext tools to generate translations. The macro used for generations is _("") so my xml should look like this: <ProcedureSchema> <procedures class_id="4" tracking_level="0" version="0"> <count>1</count> <item_version>0</item_version> <item> <Name>_("Full procedure")</Name> </item> </procedures> </ProcedureSchema> The problem is boost serialization escapes double quotes with " : <Name>_("Full procedure")</Name> Would it be possible to not escape double quotes ? or at least provide a parameter that allows it ?

2 1

Boost.Log and reinitializing text file backend on I/O errors
by Tero Saarni 13 Feb '17

13 Feb '17

Hi, I'm using text file sink to log into a file on NFS filesystem. I would like to make logging more robust when it comes to unreliability of NFS. I've registered an exception handler to ignore I/O errors, but I don't know how to re-open the log file automatically so that logging would continue when the filesystem is online again. My first try was to remove and reinitialize all sinks when the exception handler is called, but this seems to cause deadlock. Is there a way to simply re-open the associated file which caused the exception? -- Tero

1 0

[accumulator] std::chrono::duration in boost::accumulator
by georg＠schorsch-tech.de 12 Feb '17

12 Feb '17

I want to build a histogram of `std::chrono::high_resolution_clock::duration` object. For this issue i wanted to use boost::accumulators as the framework. As it did not compile in my project i teared it down and based it on a running example with `double` as a data type. My general goal on my project is to do use for everything united types. Time and all measured stuff. I would want to avoid to use `.count()` on the duration. Is there any known workaround around this? it is not dependent on the compiler as it seems. With gcc 6.3 it failes too. It compiles when i use clang++-3.9 --std=c++14 -g -O0 main.cpp But when i set the define USE_CHRONO it failes with the error: clang++-3.9 --std=c++14 -g -O0 -DUSE_CHRONO main.cpp In file included from main.cpp:7: /usr/include/boost/accumulators/statistics/density.hpp:75:15: error: no matching constructor for initialization of 'array_type' (aka 'vector<std::chrono::duration<unsigned long, std::ratio<1, 1000000000> > >') , samples_in_bin(num_bins + 2, 0.) ^ ~~~~~~~~~~~~~~~~ and here is my teared down example. I used this site as a base and exhanged double to data_t. http://programmingexamples.net/wiki/CPP/Boost/Histogram #include <vector> #include <algorithm> #include <iostream> #include <chrono> #include <boost/accumulators/accumulators.hpp> #include <boost/accumulators/statistics/density.hpp> #include <boost/accumulators/statistics/stats.hpp> using namespace boost; using namespace boost::accumulators; using duration_t = std::chrono::high_resolution_clock::duration; #ifdef USE_CHRONO using data_t = duration_t; data_t construct(double d) { return std::chrono::milliseconds(0); } #else using data_t = double; data_t construct(double d) { return d; } #endif using acc = accumulator_set<data_t, features<tag::density> >; using histogram_type = iterator_range<std::vector<std::pair<data_t, data_t> >::iterator >; template <typename T> class data_filler { public: data_filler(){} T operator()() { return rand()/(T)RAND_MAX; } }; template <> class data_filler<duration_t> { public: data_filler(){} duration_t operator()() { return std::chrono::milliseconds(rand()/RAND_MAX); } }; int main(int argc, char** argv) { //create some random data std::vector<data_t> data(100); std::generate(data.begin(), data.end(), data_filler<data_t>()); int c = data.size();//cache size for histogramm. //create an accumulator acc myAccumulator( tag::density::num_bins = 20, tag::density::cache_size = 10); //fill accumulator for (int j = 0; j < c; ++j) { myAccumulator(data[j]); } auto hist = density(myAccumulator); data_t total = construct(0.0); for( int i = 0; i < hist.size(); i++ ) { // std::cout << "Bin lower bound: " << hist[i].first << ", Value: " << hist[i].second << std::endl; total += hist[i].second; } //std::cout << "Total: " << total << std::endl; //should be 1 (and it is) return 0; }

1 0

boost::icl::contains question
by Sanchay Harneja 09 Feb '17

09 Feb '17

Hi, boost::icl::interval_map<int, boost::icl::interval_map<int, boost::icl::interval_set<int>>> larger, smaller; larger.add(make_pair(boost::icl::discrete_interval<int>::closed(102,104), boost::icl::interval_map<int, boost::icl::interval_set<int>>{ make_pair(boost::icl::discrete_interval<int>::closed(0,0), boost::icl::interval_set<int>{boost::icl::discrete_interval<int>::closed(2,4)})})); smaller.add(make_pair(boost::icl::discrete_interval<int>::closed(103,103), boost::icl::interval_map<int, boost::icl::interval_set<int>>{ make_pair(boost::icl::discrete_interval<int>::closed(0,0), boost::icl::interval_set<int>{boost::icl::discrete_interval<int>::closed(3,3)})})); cout << larger << endl; cout << smaller << endl; cout << boost::icl::contains(larger, smaller) << endl; cout << ((smaller & larger) == smaller) << endl; As given above, I'm trying to check if smaller is subset of larger. But I get following output: {([102,104]->{([0,0]->{[2,4]})})} {([103,103]->{([0,0]->{[3,3]})})} 0 1 Any reason why boost::icl::contains(larger, smaller) doesn't work but ((smaller & larger) == smaller) works? Thanks.

1 0

Thread safe full duplex sockets
by Christi258 08 Feb '17

08 Feb '17

This question has been asked many times, but I'm still not satisfied with the answers. I want to use a socket in full duplex: 1. asynchronously: with async_read, async_write (multiple threads running io_service.run()) 2. synchronously: with read and write in two distinct threads I am pretty sure that 1. is thread safe using strands. But I can find no information about 2. Please refere to any official documents of boost. -- View this message in context: http://boost.2283326.n4.nabble.com/Thread-safe-full-duplex-sockets-tp469155… Sent from the Boost - Users mailing list archive at Nabble.com.

2 1

[serialization] Object reference tracking on instances bug?
by Robert P 07 Feb '17

07 Feb '17

In my serialize function I am exporting a class which is a template wrapper around std:vector. template <typename E> class MyArray { public: vector<E> array; ... template <typename Archive> void MyArray::serialize(Archive & ar, const unsigned int version) { ar & BOOST_SERIALIZATION_NVP(array); } } When I add unique class instance variables to this array and then serialize it to XML... ... MyArray<Color> colorsArray; Color a; a.name = "one"; colorsArray.add(a); Color b; b.name = "two"; colorsArray.add(b); ... template <typename Archive> void MyColorsObject::serialize(Archive & ar, const unsigned int version) { ar & BOOST_SERIALIZATION_NVP(colorsArray); } Sometimes the XML comes out using object_id_reference instead of the unique values, and this then gets improperly unserialized with incorrect values, i.e. both colors will have "one" as the name. I was able to disable object tracking and it works now, but I don't think it should be doing object reference tracking on instance variables. Is it because of the template wrapper around vector?

4 4

[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

Re: [Boost-users] Boost iostreams for binary data
by Bjorn Reese 06 Feb '17

06 Feb '17

On 01/31/2017 09:25 PM, Robert Dailey wrote: > 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>`. Do they work with arrays?

2 3

[clang-win][bjam][context] '-c' is not recognized as an internal or external command
by Mikhail Strelnikov 06 Feb '17

06 Feb '17

Hello Boost, I'd like to build Boost.Context with clang on Windows with BB. There are my files: site-config.jam: using clang-win : : "C:/Program Files/LLVM/bin/clang-cl.exe" : <compatibility>vc14 <cxxflags>-Xclang <cxxflags>-std=c++1z <cxxflags>-DBOOST_USE_WINDOWS_H <cxxflags>-DNOMINMAX <cxxflags>-DWIN32_LEAN_AND_MEAN <cxxflags>-D_HAS_AUTO_PTR_ETC=1 ; Jamroot: local BOOST_ROOT = [ modules.peek : BOOST_ROOT ] ; project main : source-location . : requirements <include>$(BOOST_ROOT) <define>BOOST_ALL_NO_LIB=1 ; use-project /boost : $(BOOST_ROOT) ; exe main : main.cpp /boost//coroutine /boost//date_time ; main.cpp int main() {} I run the command: b2.exe -d+2 toolset=clang-win address-model=64 link=static runtime-link=static release -sBOOST_ROOT=D:\path\to\boost This gives me following error: clang-win.compile.asm D:\path\to\boost\bin.v2\libs\context\build\clang-vc14-win\release\link-static\runtime-link-static\threading-multi\asm\make_x86_64_ms_pe_gas.obj -c -Zp4 -Cp -Cx -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTEXT_SOURCE -DBOOST_DISABLE_ASSERTS -DNDEBUG -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTEXT_SOURCE -DBOOST_DISABLE_ASSERTS -DNDEBUG /W3 -Fo "D:\path\to\boost\bin.v2\libs\context\build\clang-vc14-win\release\link-static\runtime-link-static\threading-multi\asm\make_x86_64_ms_pe_gas.obj" "D:\path\to\boost\libs\context\src\asm\make_x86_64_ms_pe_gas.asm" '-c' is not recognized as an internal or external command, Am I doing something wrong? Thanks.

2 4

[mpl] Working with map, copy and back_inserter
by ☂Josh Chia (謝任中) 05 Feb '17

05 Feb '17

I'm trying to implement a compile-time topological sort of the DAG representing a certain dependency relationship between my classes. One of the data structures I can use to implement topological sort is a map, so I'm trying to use mpl::map using mpl::size_t<> as key. The documentation doesn't define key equality for mpl::map, but I assume it's effectively std::is_same<>. If so, I think I have a problem. In the following code, the last two lines fail static_assert(). The essence of the problem is that my attempt to construct/build my keys using copy with back_inserter does not give me a mpl::vector<> of mpl::size_t<> that is_same to Count, the expected value. It does give me a sequence, and the elements have the right value and value_type but they are not is_same to the expected size_t<> types. So, if I use the elements together with the size_t<> in an mpl::map, won't they be considered to be different keys? Josh #include <type_traits> #include <boost/mpl/at.hpp> #include <boost/mpl/back_inserter.hpp> #include <boost/mpl/copy.hpp> #include <boost/mpl/equal.hpp> #include <boost/mpl/equal_to.hpp> #include <boost/mpl/range_c.hpp> #include <boost/mpl/size_t.hpp> #include <boost/mpl/vector.hpp> using namespace std; namespace mpl = boost::mpl; using Empty = typename mpl::vector<>; using Count = mpl::vector<mpl::size_t<0>, mpl::size_t<1>>; using ConstructedCount = typename mpl::copy< typename mpl::range_c<size_t, 0, 2>, mpl::back_inserter<Empty>>::type; using The0 = typename mpl::at<ConstructedCount, mpl::size_t<0>>::type; using The1 = typename mpl::at<ConstructedCount, mpl::size_t<1>>::type; static_assert(mpl::equal<Count, ConstructedCount, mpl::equal_to<mpl::_1, mpl::_2>>::value, "succeeds"); static_assert(The1::value == 1, "succeeds"); static_assert(std::is_same<typename The1::value_type, size_t>::value, "succeeds"); static_assert(std::is_same<Count, ConstructedCount>::value, "fails"); static_assert(std::is_same<The1, mpl::size_t<1>>::value, "fails");

2 1

[mpl] at<> behaves differently for vector_c<> and vector<>
by ☂Josh Chia (謝任中) 05 Feb '17

05 Feb '17

I asked earlier in a post "[mpl] Working with map, copy and back_inserter". This is a related question. The common question is: What does compile-time equality means in MPL, particularly for map and set key equality? Does it mean std::is_same? The following code works whether USE_VECTOR_C is defined as 0 or 1 -- the last 2 lines are static_asserts that have conditions determined by USE_VECTOR_C so that they succeed, highlighting the difference in behavior between USE_VECTOR_C == 0 and USE_VECTOR_C == 1. USE_VECTOR_C == 0 is the normal case where everything is working as I expect. USE_VECTOR_C == 1 is the unexpected case where the static_asserts in the last 2 lines have conditions altered so that they succeed. Why do vector_c and vector give me different "element values"? In general, what should I be careful about when trying to use the "compile-time values" as keys to avoid the situation elucidated by the last line, where I expect two "compile-time values" to be the same but they are not, resulting in two set/map items instead of one? To clarify, I'm using boost 1.63 with gcc 6.3.1 and -std=c++14 on Arch Linux. Josh #include <type_traits> #include <boost/mpl/at.hpp> #include <boost/mpl/insert.hpp> #include <boost/mpl/set.hpp> #include <boost/mpl/size.hpp> #include <boost/mpl/size_t.hpp> #include <boost/mpl/vector.hpp> #include <boost/mpl/vector_c.hpp> using namespace std; namespace mpl = boost::mpl; #define USE_VECTOR_C 0 using Zero = mpl::size_t<0>; #if USE_VECTOR_C == 1 using Vector = mpl::vector_c<size_t, 0>; #else using Vector = mpl::vector<Zero>; #endif using ZeroElt = typename mpl::at<Vector, Zero>::type; using EmptySet = mpl::set<>; using NonEmptySet = typename mpl::insert<typename mpl::insert<EmptySet, Zero>::type, ZeroElt>::type; static_assert(ZeroElt::value == 0, ""); static_assert(is_same<ZeroElt::value_type, size_t>::value, ""); static_assert(is_same<ZeroElt, Zero>::value == !USE_VECTOR_C, ""); static_assert(mpl::size<NonEmptySet>::value == USE_VECTOR_C + 1, "");

2 1

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

Can I config process_id to log file name in the .ini setting file using Boost.Log?
by Bruce 04 Feb '17

04 Feb '17

Hi, I am using Boost.Log to output log file and using .ini file to config it. Now I need to start the exe file from the same directory for more than two instance with different start id, something like this: >start my_app.exe 1 >start my_app.exe 2 But currently only the first instance output the log content and the second one can't get the log file because the two exe uses the same log file. So I need to tell the app to use the different log file. So I want to config the .ini file to add process_id to the output file name, but I don't know how? I want to config the ini file like this but it failed:-( FileName="./log/mylog_%ProcessID%.log" Is there a way to add precess id to the output file name? Thanks.

1 0

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

Mail List Migration - Update
by Michael Caisse 02 Feb '17

02 Feb '17

The Boost mail lists are now migrated to a new set of servers. This change affected all mail lists and web resources (signing up, changing passwords, moderator access, archives...) that were associated with the domain lists.boost.org . If you are having difficulties, please drop me an email. (Oh the irony) Happy coding! michael -- Michael Caisse Ciere Consulting ciere.com

1 0

Mail Lists Migrate at 00:00 UTC Feb 3
by Michael Caisse 02 Feb '17

02 Feb '17

The following mail lists will be switched to new infrastructure at 00:00 UTC on February 3rd. There will be a small interruption while the DNS/MX records propagate. * Boost - Boost developers' mailing list * Boost-announce - Boost announce-only mailing list * Boost-bugs - Bugs reported/updated through Boost's Trac * Boost-build - Boost.Build developer's and user's list * Boost-cmake - Discussion of the CMake-based build system for Boost * Boost-commit - Boost Subversion commit messages * Boost-docs - Discussion of Boost Documentation * Boost-Interest - Moderated announcements of interest to the Boost community. * Boost-maint - Boost community maintenance mailing list * Boost-mpi - Discussion of Boost.MPI development * Boost-test - Test list for the boost mailing lists * Boost-Testing - Running Boost regression tests * Boost-users - Boost Users mailing list * Geometry - Boost.Geometry library mailing list * glas - Generic Linear Algebra Software * proto - Discussions about Boost.Proto and DSEL design * threads-devel - Discussions about the boost.thread library * ublas - ublas mailing list -- Michael Caisse Ciere Consulting ciere.com

1 0

Cross compiling context library of boost for windows 32 on a linux 64-bit machine
by Jack Kumba 01 Feb '17

01 Feb '17

Hello, Did someone succeed cross compiling context library of boost for windows 32 on a linux 64-bit machine? OR Is it even possible? I see the following error: libs/context/src/unsupported.cpp:7:2: error: #error "platform not supported" #error "platform not supported" Also, there is this ticket on this issue https://svn.boost.org/trac/boost/ticket/7262 Please advise me. Thanks, Jack

1 0

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

How to compile boost-thread for Universal Windows?
by Petr Hudeček 31 Dec '16

31 Dec '16

Hello, I'm trying to use the boost-thread library in a Windows Runtime (UWP) project. The tutorial at https://blogs.msdn.microsoft.com/vcblog/2014/07/18/using-boost-libraries-in… doesn't seem to work anymore. If I compile boost sources, either from the primary distribution, or from https://github.com/wpbest/Boost, I can compile it as a static library but when I link to it from the project, I receive linker errors that four identifiers could not be found. These identifiers are API functions such as CreateWaitableTimer. Is there a way to use boost-thread from a UWP project despite this? Perhaps setting some preprocessor symbols? Thank you, Petr Hudecek

4 5

Echo AsyncReadStream/AsyncWriteStream example
by Adam Zegelin 30 Dec '16

30 Dec '16

Hi. Is there a boost::asio example that shows an implementation of AsyncReadStream/AsyncWriteStream that copies write->read? i.e. echoes what was sent I’m trying to emulate serial device that takes input commands separated by \r, executes them, and then outputs the result. i.e., I'm trying to create a fake asio::serial_port that can read input, process it and then provide output. The device I'm trying to emulate echoes the sent characters. Commands are executed once '\r' is received. Ideally the fake serial port also echos the received data immediately. I've got the read part working by implementing async_write_some(…), but I'm having trouble implementing the async_read_some(…) method so that it can be called at anytime, especially when io_service.run() is run from multiple threads. Thanks, Adam

1 0

Boost 1.63.0 is released!
by Marshall Clow 28 Dec '16

28 Dec '16

Release 1.63.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains numerous enhancements and bug fixes for existing libraries. For details, including download links, see http://www.boost.org/users/news/version_1.63.0 You can also download directly from SourceForge: https://sourceforge.net/projects/boost/files/boost/1.63.0/ To install this release on your system, see http://www.boost.org/doc/libs/release/more/getting_started/index.html Thanks to everyone who participated in this release. Thanks, --The Boost release team Vladimir Prus Rene Rivera Marshall Clow Eric Niebler Daniel James Beman Dawes

2 1

[msm] Transitions not atomic with orthogonal regions
by Stian Zeljko Vrba 26 Dec '16

26 Dec '16

I have spent almost an hour debugging the following issue. I have a "main" orthogonal region with a couple of states and an "error" region with RUNNING and PAUSED states, like this: struct PAUSED : public msm::front::interrupt_state<new_job> {}; struct RUNNING : public msm::front::state<> {}; There are transitions PAUSED --new_job--> RUNNING and RUNNING --failed--> PAUSED. Then, in one of the main states, I have struct MAIN_STATE1 : public msm::front::state<> { template<typename Event, typename FSM> void operator()(const Event& e, FSM& fsm) { if (error_condition) fsm.process_event(failed{}); } } and in the FSM I have using initial_state = mpl::vector<MAIN_STATE0, PAUSED>; Now, when new_job is processed and MAIN_STATE1::on_entry called, the machine is in (MAIN_STATE1, PAUSED). In this state, process_event(failed{}) is ignored and not queued because PAUSED is interrupt state. Then, the next orthogonal region is processed and the machine goes into (MAIN_STATE1, RUNNING), which destroys the rest of the logic around which the FSM is designed... Adding using active_state_switch_policy = msm::active_state_switch_after_exit; to the machine did not help in any way. Reordering the states in initial_state fixed the problem, but this is a rather unsatisfactory fix because it doesn't solve the underlying problem of transition atomicity. This is counter-intuitive, being on the border between a bug and lack of clear documentation. Specifically: 1. State switch should be atomic. By using active state switch after exit, I had *expected* that first all exit handlers of the current state are called, the state is atomically switched to the new state, and then all entry handlers are called. What I have *observed* is that on_entry handler of a state in one orthogonal region is called before the other orthogonal region has switched *its* state. Thus, with orthogonal regions, the machine can be in an "impossible" intermediate combination of states. Because not all side-effects have run, this has consequences for all actions/guards acting on state or FSM data, which is illustrated by the following: 2. process_event eagerly evaluates is_event_handling_blocked_helper for each orthogonal region in order. The event should be queued unconditionally, and only after the transition has completed, the machine should dequeue events and check whether processing is blocked etc. This, I think, would make at least process_event to appear atomic wrt state switch. Which leads me to conclude that MSM is seductively declarative on the surface, but that it's rather tricky operationally.

1 0

Boost 1.63.0 Release Candidate 2
by Marshall Clow 25 Dec '16

25 Dec '16

The second release candidate for the 1.63.0 release is now available at: https://sourceforge.net/projects/boost/files/boost/1.63.0/ The only changes are in Boost.Config, Boost.Context, and Boost.Fiber. The SHA256 checksums are as follows: 25db3956a8d58187ac7a0702cc917e9bab47ff90baafc35e4e789dca1ce5f423 boost_1_63_0_rc2.7z beae2529f759f6b3bf3f4969a19c2e9d6f0c503edcb2de4a61d1428519fcb3b0 boost_1_63_0_rc2.tar.bz2 fe34a4e119798e10b8cc9e565b3b0284e9fd3977ec8a1b19586ad1dec397088b boost_1_63_0_rc2.tar.gz 97ce6635df1f44653a597343cd5757bb8b6b992beb3720f5fc761e3644bcbe7b boost_1_63_0_rc2.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The release managers

2 2

cross compile application include boost-lib
by Thomas Schmiedl 24 Dec '16

24 Dec '16

Hello, I try to use this application https://github.com/repetier/Repetier-Server on my mips-based router. Sorry, I'm not a developer. Please could someone explain the cross-compiling steps for Linux (I use Ubuntu 14 x86 as build system). gcc/g++ toolchain for mips is from this project http://freetz.org/wiki/help/howtos/common/newbie.en. Do I have also to cross-compile boost for mips or only install the Ubuntu-source-package (sudo apt-get install libboost-all-dev). Thanks for your help and best regards, Thomas

2 2

[boost] [build] [context] Mac build options for Boost.Context
by Nat Goodspeed 23 Dec '16

23 Dec '16

Building Boost 1.57 on OS X 10.11, but building it *for* OS X down to 10.9, we're passing bjam a cxxflags command-line argument including -mmacosx-version-min=10.9. We see that switch (along with our other cxxflags switches) in most "g++" lines in the build output, since we also pass -d2 -d+4. But for the assembly source files in Boost.Context, the lines do not contain our requested -mmacosx-version-min switch. In fact they don't seem to contain any of our cxxflags switches. As a result, the assembly object files are built for the OS X version on the build host, 10.11. At executable link time, this produces messages: ld: warning: object file (packages/lib/Release/libboost_context-mt.a(jump_x86_64_sysv_macho_gas.o)) was built for newer OSX version (10.11) than being linked (10.9) ld: warning: object file (packages/lib/Release/libboost_context-mt.a(make_x86_64_sysv_macho_gas.o)) was built for newer OSX version (10.11) than being linked (10.9) (These are the only two .o files producing such messages.) I'm afraid that the resulting executable won't run on OS X 10.9 or 10.10, and that segment of the population is still interesting to us. How should we propagate the cxxflags=-mmacosx-version-min=10.9 feature to the assembler command for Boost.Context?

2 2

Units: Are scales for bytes really working?
by Akim Demaille 21 Dec '16

21 Dec '16

Hi, I’m trying to run the example given in http://www.boost.org/doc/libs/1_62_0/doc/html/boost_units/Examples.html#boo…, and the result is puzzling. $ cat foo2.cc #include <iostream> #include <boost/units/systems/information/byte.hpp> #include <boost/units/io.hpp> using namespace std; using boost::units::binary_prefix; using boost::units::engineering_prefix; using boost::units::no_prefix; using boost::units::symbol_format; using boost::units::quantity; using boost::units::information::byte_base_unit; int main() { cout << BOOST_VERSION << endl; // Don't forget that the units name or symbol format specification is persistent. cout << symbol_format; // Resets the format to the default symbol format. quantity<byte_base_unit::unit_type> b = 2048. * byte_base_unit::unit_type(); cout << b << endl; cout << engineering_prefix << b << endl; // 2.048 kb cout << symbol_format << binary_prefix << b << endl; // "2 Kib" } $ g++-6 foo2.cc -o foo2 $ ./foo2 106200 2048 B 16.384 kb 16 Kib What am I doing wrong? Note that there are a couple of issues in the example as given: - there should not be any endl after cout << symbol_format; - using ‘\n’ instead of endl, too many people seem to believe that std::endl is the normal way to end the lines - it would be nice to provide all the needed includes

1 0

Re: [Boost-users] [boost] Stacktrace library starts review today 14th Dec
by Antony Polukhin 17 Dec '16

17 Dec '16

2016-12-17 20:51 GMT+03:00 Andrey Semashev <andrey.semashev(a)gmail.com>: <...> > That said, I'd like to thank Antony for the submission and encourage > him to continue his work on the library. The library does try to fill > an important gap. Thank you for the review! I'd like to discuss a proposed changes. Thing that I'm worried about: * replacing class `stacktrace` with vector<void*> will definitely break the most common use case std::cout << get_stacktrace(); as it's not a good idea to overload ostream operator for vector of void pointers * addr2line and forking is not nice. Is linking with a GPL licensed code an acceptable alternative? * removing `basic_stacktrace` will definitely remove all the possibilities for optimization of caching COM/parsed DWARF. This is a quick win that later may turn into big troubles. -- Best regards, Antony Polukhin

1 0

Trouble with std::forward and fusion vector using clang 3.4 and older library - is there a workaround?
by Stan Blakey 16 Dec '16

16 Dec '16

I am trying to compile using clang 3.4 and -std=c++11. With the -std=c++11 it compiles and runs without any issue. With -std=c++11 I get boost_1_60_0\boost/fusion/container/vector/vector.hpp:126:20: error: no template named 'forward' in namespace 'std'; did you mean 'advance_detail::forward'? return std::forward<result>(*advance_c<N>(begin(seq))); and many similar errors. I have tried all the boost BOOST_NO_CXX11_HDR_ macros but not found one that resolves this issue. I don't have any choice about compiler version or library version due to other constraints. Any suggestions appreciated, Stan *#include* <boost/fusion/tuple.hpp> *#include* <boost/fusion/algorithm.hpp> *#include* <string> *#include <iostream>* *using* *namespace* boost::fusion; *struct* print { *template* <*typename* *T*> *void* *operator()*(*const* *T* &t) *const* { std::cout << std::boolalpha << t << '\n'; } }; *int* *main*() { *typedef* tuple<*int*, std::string, *bool*, *double*> tuple_type; tuple_type t(10,"Boost", *true*, 3.14); for_each(t, print()); }

2 4

Boost 1.63.0 Release Candidate 1
by Marshall Clow 15 Dec '16

15 Dec '16

The release candidates for the 1.63.0 release are now available at: https://sourceforge.net/projects/boost/files/boost/1.63.0/ The SHA256 checksums are as follows: 010699561c6011e6d97dc453d55bc5e54cdc192622434eff7b8ac559efac846c boost_1_63_0_rc1.7z d8ebf8d90b2f823f04119445ac339d704395d655907333ec0fab863040119d24 boost_1_63_0_rc1.tar.bz2 dabe29b8a60369ae7c15c20681a32717f3c37d97e5dc6d39c5b2fd0494b8e995 boost_1_63_0_rc1.tar.gz 1683942022fd63c205c48fb2155af6094c67ef67aa13ffb3e1db78fecf817efe boost_1_63_0_rc1.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The release managers

7 12