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

[hana] create aribtrary tuples of integral_constants
by Steve Lorimer 19 Apr '17

19 Apr '17

Making use of Scott Schurr's str_const ( https://github.com/boostcon/cppnow_presentations_2012/blob/master/wed/schur…) I have a constexpr string. class StrConst { public: template<size_t N> constexpr StrConst(const char (&str)[N]) : str_(str) , len_(N - 1) { static_assert(N > 1, "not a string"); } constexpr operator const char*() const { return str_; } constexpr size_t size() const { return len_; } constexpr char operator[] (size_t i) const { return i < len_ ? str_[i] : throw std::out_of_range("invalid index"); } private: const char* const str_; const size_t len_; }; I have another constexpr function which returns the position of the first caret found in a string, starting from position n: constexpr int caretPos(const StrConst& str, size_t n = 0) { if (n == str.size()) return -1; if (str[n] == '^') return n; return caretPos(str, n+1); } I can use the results of caretPos to create a typedef for a std::tuple of std::integral_constants, where the size of the tuple is the number of carets found in the string, and each tuple element is an integral constant whose value is the position of the caret in the string. Here I manually construct this tuple: int main() { constexpr StrConst s("hello^world^"); constexpr int pos1 = caretPos(s); constexpr int pos2 = caretPos(s, pos1+1); using P1 = std::integral_constant<int, pos1>; using P2 = std::integral_constant<int, pos2>; using PosTuple = std::tuple<P1, P2>; static_assert(std::tuple_element_t<0, PosTuple>::value == 5, ""); static_assert(std::tuple_element_t<1, PosTuple>::value == 11, ""); } Question: I would now like to generalise this for any input string with any number of carets. template<size_t... Ns> using PosTuple = std::tuple<std::integral_constant<int, Ns>...>; How can I generate the sequence of Ns... required here using caretPos or some other means?

2 1

[release] Boost 1.64.0 Release Candidate 1
by Rene Rivera 17 Apr '17

17 Apr '17

The release candidates for the 1.64.0 release are now available at: <https://dl.bintray.com/boostorg/beta/1.64.0.rc.1/> The SHA256 checksums are as follows: 49c6abfeb5b480f6a86119c0d57235966b4690ee6ff9e6401ee868244808d155 boost_1_64_0_rc1.7z 7bcc5caace97baa948931d712ea5f37038dbb1c5d89b43ad4def4ed7cb683332 boost_1_64_0_rc1.tar.bz2 0445c22a5ef3bd69f5dfb48354978421a85ab395254a26b1ffb0aa1bfd63a108 boost_1_64_0_rc1.tar.gz b99973c805f38b549dbeaf88701c0abeff8b0e8eaa4066df47cac10a32097523 boost_1_64_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 Boost Release Team -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

2 1

Serialization support for colony container
by Brian Wood 17 Apr '17

17 Apr '17

Shalom It's looking like Matthew Bentley's colony container -- http://plflib.org -- is going to pass over Boost on it's way to the standard. I've added serialization support for this container to the C++ Middleware Writer and added some code that tests that support to my repo -- https://bitbucket.org/webenezer/onwards . I enjoyed Jon Kalb's CppChat show where he talked to Matthew about this container -- http://www.slashslash.info/cppchat/ https://www.youtube.com/watch?v=SFAJ238rBNw -- Brian Ebenezer Enterprises - In G-d we trust. http://webEbenezer.net

2 1

[CallableTraits] Review results
by Louis Dionne 17 Apr '17

17 Apr '17

Dear Boost, I am pleased to announce that the CallableTraits library is CONDITIONALLY ACCEPTED into Boost. I counted the following formal reviews: - Bruno Dutra: Yes - Emil Dotchevski: Yes - John P. Fletcher: Yes - Klemens Morgenstern: Yes - Peter Dimov: Yes - Zach Laine: Yes The following people also participated to the review by providing informal feedback: - Edward Diener - Gavin Lambert - Niall Douglas - Paul Fultz II - Tim Song I also based my decision on previous experience I've had using the library, and some issues we faced in the Standard Committee where we could have used CallableTraits. I'd like to thank everyone who participated to the review for their feedback, and also Barrett Adair for his submission. The following lists the conditions for acceptance, and also summarizes the general feedback received during the review. GitHub issues are leveraged to make the tracking of these comments easier. Below, whenever I refer to #XYZ, the corresponding ticket can be found at https://github.com/badair/callable_traits/issues/XYZ To see all the issues that were discussed during the review, you can search for tickets labeled with `review` on GitHub (please allow some time for Barrett to update the new issues I just filed): https://github.com/badair/callable_traits/issues?page=1&q=+label%3Areview Conditions for acceptance ------------------------- The following are points that must be addressed for the library to be accepted. Once all of the associated GitHub issues are closed, I ask that the author post to this list with links to the closed issues. Unless major problems (having to do with the closed issues) are raised at that time, the library will be automatically accepted into Boost, no additional review required. - The library needs to clearly document the advantages of CallableTraits over FunctionTypes. Concrete examples must be given (at least one, preferably two). See #117. - The level of C++ conformance required for the whole library needs to be clearly stated in the documentation. Individual components should only document divergences from that base level of conformance. The current state of things is quite confusing for users. See #118. - The "algorithmic" parts of the library must be removed, since they are out of scope. This has already been partly done in issue #114, but the following algorithms must be discussed too (let's follow up in #114): + args_at + clear_args + pop_front_args + push_front_args + expand_args_right + expand_args_left - The lazy metafunctions and predicate traits should be SFINAE-friendly, just like the aliases are. I think this inconsistency is a big deal, enough to be a condition for acceptance. See #134. Summary of the feedback received -------------------------------- The following is a compilation of other points that were made during the review, but which are not requirements for acceptance. I trust, but do not require, that all of those points will be considered by the author: - There is a loss of information with the `args` metafunction. For example, `void(T)` and `void(T, ...)` both give the same result. See #132. - Consider adding a way of obtaining the parameter list of a function without the type of `*this`. See #133. - The documentation uses the terms of art "implementation defined" and "undefined behavior" incorrectly. See #103 and #131. - The non-reference documentation should present at least one real-world use case. See #116. - The library should handle top-level cv-qualifiers. See #106. - Consider supporting different calling conventions (e.g. `__cdecl`). See #102. - Consider adding a pre-C++17 implementation of `is_invocable` and friends. See #119. - The documentation should clearly state that the library can be used without the rest of Boost. See #99. - Consider combining `expand_args` and `args` into a single metafunction with a default "output" parameter of `std::tuple`. See #126. - Consider adding `make_fn` and `make_mem_fn` metafunctions to construct a signature from a return type and a tuple of the arguments. See #113. - Consider renaming some traits, like `is_reference_member`. See #108. - Reword some parts of the documentation that look odd due to the use of passive tense. See #105. - Consider adding a version of `apply_member_pointer` which carries cv-qualifiers. See #138. - Consider adding `remove_member_cv_ref` and `copy_member_cv_ref`. See #139. - Why does `qualified_parent_class_of` always returns a const& for PMDs? See #112. - Why does `qualified_parent_class_of` return a ref-qualified type even for unqualified PMFs? See #112. A few of my own comments: - Consider using alphabetical order in the table of contents of the reference. See #135. - Consider renaming `apply_member_pointer` to something like `make_member`. See #136. - Consider dropping the `parent_` in `parent_class_of`, or adding a note to justify the name. See #137. Again, thanks to everyone who participated in the review, and congratulations to Barrett for his work! Regards, Louis Dionne

1 0

How to setup log directory in an directory that is not fixed?
by Bruce 17 Apr '17

17 Apr '17

Hi, I am using boost.Log. I config the log using a logconfig.ini file. Now the requirement changed, we need to put the log in an directory specific to a login account. The account may change so we have to first create the directory then set the log output file to this directory. I tried to first log the logconfig.ini and then set the logging::add_file_log(...), but the file path set in the .ini files created too. If I don't setup the FileName in the .ini file, it throws a exception. Is there anyway to set the path and the file name separately? Or change the file path after loading the .ini config file? Thanks

1 0

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

16 Apr '17

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

2 1

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

16 Apr '17

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

4 6

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

16 Apr '17

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

2 1

Howard Hinnant
by Leo Carreon 16 Apr '17

16 Apr '17

Hi Boost Users, Does any know how to contact Howard Hinnant by email? Kind regards, Leo

3 3

What is the effective way to use boost::asio::deadline_timer for udp socket receive_from?
by jupiter 14 Apr '17

14 Apr '17

Hi, My program needs a sync udp socket send / receiver so I use the deadline_timer as timeout for udp socket receive_from on Debian Jessie: boost::asio::deadline_timer deadline(io_service, boost::posix_time::seconds(2)); In checkDeadline function, when the timer expires, it calls socket.cancel, otherwise calls the deadline.async_wait(checkDeadline); again. Apparently when the program runs to socket.receive_from(), it is blocked and the timer is never called because both socket.receive_from and the timer in the same thread. I've been thinking to run the timer in another thread, but I checked Internet, there are comments said deadline_timer is not thread safe, please correct me if I am wrong here. It will be a simple solution for me if I can run timer on another thread. Anyone has other ideas to run the timer effectively? Appreciate your comments. Thank you.

4 8

Re: [Boost-users] udp::endpoint listen_endpoint invalid argument
by Bjorn Reese 12 Apr '17

12 Apr '17

On 04/11/2017 07:32 AM, jupiter via Boost-users wrote: > To simplify it, I changed to: > udp::endpoint listen_endpoint( > boost::asio::ip::address::from_string("localhost"), 15555); Quoting the documentation: "from_string Create an address from an IPv4 address string in dotted decimal form, or from an IPv6 address in hexadecimal notation." You need to resolve "localhost" first.

3 2

udp::endpoint listen_endpoint invalid argument
by jupiter 11 Apr '17

11 Apr '17

Hi, I built doc/html/boost_asio/example/timeouts/blocking_udp_client.cpp on Debian Jessie, but when I run it, I got Invalid argument on the statement of udp::endpoint listen_endpoint( boost::asio::ip::address::from_string(argv[1]), std::atoi(argv[2])); To simplify it, I changed to: udp::endpoint listen_endpoint( boost::asio::ip::address::from_string("localhost"), 15555); Appreciate any clues what's wrong with that statement and why it caused invalid argument? Thank you.

2 1

Thread Pool example
by Gonzalo Garramuño 10 Apr '17

10 Apr '17

Hi, I currently use boost (1.60) for my program and would like to have a part of it multithreaded (the creation of icons in a file requester). I would like to create those with a thread pool. I am currently using gcc 4.6.3, which is not yet c++11 compatible. I found no documentation on the usage of boost/thread/thread_pool.hpp so I turn to the list. Does anyone have an example of a thread pool with boost threads. Thanks in advance, -- Gonzalo Garramuño

3 3

Boost.Pool: singleton_pool - thread safe for any kind of threads?
by Igor Yakushin 07 Apr '17

07 Apr '17

Hi All, singleton_pool documentation claims that it is thread safe. It is not clear too me if this is applied to all kinds of threads or only the ones from Boost library. For example, I am using OpenMP which is external to Boost. Would singleton_pool still be thread safe or do I need to redefine Mutex? What if I later decide to use some other kind of threads like Intel Cilk Plus or TBB? Thank you, Igor

2 1

Boost Asio not built
by Balázs Bámer 07 Apr '17

07 Apr '17

Hi All, I have downloaded Boost 1.63 the second time. On my home computer, building it yielded all libraries. However, I do similar now at work, and it won't build Asio. First I do ./bootstrap.sh --with-libraries=all Then I build, but these are the results: balazs@bamer-debian:/opt/boost-1.63$ ls stage/lib/ |grep asio|wc 0 0 0 Although there are cpp files, that should be turned into a linbrary: balazs@bamer-debian:/opt/boost-1.63$ find |grep asio |grep cpp$|wc 214 214 9862 Asking bootstrap about what it would do shows it is not willing to build Asio: balazs@bamer-debian:/opt/boost-1.63$ ./b2 --show-libraries The following libraries require building: - atomic - chrono - container - context - coroutine - coroutine2 - date_time - exception - fiber - filesystem - graph - graph_parallel - iostreams - locale - log - math - metaparse - mpi - program_options - python - random - regex - serialization - signals - system - test - thread - timer - type_erasure - wave What should I do? Is there a dependency missing? Thank you in advance. Best regards: Balazs

5 6

How to design proper release of a boost::asio socket or wrapper thereof
by Christopher Pisz 06 Apr '17

06 Apr '17

I am making a few attempts at making my own simple asynch TCP server using boost::asio after not having touched it for several years. The latest example listing I can find is: http://www.boost.org/doc/libs/1_54_0/doc/html/boost_asio/tutorial/tutdaytim… The problem I have with this example listing is that it cheats and it cheats big, by making the tcp_connection a shared_ptr, such that it doesn't worry about the lifetime management of each connection. I am worried about the lifetime management of each connection. I figure the natural thing to do would be to keep some collection of tcp_connection objects or pointers to them inside tcp_server. Adding to that collection from the OnConnect callback and removing from that collection OnDisconnect. Note that OnDisconnect would most likely be called from an actual Disconnect method, which in turn would be called from OnReceive callback or OnSend callback, in the case of an error. Well, therein lies the problem. Consider we'd have a callstack that looked something like this: tcp_connection::~tcp_connection tcp_server::OnDisconnect tcp_connection::OnDisconnect tcp_connection::Disconnect tcp_connection::OnReceive This would cause errors as the call stack unwinds and we are executing code in a object that has had its destructor called...I think, right? I then thought to myself, well I could flag the tcp_connection as disconnected when it disconnects and then on some timer on the tcp_server, go through its collection and start deleting disconnected tcp_connection objects, but then the timer could fire after the flag is set, but before it returns from a OnReceive where an error occurred and I Disconnected as a response. I imagine everyone doing server programming comes across this scenario in some fashion. What is a strategy for handling it? I hope the explanation is good enough to follow. If not let me know and I will create my own source listing, but it will be very large. -- View this message in context: http://boost.2283326.n4.nabble.com/How-to-design-proper-release-of-a-boost-… Sent from the Boost - Users mailing list archive at Nabble.com.

2 1

Re: [Boost-users] How to design proper release of a boost::asio socket or wrapper thereof
by Bjorn Reese 06 Apr '17

06 Apr '17

On 04/05/2017 10:32 PM, Christopher Pisz via Boost-users wrote: > The problem I have with this example listing is that it cheats and it cheats > big, by making the tcp_connection a shared_ptr, such that it doesn't worry > about the lifetime management of each connection. That is not cheating. > Consider we'd have a callstack that looked something like this: > tcp_connection::~tcp_connection > tcp_server::OnDisconnect > tcp_connection::OnDisconnect > tcp_connection::Disconnect If Disconnect is an asynchronous operation, then it should not call OnDisconnect directly. You can post it on the io_service instead. > I imagine everyone doing server programming comes across this scenario in > some fashion. What is a strategy for handling it? Preferably shared_ptr, or io_service::post() if for some reason you cannot use shared_ptr, e.g. if the object has to be destroyed by a a specific thread.

3 3

[gsoc17] Help review Google Summer of Code proposals
by Niall Douglas 05 Apr '17

05 Apr '17

Dear Boost, Student proposals for Google Summer of Code are submitted, please help us decide which have the most merit. I have reduced the fifty something proposals submitted down to twenty seven which have some chance. To be able to view and rank the student proposals, please do the following: 1. Send to gsoc-admin(a)boost.org your Google login. We will invite you to view the student proposals on the Boost Google Drive. Until you receive the invitation email, you won't be able to view the proposals. 2. Go to https://goo.gl/forms/EVppdHsHMnjkcUoD3 which is a Google form where you can score the proposals. We have linked each proposal there to the Google Drive item and there you can rank a proposal between 1 and 5. Make sure you use the same email as your Google login in the form, otherwise we will ignore any forms submitted to prevent gaming the results. 3. Even if you can't rank all twenty seven proposals, try to do as many as you can and then PRESS SUBMIT at the end of the form (forgetting to press SUBMIT means we never get your rankings). The proposals are presented in random order per person so any work you do will be useful. 4. Please try to have your rankings done by Monday 10th. You may find reviewing the page at https://svn.boost.org/trac/boost/wiki/SoC2017 useful. 5. Finally, if you'd like to mentor any of the proposals, send to gsoc-admin(a)boost.org your Google login so we may invite you onto the Google website as a mentor. Many thanks in advance. Niall & Bryce

1 0

[Fusion] wide-char output
by Leo Cacciari 05 Apr '17

05 Apr '17

Hi, the documentation of the Boost.Fusion library (1.63.0) at http://www.boost.org/doc/libs/1_63_0/libs/fusion/doc/html/fusion/sequence/o… affirms that operator<< is defined in the boost::fusion namespace with the following synopsis: template <typename OStream, typename Sequence> OStream& operator<<(OStream& os, Sequence& seq); where the template parameter OStream is defined as "An output stream". Accordingly, I thought that the following would work: using boost::fusion::operator<<; fusion::vector<int, double, const char *> v = fusion::make_vector(42, 3.1415, "foobar"); std::wcout << "v = " << v << std::endl; However, the compiler (MSVC 9) complains that it has: "found no defined operator << taking a right-hand argument of type boost::fusion::vector<T0,T1,T2> with T0 = int, T1 = double, T2 = char *" If I replace std::wcout with its narrow-char sibling std::cout, everything works as expected; i.e. the code compiles and when run prints (42,3.1415, foobar). Looking into the source (file boost/fusion/sequence/io/out.hpp) it seems that the operator<< is only defined for left-hand argument of type std::ostream. Thus the questions: 1. Is this a bug and should I post a ticket about it? (I looked in the bugs database but I couldn't find it) 2. If it's a bug, are there any plan to patch it soon? 3. If not, does exist any reason why it shouldn't be patched nevertheless? If needed, I could volunteer for writing a patch. Thank for your attention -- Leo Cacciari Aliae nationes servitutem pati possunt. Populi Romani est propria libertas.

3 4

Query regarding Boost.Log
by Leo Carreon 02 Apr '17

02 Apr '17

Hi, Does Boost.Log require synchronization when multiple processes log to the same log file? Kind regards, Leo

1 0

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

31 Mar '17

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

2 1

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

31 Mar '17

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

2 1

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

30 Mar '17

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

3 6

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

30 Mar '17

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

3 3

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

30 Mar '17

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

2 1

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

30 Mar '17

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

2 2

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

29 Mar '17

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

1 0

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

29 Mar '17

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

4 13

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

29 Mar '17

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

1 0

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

29 Mar '17

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

1 0

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

28 Mar '17

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

1 1

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

28 Mar '17

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

4 5

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

28 Mar '17

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

1 0

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

27 Mar '17

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

7 20

Compile error with low_bits_mask_t
by Michael Kaes 27 Mar '17

27 Mar '17

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

1 0

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

26 Mar '17

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

1 1

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

26 Mar '17

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

5 5

License questions
by Julian D. 25 Mar '17

25 Mar '17

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

3 2

Re: [Boost-users] License questions
by Julian D. 24 Mar '17

24 Mar '17

That appears to be the definition of what license they wanted, not the actual license. The license body makes it unclear if I can use this in a closed-source commercial environment On Thu, Mar 23, 2017 at 3:51 PM, <boost-users-request(a)lists.boost.org> wrote: > > Message: 5 > Date: Thu, 23 Mar 2017 17:54:04 +0100 > From: Mateusz Loskot <mateusz(a)loskot.net> > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] License questions > Message-ID: > <CABUeae_a-cNCdw00fYN4Gyb_a7Gk_QOo7cARXNo3Lh8eXAAVtQ@ > mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On 23 March 2017 at 17:38, Julian D. via Boost-users > <boost-users(a)lists.boost.org> wrote: > > I am making a confidential commercial closed-source program, and Boost's > > libraries seem useful for me. I can't tell if the Boost license allows > me to > > include it in closed-source. Would anybody know? > > http://www.boost.org/users/license.html#requirements > > 2nd bullet > > Best regards, > -- > Mateusz Loskot, http://mateusz.loskot.net

4 4

[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