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

Boost ASIO write: Socket operation on non-socket
by Sharma, Nishant 11 Jan '18

11 Jan '18

Hi, I cannot post the complete program, but when I do asio::write , I get the error: write: Socket operation on non-socket Now, just before that I check if the socket is opened or not and it indeed is opened. io_service is also running.. I just need some pointers and possible cause for this so that I can debug and take his further... My use model is I call asio::write which is synchronous and for reading I use async_read which first reads the header data and then calls asio::read to read the actual data. Best Regards, Nishant Sharma

2 1

Google Summer of Code 2018
by David Bellot 10 Jan '18

10 Jan '18

Dear Boost community, once again this year, we will apply to be a mentoring organization for the Google Summer of Code 2018. Our organization has been quite succesful for the last decade and this year we hope to be selected again. As part of filling in our application for 2018, we must supply to Google a list of potential GSoC mentors and potential GSoC projects for summer 2018 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/SoC2018 before *January 23rd* would be an enormous help to getting us approved again this year and bringing to Boost another Google funding (worth dozens of thousands of dollars on average). 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. If you want to have a better chance receiving funding for your project ideas, it is better to find good students early 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. Finally, I would like to thank Niall Douglas, our previous Boost admnistrator for GSoC, who did an awesome work during many years and helped the Boost community grow thanks to all the funding we received years after years from Google. Best regards, David

1 0

1.66 changes in layout suffix seems to break cmake finder
by Stephan Menzel 09 Jan '18

09 Jan '18

Hello, I am currently trying to upgrade my projects to 1.66 and I am puzzled by a change in bjam's 'laout' parameter. I am building boost for MSVC14 (x64). Normally I use the following command line: > bjam.exe --layout=versioned variant=release address-model=64 link=static,shared runtime-link=shared threading=multi stage to achieve the build flags and setup that I need. Up until 1.65 this yielded libs named like: libboost_atomic-vc140-mt-1_65.lib This is what appears to be the most flexible for my use case and I always discover them using the 'normal' CMake finders like this: set(BOOST_ROOT ${WHERE_MY_THIRD_PARTY_STUFF_IS}/boost-1.66.0 CACHE PATH "set root of boost install") set(BOOST_INCLUDEDIR ${BOOST_ROOT}/include CACHE PATH "set boost includes") set(BOOST_LIBRARYDIR ${BOOST_ROOT}/lib CACHE PATH "set boost library dir") set(Boost_ADDITIONAL_VERSIONS "1.66.0") find_package(Boost REQUIRED COMPONENTS ...) Now over the years the meaning of the --layout parameter and its defaults have occasionally changed by I always managed to get something like this. But now, with 1.66 the filenames are changed to that: libboost_atomic-vc140-mt-x64-1_66.lib With this, CMake won't find the libs anymore. I have tried all different variantions of --layout I know (system, tagged, versioned) but I cannot get the old naming scheme back. I could rename the files manually but I am a bit afraid that this might break some linker (autolink) magick and also it doesn't seem right. Trying with several CMake finder options also got me nowhere. Using layout system is not desired as I like to quickly distinguish between versions on sight. So my question is: Is there a way to get >=1.66 to build with the filename scheme it had until now? Or is there a change to the CMake finders that will fix this? Thanks for any suggestions... Stephan

3 7

[filesystem] VS2005 compiler warnings
by Klebsch, Mario 09 Jan '18

09 Jan '18

Hi, I am using boost library 1.63.0 in an old project, which still uses VS2005. I get some compiler warnings from boost::filesystem: boost\libs\filesystem\src\unique_path.cpp(114) : warning C4267: 'argument' : conversion from 'size_t' to 'DWORD', possible loss of data boost\libs\filesystem\src\windows_file_codecvt.cpp(43) : warning C4244: 'argument' : conversion from '__w64 int' to 'int', possible loss of data boost\libs\filesystem\src\windows_file_codecvt.cpp(43) : warning C4244: 'argument' : conversion from '__w64 int' to 'int', possible loss of data boost\libs\filesystem\src\windows_file_codecvt.cpp(63) : warning C4244: 'argument' : conversion from '__w64 int' to 'int', possible loss of data boost\libs\filesystem\src\windows_file_codecvt.cpp(63) : warning C4244: 'argument' : conversion from '__w64 int' to 'int', possible loss of data boost\boost\filesystem\string_file.hpp(27) : warning C4267: 'argument' : conversion from 'size_t' to 'std::streamsize', possible loss of data boost\boost\filesystem\string_file.hpp(38) : warning C4267: 'argument' : conversion from 'size_t' to 'std::streamsize', possible loss of data I am new on boost-users, so I don't yet know, whether patches for compiler warnings are welcome, but I would like to propose some changes: For the warning in unique_path.cpp(114),I think it is safe to static_cast len to DWORD: > BOOL gen_ok = ::CryptGenRandom(handle, static_cast <DWORD>(len), static_cast<unsigned char*>(buf)); For the two lines in windows_file_codecvt.cpp, I also think that a static_cast is ok: windows_file_codecvt.cpp(42) > if ((count = ::MultiByteToWideChar(codepage, MB_PRECOMPOSED, from, windows_file_codecvt.cpp(43) > static_cast<int>(from_end - from), to, static_cast<int>(to_end - to))) == 0) windows_file_codecvt.cpp(62) > if ((count = ::WideCharToMultiByte(codepage, WC_NO_BEST_FIT_CHARS, from, windows_file_codecvt.cpp(63) > static_cast<int>(from_end - from), to, static_cast<int>(to_end - to), 0, 0)) == 0) The last two warnings are in generic parts, and changes would affect not only windows. Unfortunately, I have no good idea, on how to fix or avoid these warnings. 73, Mario -- Mario Klebsch Actia I+ME GmbH Mario.klebsch(a)ime-actia.de<mailto:Mario.klebsch@ime-actia.de> Dresdenstrasse 17/18 Fon: +49 531 38 701 716 38124 Braunschweig Fax: +49 531 38 701 88 Germany

1 0

[Boost.Asio] defer, dispatch and post differences?
by Daniel Bergström 08 Jan '18

08 Jan '18

The free functions *defer*, *dispatch* and *post* all have the exact same set of overloads and description in the library's reference (version 1.66.0). I also couldn't find anything on the subject in the *Overview* section of the library's documentation. Is the differences between them clearly described somewhere else, that I've missed, or could someone explain it? Thank you, Daniel

5 14

Boost asio reuse address
by Sharma, Nishant 07 Jan '18

07 Jan '18

Hi, Just wanted to know if setting the following option on acceptor should be ever done or not.. When should this be used.. acceptor_.set_option(boost::asio::ip::tcp::acceptor::reuse_address(true)); The reason I am asking this is because I have a server application which crashed but the socket did not close. So, the next time, I was bringing up the server, I get the error : Error occured! Error code = system:98. Message: bind: Address already in use But, even giving the option above, it is not working fine. I referred to the URL : https://stackoverflow.com/questions/34596638/boost-asio-so-reuseport to figure out the steps in which acceptor should be created from this link. Best Regards, Nishant Sharma

2 1

Building boost fails with VS2017 (v15.5.2)
by Christian Henning 06 Jan '18

06 Jan '18

This is rather strange. I have downloaded boost 1.66 and can build Boost.Build engine. But building the libs fails. The full output is here: https://pastebin.com/raw/mRriQDvq Here is what I'm seeing: ********************************************************************** ** Visual Studio 2017 Developer Command Prompt v15.5.2 ** Copyright (c) 2017 Microsoft Corporation ********************************************************************** [vcvarsall.bat] Environment initialized for: 'x64' C:\Users\chhenning\source>d: D:\>cd boost D:\boost>.\bootstrap.bat Building Boost.Build engine Bootstrapping is done. To build, run: .\b2 To adjust configuration, edit 'project-config.jam'. Further information: - Command line help: .\b2 --help - Getting started guide: http://boost.org/more/getting_started/windows.html - Boost.Build documentation: http://www.boost.org/build/doc/html/index.html D:\boost>b2 -j8 --toolset=msvc variant=release link=static runtime-link=shared address-model=64 define=_CRT_NONSTDC_NO_DEPRECATE define=_CRT_SECURE_NO_DEPRECATE define=_SCL_SECURE_NO_DEPRECATE define=_SECURE_SCL=0 define=_HAS_ITERATOR_DEBUGGING=0 define=BOOST_REGEX_MATCH_EXTRA stage Performing configuration checks - 32-bit : no (cached) - 64-bit : no (cached) - arm : no (cached) - mips1 : no (cached) - power : no (cached) - sparc : no (cached) - x86 : no (cached) - combined : no (cached) - symlinks supported : no (cached) - junctions supported : yes (cached) - hardlinks supported : yes (cached) error: No best alternative for libs/context/build/asm_sources next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>qcc not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>pe <threading>multi <toolset>msvc not matched next alternative: required properties: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>o32 <address-model>32 <architecture>mips1 <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>o32 <address-model>32 <architecture>mips1 <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>xcoff <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>xcoff <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>xcoff <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>xcoff <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>32_64 <architecture>power <binary-format>mach-o <threading>multi not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf <threading>multi <toolset>intel not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>clang not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>clang-win not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>intel not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>msvc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>intel not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>intel not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>clang not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>clang-win not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>intel not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>msvc not matched next alternative: required properties: <abi>x32 <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>x32 <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>x32 <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>intel not matched next alternative: required properties: <abi>sysv <address-model>32_64 <architecture>x86 <binary-format>mach-o <threading>multi not matched next alternative: required properties: <abi>sysv <architecture>combined <binary-format>mach-o <threading>multi not matched - C++11 mutex : no (cached) - Boost.Config Feature Check: cxx11_auto_declarations : no (cached) - Boost.Config Feature Check: cxx11_constexpr : no (cached) - Boost.Config Feature Check: cxx11_defaulted_functions : no (cached) - Boost.Config Feature Check: cxx11_final : no (cached) - Boost.Config Feature Check: cxx11_hdr_mutex : no (cached) - Boost.Config Feature Check: cxx11_hdr_regex : no (cached) - Boost.Config Feature Check: cxx11_hdr_tuple : no (cached) - Boost.Config Feature Check: cxx11_lambdas : no (cached) - Boost.Config Feature Check: cxx11_noexcept : no (cached) - Boost.Config Feature Check: cxx11_nullptr : no (cached) - Boost.Config Feature Check: cxx11_rvalue_references : no (cached) - Boost.Config Feature Check: cxx11_template_aliases : no (cached) - Boost.Config Feature Check: cxx11_thread_local : no (cached) - Boost.Config Feature Check: cxx11_variadic_templates : no (cached) - has_icu builds : no (cached) warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - zlib : no (cached) - bzip2 : no (cached) - lzma : no (cached) - iconv (libc) : no (cached) - iconv (separate) : no (cached) - icu : no (cached) - icu (lib64) : no (cached) - native-atomic-int32-supported : no (cached) - message-compiler : yes (cached) - native-syslog-supported : no (cached) - pthread-supports-robust-mutexes : no (cached) - compiler-supports-visibility : no (cached) - x86 : no (cached) - arm : no (cached) - mips1 : no (cached) - power : no (cached) - sparc : no (cached) - gcc visibility : no (cached) - long double support : no (cached) warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. - libbacktrace builds : no (cached) - addr2line builds : no (cached) - WinDbg builds : no (cached) - WinDbgCached builds : no (cached) Component configuration: - atomic : building - chrono : building - container : building - context : building - coroutine : building - date_time : building - exception : building - fiber : building - filesystem : building - graph : building - graph_parallel : building - iostreams : building - locale : building - log : building - math : building - mpi : building - program_options : building - python : building - random : building - regex : building - serialization : building - signals : building - stacktrace : building - system : building - test : building - thread : building - timer : building - type_erasure : building - wave : building ...patience... ...patience... ...patience... ...patience... ...patience... ...patience... ...found 16860 targets... ...updating 401 targets... compile-c-c++ bin.v2\libs\atomic\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi\lockpool.obj 'cl' is not recognized as an internal or external command, operable program or batch file. call "C:\Users\CHHENN~1\AppData\Local\Temp\b2_msvc_14.1_vcvarsx86_amd64_.cmd" >nul cl /Zm800 -nologo @"bin.v2\libs\atomic\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi\lockpool.obj.rsp" ...failed compile-c-c++ bin.v2\libs\atomic\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi\lockpool.obj... ...skipped <pbin.v2\libs\atomic\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi>libboost_atomic-vc141-mt-1_66.lib for lack of <pbin.v2\libs\atomic\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi>lockpool.obj... ...skipped <pstage\lib>libboost_atomic-vc141-mt-1_66.lib for lack of <pbin.v2\libs\atomic\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi>libboost_atomic-vc141-mt-1_66.lib... compile-c-c++ bin.v2\libs\system\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi\error_code.obj 'cl' is not recognized as an internal or external command, operable program or batch file. call "C:\Users\CHHENN~1\AppData\Local\Temp\b2_msvc_14.1_vcvarsx86_amd64_.cmd" >nul cl /Zm800 -nologo @"bin.v2\libs\system\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi\error_code.obj.rsp" ...failed compile-c-c++ bin.v2\libs\system\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi\error_code.obj... ...skipped <pbin.v2\libs\system\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi>libboost_system-vc141-mt-1_66.lib for lack of <pbin.v2\libs\system\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi>error_code.obj... ...skipped <pstage\lib>libboost_system-vc141-mt-1_66.lib for lack of <pbin.v2\libs\system\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi>libboost_system-vc141-mt-1_66.lib... compile-c-c++ bin.v2\libs\chrono\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi\chrono.obj 'cl' is not recognized as an internal or external command, operable program or batch file. [snip] Anyone any idea what is going on? Thanks, Christian

3 5

[process] Couple of issues
by Sebastian Messerschmidt 02 Jan '18

02 Jan '18

Hi, I'm using boost 1.64 on Windows7 with VisualStudio 2015 64bit. While testing boost.process I've encountered some issues that I'm not able to resolve: 1. Passing of multiple parameters: Consider this minimal example: <code> void test_sync() { try { bp::ipstream is; bp::child c(bp::search_path("ping"), "127.0.0.1 -t", bp::std_out > is); std::string line; while (c.running() && std::getline(is, line) && !line.empty()) { std::cerr << line << std::endl; } c.wait(); } catch (const std::exception& e) { std::cerr << "Error in execution: " << e.what(); } } </code> This doesn't correctly execute "ping 127.0.0.1 -t", instead it will act like "ping 127.0.0.1". I could not find an up2date example on how to pass parameters correctly. Any ideas? 2. No output on std::cout It seems that some applications don't output to std::cout/clog/cerr but somehow via printing to console directly (my guess as it is colored output on windows) In those instances, redirection fails. Can anyone think of a way to still monitor the output of the spawned child? Cheers Sebastian

2 3

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

30 Dec '17

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

2 4

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

28 Dec '17

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

2 1

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

28 Dec '17

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

2 1

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

23 Dec '17

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

1 0

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

20 Dec '17

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

2 2

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

19 Dec '17

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

1 0

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

19 Dec '17

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

2 1

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

19 Dec '17

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

1 0

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

19 Dec '17

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

7 12

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

15 Dec '17

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

2 1

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

15 Dec '17

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

1 0

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

15 Dec '17

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

1 0

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

15 Dec '17

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

3 2

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

15 Dec '17

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

2 1

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

14 Dec '17

The second release candidates for the 1.66.0 release are now available at: <https://dl.bintray.com/boostorg/prerelease/> The in progress release notes are: <http://www.boost.org/users/history/in_progress.html> Library documentation is available at: <http://www.boost.org/doc/libs/1_66_0/> The SHA256 checksums are as follows: 596389389c005814ecb2a6b64c31dccd2c3e6fbc5a802b4dfada999ae5844628 boost_1_66_0_rc2.7z 5721818253e6a0989583192f96782c4a98eb6204965316df9f5ad75819225ca9 boost_1_66_0_rc2.tar.bz2 bd0df411efd9a585e5a2212275f8762079fed8842264954675a4fddc46cfcf60 boost_1_66_0_rc2.tar.gz e1c55ebb00886c1a96528e4024be98a38b815115f62ecfe878fcf587ba715aad boost_1_66_0_rc2.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.

2 1

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

14 Dec '17

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

1 0

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

13 Dec '17

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

2 2

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

13 Dec '17

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

3 12

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

13 Dec '17

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

1 0

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

11 Dec '17

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

2 2

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

10 Dec '17

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

2 1

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

09 Dec '17

The release candidates for the 1.66.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.66.0/source/> The in progress release notes are: <http://www.boost.org/users/history/in_progress.html> Library documentation is available at: <http://www.boost.org/doc/libs/1_66_0/> The SHA256 checksums are as follows: c9d29486dd12f19d321da65eb5f0a157ec0f0edfd4701ade48c644310c8f0676 boost_1_66_0_rc1.7z 6232f7e7873b2d1f112fb62c726f7066e9a7e0643ed2aac7d31d20bf5749fbc0 boost_1_66_0_rc1.tar.bz2 30ad6d1c7380d6e6a87ce1bc54388ab957de67a2e8fa44dd3c106eafad0f6ac2 boost_1_66_0_rc1.tar.gz cd2c64f243c89e04329e94f3b803f0744171b44fee7a8b4e3256b3a625dcbd1c boost_1_66_0_rc1.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy.

2 2

Errors while trying to build boost::priority_queue
by Ram 09 Dec '17

09 Dec '17

Hi, When I try to build "priority_queue_example.cpp" it get these warnings(and so errors) pointing to "priority_queue_example.h" on the line where my priority_queue is declared. The warnings are, 1> priority_queue_example.cpp 1>c:\Projects\lib\boost\boost\heap\detail\stable_heap.hpp(102): error C2220: warning treated as error - no 'object' file generated 1>c:\Projects\lib\boost\boost\heap\detail\stable_heap.hpp(102): warning C4100: 'rhs' : unreferenced formal parameter 1> c:\Projects\lib\boost\boost\heap\detail\stable_heap.hpp(102) : while compiling class template member function 'boost::heap::detail::size_holder<false,size_t>::size_holder(const boost::heap::detail::size_holder<false,size_t> &)' 1> c:\Projects\lib\boost\boost\heap\detail\stable_heap.hpp(189) : see reference to function template instantiation 'boost::heap::detail::size_holder<false,size_t>::size_holder(const boost::heap::detail::size_holder<false,size_t> &)' being compiled 1> c:\Projects\lib\boost\boost\heap\detail\stable_heap.hpp(151) : see reference to class template instantiation 'boost::heap::detail::size_holder<false,size_t>' being compiled 1> c:\Projects\lib\boost\boost\heap\priority_queue.hpp(65) : see reference to class template instantiation 'boost::heap::detail::heap_base<T,myObjectPtrCompare,false,unsigned __int64,false>' being compiled 1> with 1> [ 1> T=myObject * 1> ] 1> c:\Projects\priority_queue_example.h(193) : see reference to class template instantiation 'boost::heap::priority_queue<myObject *,boost::heap::compare<myObjectPtrCompare>,boost::parameter::void_,boost::parameter::void_,boost::parameter::void_>' being compiledcompare<ObjectPtrCompare>,boost::parameter::void_,boost::parameter::void My priority_queue is declared as, mutable boost::heap::priority_queue<myObject*, boost::heap::compare<myObjectPtrCompare> > hp; Can you please help me fix this, I have been trying to for 2 days. Not sure what this means. This is my comparison class defined, struct myObjectPtrCompare { bool operator()(const myObject* lhs, const myObject* rhs) const { return (lhs->getProp() < rhs->getProp()); } }; Thanks!

2 2

boost::priority_queue help
by Ram 09 Dec '17

09 Dec '17

Created a boost::priority_queue with my comparison operation defined. Here is how my priority_queue looks, boost::heap::priority_queue<myObject*, boost::heap::compare<myObjectPtrCompare> > max_heap; My comparison is defined as, struct myObjectPtrCompare{ bool operator()(const myObject* lhs, const myObject* rhs) const { return (lhs->getTime() < rhs->getTime()); }}; I have used it as, myObject* obj1 = static_cast<myObject*>(base1); 'base1' is an object of class 'myBase'(base class of myObject) myObject and getTime() within it used for comparision are defined as, class myObject : public myBase { Time getTime() const { return time; }... ...} Compiling this gives me this error, c:\Projects\pq_test.cpp(27): error C2662: 'void boost::heap::priority_queue<myObject*,boost::heap::compare<myObjectPtrCompare>,boost::parameter::void_,boost::parameter::void_,boost::parameter::void_>::push(myObject *const &)' : cannot convert 'this' pointer from 'const boost::heap::priority_queue<myObject *,boost::heap::compare<myObjectPtrCompare>,boost::parameter::void_,boost::parameter::void_,boost::parameter::void_>' to 'boost::heap::priority_queue<myObject *,boost::heap::compare<myObjectPtrCompare>,boost::parameter::void_,boost::parameter::void_,boost::parameter::void_> &'1> Conversion loses qualifiers Using Visual Studio 2013 C++. I understand that I am doing something wrong with const correctness, but I am not able to figure out what is wrong. Any help is appreciated. TIA!

2 2

boost::priority_queue const correctness problem, help needed
by Ram 08 Dec '17

08 Dec '17

Created a boost::priority_queue with my comparison operation defined. Here is how my priority_queue looks, boost::heap::priority_queue<myObject*, boost::heap::compare<myObjectPtrCompare> > max_heap; boost::heap::priority_queue<myObject*, boost::heap::compare<myObjectPtrCompare> > max_heap; My comparison is defined as, struct myObjectPtrCompare { bool operator()(const myObject* lhs, const myObject* rhs) const { return (lhs->getTime() < rhs->getTime()); } }; I have used it as, myObject* obj1 = static_cast<myObject*>(base1); 'base1' is an object of class 'myBase'(base class of myObject) myObject and getTime() within it used for comparision are defined as, class myObject : public myBase { Time getTime() const { return time; } .... } Compiling this gives me this error, c:\Projects\pq_test.cpp(27): error C2662: 'void boost::heap::priority_queue<myObject*,boost::heap::compare<myObjectPtrCompare>,boost::parameter::void_,boost::parameter::void_,boost::parameter::void_>::push(myObject *const &)' : cannot convert 'this' pointer from 'const boost::heap::priority_queue<myObject *,boost::heap::compare<myObjectPtrCompare>,boost::parameter::void_,boost::parameter::void_,boost::parameter::void_>' to 'boost::heap::priority_queue<myObject *,boost::heap::compare<myObjectPtrCompare>,boost::parameter::void_,boost::parameter::void_,boost::parameter::void_> &' 1> Conversion loses qualifiers Using Visual Studio 2013 C++. I understand that I am doing something wrong with const correctness, but I am not able to figure out what is wrong. Any help is appreciated. TIA!

1 0

boost.test fails to zip custom datasets
by Georgios Sermaidis 08 Dec '17

08 Dec '17

I am trying to understand how to use datasets with the boost.test library. I am following the documentation here <http://www.boost.org/doc/libs/1_65_1/libs/test/doc/html/boost_test/tests_or…> and have created my dataset as follows: namespace bdata = boost::unit_test::data; struct test_set { class iterator { int m_a; public: iterator() : m_a(0){} void operator++() { ++m_a; } int operator*() const { return m_a; } }; using sample = int; enum {arity = 1}; auto begin() const { return iterator{}; } bdata::size_t size() const { return 5; // let's assume only 5 numbers } }; namespace boost { namespace unit_test { namespace data { namespace monomorphic { template <> struct is_dataset<test_set> : std::true_type{}; }}}} which is very simple and iterates numbers from 0 to 4. The following simple test compiles and runs just fine: // this works as expected and prints 0, 1, 2, 3, 4 BOOST_DATA_TEST_CASE( example_test1, test_set(), my_datum) { std::cout << my_datum << std::endl; } However, when I try to zip <http://www.boost.org/doc/libs/1_65_1/libs/test/doc/html/boost_test/tests_or…> two such datasets it fails to compile (Apple LLVM version 9.0.0 (clang-900.0.38)): // error: invalid operands to binary expression ('typename data::result_of::make<test_set>::type' (aka 'test_set') and 'test_set') test_set() ^ test_set(), // ~~~~~~~~~~~^~~~~~~~~~~~~ BOOST_DATA_TEST_CASE( example_test2, test_set() ^ test_set(), my_datum1, my_datum2) { std::cout << my_datum1 << " " << my_datum2 << std::endl; } Is what I am trying to do legal? If so, what is the correct way to achieve it? Thank you for your help! Live code here <https://wandbox.org/permlink/6CI286mynvVCjQdW>

2 2

Easy install doesn't
by Jean-Louis Leroy 07 Dec '17

07 Dec '17

I downloaded the current version of boost from here: http://www.boost.org/users/download/ (the Unix tgz) Then I religiously followed these instructions: http://www.boost.org/doc/libs/1_61_0/more/getting_started/unix-variants.htm… It didn't install much of anything useful...just stuff in /usr/local/share/boost-build, apparently the build system. No headers were installed, no libs were built or installed... I tried to install from debian packages and that failed miserably too but that's another story... Help please?

3 2

[iostreams] file_descriptor doesn't retry on EINTR
by David Roberts 30 Nov '17

30 Nov '17

Hi, I have found that the file_descriptor class in Boost.Iostreams does not retry on EINTR. The relevant code is in libs/iostreams/src/file_descriptor.cpp. A bug was raised for this 7 years ago: https://svn.boost.org/trac10/ticket/4913 <https://svn.boost.org/trac10/ticket/4913> There is a patch attached to that bug that makes the file_descriptor_impl::read method retry on EINTR. If something like this were implemented then something similar should also be done to retry in the file_descriptor_impl::write method. I could have a go at submitting a PR to make both the read and write methods retry if interrupted. But before I do this, is there any other history I should be aware of, like a good reason why EINTR is not currently handled? Many thanks, David

2 1

boost::asio::buffer bug with string literal
by Martijn Otto 29 Nov '17

29 Nov '17

When using boost::asio::buffer with a string literal the terminating null character is included in the buffer size, leading to bugs like accidentally sending out a null character. We could fix this by adding something like this to buffer.hpp: /// Create a new non-modifiable buffer that represents the given character array. /** * @returns A const_buffer value equivalent to: * @code const_buffer( * static_cast<const void*>(data), * (N - 1) * sizeof(char)); @endcode */ template <std::size_t N> inline BOOST_ASIO_CONST_BUFFER buffer( const char (&data)[N]) BOOST_ASIO_NOEXCEPT { return BOOST_ASIO_CONST_BUFFER(data, (N - 1) * sizeof(char)); } But this might cause trouble when using a const char array that is not null-terminated, since we then basically drop the last character. Would this be the best approach?

3 6

[Spirit.Qi] failing to parse IP address octets
by Michael Powell 27 Nov '17

27 Nov '17

Hello, I've got the following parsers which are failing to find the correct attributes. I tried to parse in terms of uint_parser<uint8_t, 10, 1, 3>() at first, but this was not working properly. So I tried the following: _octet_rule = lexeme[ char_('0') | (char_('1') >> -(digit >> -digit)) | (char_('2') >> -((char_('0', '4') >> -(digit)) | (char_('5') >> -(char_('0', '5'))) | char_('6', '9') ) ) | (char_('3', '9') >> -digit) ]; Which is presently failing to find all three digits in the "20\d"-"24\d" use case. Octet itself parses correctly when I use this rule: _octet_rule >> !(char_); My octet test cases verify the entire range of 0-255 successfully, as well as the following invalid cases: VerifyOctet(-1, invalid_); VerifyOctet(1990, invalid_); VerifyOctet(2550, invalid_); VerifyOctet("255.", invalid_); VerifyOctet(256, invalid_); VerifyOctet(999, invalid_); VerifyOctet("abc", invalid_); VerifyOctet(123.456, invalid_); Converted to corresponding string, i.e. "1990" or "123.456". But when I combine that into the IP address rule, the test results occur: _octet_rule >> repeat(3)[char_('.') >> _octet_rule]; And the test results: CHECK_THAT( y, Equals(x) ) with expansion: "145.23.183.47" equals: "145.231.183.47" with message: Verifying address >>> 145.231.183.47 <<< FAILED: CHECK_THAT( y, Equals(x) ) with expansion: "189.21.29.11" equals: "189.211.29.11" with message: Verifying address >>> 189.211.29.11 <<< FAILED: CHECK_THAT( y, Equals(x) ) with expansion: "90.60.32.24" equals: "90.60.32.246" with message: Verifying address >>> 90.60.32.246 <<< FAILED: CHECK_THAT( y, Equals(x) ) with expansion: "22.59.144.140" equals: "223.59.144.140" with message: Verifying address >>> 223.59.144.140 <<< IP address test data is randomly generated, or combinatorially if I wanted to wait for all 4.3B or so test cases. However, I figure that as long as the Octet rule is working, it is reasonable to expect the Address rule may also work. Not sure why those last digits are being dropped, however. Or how the 1's can succeed where the 2's are failing. Any suggestions, Spirit folks? Thanks! Cheers, Michael Powell

1 3

[serialization] property_tree::ptree bpta back-end, json, forward (upward) compatibility
by Sergey Spiridonov 27 Nov '17

27 Nov '17

Hi Current binary, text and xml archive back-ends allow to implement backward compatibility. This means that it is possible to read old serialization files with the new version of the serialization code, with the help of the version of the class which is stored in archive itself. Unfortunately forward compatibility is not possible to implement with the existing archive backends. Suppose we have class A with one field. struct A { template<class Archive> inline void serialize(Archive & ar, const unsigned int version ) { ar & BOOST_SERIALIZATION_NVP(field); } int field; }; Later we want to add a new field2. To be able to load the previously created file we need can use versioning. struct A { template<class Archive> inline void serialize(Archive & ar, const unsigned int version ) { ar & BOOST_SERIALIZATION_NVP(field); if(version > 0) { ar & BOOST_SERIALIZATION_NVP(field2); } } int field; int field2; }; BOOST_CLASS_VERSION(A, 1) But if we want the opposite, to load the old class from the file which was created from the new class (for example, if we use serialization to communicate between new and old version of application on the network), existing backends will fail. Why? The reason is that they expect certain field in certain order and do not allow unexpected unknown fields. Although with text and binary backend it is difficult to do, because field names are not stored, but xml backend has names for every field, so it can simply skip unknown fields. Unfortunately this is not implemented. I created [1] simple experimental archive which allows forward(upward) compatibility. It stores data in boost::property_tree::ptree (instead of std::stream), which, in turn, can be saved to json, if necessary. If the file which is loaded, has additional unknown fields (from future version), they will be ignored. [1] https://github.com/sena73/ptree_archive Intermediate storage of data in ptree has its advantages and disadvantages. Of course, this slows down things and requires more memory. On other hand, it allows to get upward compatibility automatically easily and even to process data before (or without) loading it into the target class. Also we get json and info storage for free. With little modification xml backend from property_tree can be used. Sure, it must be possible to create a version of boost::archive::xml which will be also capable to keep upward compatibility without necessity to load things into the property_tree first. Binary and text archives must be extended with field names to allow field skipping. -- Best regards, Sergey Spiridonov

1 1

[release] Boost 1.66.0 Beta 1
by Daniel James 24 Nov '17

24 Nov '17

Boost release 1.66.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.66.0.beta.1/source/> The SHA256 checksums are as follows: e7b23e638e8c3a9da1512439385b04850829cea7bd56d8398677c096857d830b boost_1_66_0_b1.7z 5d0405eb73bd609ebcd54bbc96d4f1e2d97c51b96c4703706695ddd94f942d6b boost_1_66_0_b1.tar.bz2 f0f455e39bc47b2b670a17cb221687506e9a22dc478956d3d8aabb9cb835a7dc boost_1_66_0_b1.tar.gz 694c8b9e902b7981670bce166f675f3875c19326936db51aabd98d2ddfea9b45 boost_1_66_0_b1.zip For details of what's in the release, see <http://www.boost.org/users/history/version_1_66_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

3 4

how to build boost binary libraries for GCC in windows 10
by Renfan Luo 23 Nov '17

23 Nov '17

Hi All As VS supports OpenMP2.0 only, I have to use GCC instead for my project with parallelisation in coding. I have downloaded Cygwin and installed the GCC 6.4.0 then updated it to the latest version 5.5.0 on my windows 10. All those binary libraries I built up in VS 2017, I guess, cannot be usable for GCC, so it may be necessary to rebuild them for boost 1.65.1 for GCC. Could you guys show me how to build them? Cheers Renfan

2 4

function template argument deduction with std::tuple
by Ireneusz Szcześniak 23 Nov '17

23 Nov '17

Hi, I have a problem related to function template argument deduction with std::tuple (with boost::tuple too). I attach a file with the complete source you can compile. Below I describe the code. I have a template function declaration: > template <typename T> > auto > get_cost(const T &); Then I define my template types: > template <typename Graph> > using Vertex = typename Graph::vertex_descriptor; > > template <typename Graph> > using Label = std::tuple<Vertex<Graph>>; I define the specialization of the get_cost function for the Label type: > template <typename Graph> > auto > get_cost(const Label<Graph> &l) > { > return std::get<0>(l); > } I can define alright a variable of type Label: > struct graph > { > using vertex_descriptor = unsigned; > }; > > Label<graph> l; But I cannot use the templated function: > get_cost(l); I get this error: > error: use of 'auto get_cost(const T&) [with T = > std::tuple<unsigned int>]' before deduction of 'auto' I got this error with GCC HEAD 8.0.0 20171113 and Clang HEAD 6.0.0 (I used wandbox.org) Some other type definitions and their specializations of the get_cost function compile. For a struct derived from the std::tuple: > template <typename Graph> > struct Label1: std::tuple<Vertex<Graph>> > { > }; > > template <typename Graph> > auto > get_cost(const Label1<Graph> &l) > { > return std::get<0>(l); > } For a member of type std::tuple: > template <typename Graph> > struct Label2 > { > std::tuple<Vertex<Graph>> t; > }; > > template <typename Graph> > auto > get_cost(const Label2<Graph> &l) > { > return std::get<0>(l.t); > } For a member of type Vertex<Graph>: > template <typename Graph> > struct Label3 > { > Vertex<Graph> m_v; > }; > > template <typename Graph> > auto > get_cost(const Label3<Graph> &l) > { > return l.m_v; > } I would like to use the Label type, i.e., because it has the constructor and operators already defined, which I need. I would appreciate it if someone could explain what is going wrong here. Best, Irek

2 6

Building b2 --prefix include directory not quite
by Michael Powell 22 Nov '17

22 Nov '17

Hello, So the B2 help indicates that the include directory should be whatever "<prefix>/include" is. So, I'm setting my prefix accordingly, something like, "/path/to/installed/boost-1.65.1", however, the include directory ends up being something a little more like this: "/path/to/installed/boost-1.65.1/include/boost-1_65_1". This looks like a bug to me. Can I set the --includedir myself and correct this during my build? Thank you... Cheers, Michael Powell

1 0

[Interprocess] Waiting thread termination causes deadlock
by Markus Bonk 22 Nov '17

22 Nov '17

Hi, I am having issues with boost::interprocess::ipcdetail::spin_condition::do_wait_timed deadlocking. The issue occurs when a thread that is waiting due to a call to interprocess_condition_any::wait() terminates unexpectedly and interprocess_condition_any::notify_all() is called (from any process). The cause of the deadlock is not that the terminating thread held a lock – it doesn’t because it is waiting, but that spin_condition::m_num_waiters is never decremented to zero because one of the threads is no longer waiting and so the enter mutex is not freed. I have tried BOOST_INTERPROCESS_ENABLE_TIMEOUT_WHEN_LOCKING, however as far as I can see this only tells me that the deadlock is there. Are there any suggestions how I can recover from spin_condition not freeing the enter mutex? Or perhaps some way of avoiding the issue? Markus ________________________________ Markus Bonk Senior Software Engineer [cid:image19ab5c.GIF@24a568cc.448b8dc0] 3Dconnexion GmbH Clarita-Bernhard-Str. 18 81249 München Germany Tel: +49 (89) 897 45 42 - 70 Fax: +49 (89) 897 45 42 - 50 markus_bonk(a)3dconnexion.com<mailto:markus_bonk@3dconnexion.com> www.3dconnexion.com<http://www.3dconnexion.com> Geschäftsführer: Antonio Pascucci Sitz der Gesellschaft: München Registergericht: München HRB 99232

1 0

Adding Lzma support to b2 invocation
by Michael Powell 22 Nov '17

22 Nov '17

Hello, So I've got LZMA downloading, have the include in hand, as well as what I presume are either object files and/or a DLL. Just need to know how to integrate that with my B2 invocation. Something like: -sLZMA_INCLUDE="/path/to/lzma/include" ? And then, how to include the object file with the linkage, or the DLL(s). And necessarily in which architecture/address-model. Otherwise, I am getting close to building. Around the corner from that is Locale support from ICU (?), which I've got downloading as well ATM. Cheers, Michael Powell

1 0

Re: [Boost-users] Building boost b2 lzma options
by Michael Powell 21 Nov '17

21 Nov '17

Next errors seem to be lzma related. Is this along the same lines as with Zlib and bzip2? To avoid confusion, this is 1.65.1, as well; not the announced 1.66. Thanks! On Mon, Nov 20, 2017 at 1:41 PM, Nelson, Erik - 2 via Boost-users <boost-users(a)lists.boost.org> wrote: > Michael Powell Sent: Monday, November 20, 2017 1:24 PM >> >> I am building Boost and making progress. Thus far wondering what >> >> options to provide my B2. I added the zlib include path to the >> >> include="...;/path/to/zlib;...", and now seems to be wanting the LIB >> >> path? > > I use > > "-sBZIP2_SOURCE=/path/to/bzip2/src" "-sZLIB_SOURCE=/path/to/zlib/src" > > And it adds the source to the build. > > ---------------------------------------------------------------------- > This message, and any attachments, is for the intended recipient(s) only, may contain information that is privileged, confidential and/or proprietary and subject to important terms and conditions available at http://www.bankofamerica.com/emaildisclaimer. If you are not the intended recipient, please delete this message. > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > https://lists.boost.org/mailman/listinfo.cgi/boost-users

3 5

Building boost b2 zlib options
by Michael Powell 20 Nov '17

20 Nov '17

Hello, I am building Boost and making progress. Thus far wondering what options to provide my B2. I added the zlib include path to the include="...;/path/to/zlib;...", and now seems to be wanting the LIB path? LINK : fatal error LNK1181: cannot open input file 'z.lib' LINK : fatal error LNK1181: cannot open input file 'zlib.lib' LINK : fatal error LNK1181: cannot open input file 'zll.lib' LINK : fatal error LNK1181: cannot open input file 'zdll.lib' Which option is that for B2? After that, it is on to finding bzip? fatal error C1083: Cannot open include file: 'bzlib.h': No such file or directory Is there a source download similar to that of zlib? I think I'm pretty close but for a handful of obscurish third party dependencies. Thanks! Cheers, Michael Powell

4 9

Could guys help on OpenMP odeint 'for' statement error
by Renfan Luo 20 Nov '17

20 Nov '17

Hi All I have just started an OpenMP application example in VS2017 platform (/* Boost libs/numeric/odeint/examples/openmp/lorenz_ensemble_simple.cpp). When switch on Properties->C/C++->Language->Open MP Support-> Yes (/openmp), it has a build error Severity Code Description Project File Line Suppression State Error C3016 'i': index variable in OpenMP 'for' statement must have signed integral type OpenMP-test1 c:\users\renfanluo\source\repos\openmp-test1\openmp-test1\openmptest1.cpp 35 If When switch off Properties->C/C++->Language->Open MP Support-> Yes (/openmp) to No (/openmp), then the error goes off. However, "No" means OpenMP is switched off, which is not what I want. It is understood that in the for statement, the variables can be assigned with data type before, the errors associated with these user defined for statement will go off but the similar error shown below remain the same for boost header files. Severity Code Description Project File Line Suppression State Error C3016 'i': index variable in OpenMP 'for' statement must have signed integral type Test-OpenMP2 C:\boost_1_65_1\boost\numeric\odeint\external\openmp\openmp_range_algebra.hpp 72 Could you guys have any ideas of how to fix this problem? Best regards Renfan

1 0

[python::numpy] Access Violation when initializing numpy
by Christian Henning 18 Nov '17

18 Nov '17

Hi all, On Windows 10 with Visual Studio 2017 I', trying to run the following code in x64 debug configuration: #include <iostream> #include <boost/python.hpp> #include <boost/python/numpy.hpp> namespace p = boost::python; namespace np = boost::python::numpy; int main() { Py_Initialize(); np::initialize(); p::tuple shape = p::make_tuple(3, 3); np::dtype dtype = np::dtype::get_builtin<float>(); np::ndarray a = np::zeros(shape, dtype); return 0; } In the line np::initialize(); I'm getting a Exception thrown at 0x0000000066E43B15 (python36.dll) in test.exe: 0xC0000005: Access violation reading location 0x0000000000000025. occurred Inside boost::python::numpy::intialize() the exception is thrown when trying to execute the line: PyObject *numpy = PyImport_ImportModule("numpy.core.multiarray"); Does anyone know why that would happen or how to debug the issue further? I have installed all packages via pip and executed the python code as described in https://www.scipy.org/getting-started.html. Thanks ahead! Christian

1 1

[python] Linker error when initializing numpy
by Christian Henning 18 Nov '17

18 Nov '17

Hi all, I have the latest boost from the master branch and built everything including python. I can see that two python related libs were built: libboost_python3-vc141-mt-gd-x64-1_66.lib libboost_numpy3-vc141-mt-gd-x64-1_66.lib For compiling python I use vcpkg and it's generating python3_d.lib for debug and python3.lib for release. The cpp code I like to compile is: #include <iostream> #include <boost/python.hpp> #include <boost/python/numpy.hpp> namespace p = boost::python; namespace np = boost::python::numpy; int main() { Py_Initialize(); np::initialize(); return 0; } A few issues: 1) linker is looking for "boost_python3-vc141-mt-gd-x64-1_66.lib" but I got "libboost_python3-vc141-mt-gd-x64-1_66.lib" Please tell me how to fix that. For now I just copied the libboost* files and renamed them. 2) Linker error: "__declspec(dllimport) void __cdecl boost::python::numpy::initialize(bool)" How can I resolve that? Thanks, Christian

4 6

Conan-center package.
by Philippe Groarke 17 Nov '17

17 Nov '17

Are there any plans to release an official Boost package on Conan-Center? If not, any specific reason? It would really help Windows builds and facilitate enterprise adoption. Thank you & good day.

1 0

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

16 Nov '17

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

3 4

Could guys help me on a boost MPI link error
by Renfan Luo 16 Nov '17

16 Nov '17

Hi All I have built boost binary library on my PC workstation in windows 10 using VS 2017 for boost 1.65.1 successfully for application of MPI in my project. I had a simple test for MPI which worked perfectly. So I moved to a further test using boost example "odeint-v2/examples/mpi/phase_chain.cpp", which is applied to solve ODE with MPI capacity. When I tried to build the project, it gives me an error Severity Code Description Project File Line Suppression State Error LNK1112 module machine type 'x86' conflicts with target machine type 'x64' MPI-test2 C:\Users\renfanluo\source\repos\MPI-test2\MPI-test2\libboost_mpi-vc141-mt-1_65_1.lib(environment.obj) 1 I googled, then I went to properties->Linker->Advanced->Target Machine, changed to "MachineX86 (/MACHINE:X86)", then rebuild the project, now the error changes to Severity Code Description Project File Line Suppression State Error LNK1112 module machine type 'x64' conflicts with target machine type 'x86' MPI-test2 C:\Users\renfanluo\source\repos\MPI-test2\MPI-test2\x64\Release\MPItest2.obj 1 So this shows that simply changing the target machine setting in VS will not work. Could you guys give me some indications of how to fix this problem. Best regards Renfan

2 1

Boost.Chrono custom I/O
by Leo Cacciari 15 Nov '17

15 Nov '17

Hi, I'm using boost.chrono in a project and I need some non-standard input-output. First of all, I need to print days as days. Consider the following code namespace testing { typedef boost::chrono::duration<long double,boost::ratio<86400>> day; } int main(int argc,char *argv[]) { using namespace testing; day d(10.5); std::cout << "Value: " << d << std::endl; } This prints Value: 10.5 [86400/1]seconds Which is obviously right; but I'd rather have: Value 10.5 days Obviously, a solution is to define operator<<(ostream&,const & day), however I'd rather use the facet approach, which looks like easier to extend to parsing and more flexible (e.g. allowing to print the above value as "10.5 days" somewhere and as "10.5 d" elsewhere.) If I understand the documentation, I must define a subclass of boost::chrono::duration_units and then imbue the facet into the stream. Is this right? Where can I found some guidelines on how to do that? Thanks for the help lc -- Leo Cacciari Aliae nationes servitutem pati possunt. Populi Romani est propria libertas.

1 0

[Beast] Problems in getting started with Beast
by Sharklaser Lasershark 14 Nov '17

14 Nov '17

Hello! I'm migrating a project from libcurl to Beast. I'm trying to compile http_client_async.cpp <https://github.com/boostorg/beast/blob/develop/example/http/client/async/ht…>, but 110 errors come from "file_win32.ipp" and "file_win32.hpp", mostly missing declarations and members. I'm using Visual Studio 2017 (warning level 4). Here is what I have done: 1. Downloaded and set up boost 1.65.1 according to the "getting started" tutorial <http://www.boost.org/doc/libs/1_65_1/more/getting_started/windows.html> - Built all binaries - Verified header only example and binary-dependent example 2. Downloaded beast/include/boost <https://github.com/boostorg/beast/tree/develop/include/boost> from GitHub and moved the folder and .hpp to - C:\Program Files\boost\boost_1_65_1\boost 3. Started an empty project and pasted in the http_client_async.cpp <https://github.com/boostorg/beast/blob/develop/example/http/client/async/ht…> example. I have spent too many days trying to get this up and running. Any help would be greatly appreciated! Kind regards

2 1

help on how to build mpi library
by Renfan Luo 14 Nov '17

14 Nov '17

I am a new user of boost and have downloaded 1.65.1 and unzipped it to my C:\local\boost_1_65_1. Then chose the "MPI nearest neighbour coupled phase chain." Example, file "phase_chain.cpp" as my first test in VS2015, I have got a link error message "Error LNK1104 cannot open file 'libboost_mpi-vc141-mt-1_65_1.lib" . I have checked the boost root directory and sub-directories and did not this library file. Hope guys can suggest how I build mpi library and install it to windows.

3 3

Customized installation
by mahmood n 11 Nov '17

11 Nov '17

Hi, It is possible to build one or two targets instead of all? When I run ../b2 install --prefix=/somewhere It build all libraries. Assume I only want filesystem. Is that possible or they all depend on each other? Regards, Mahmood

2 1

error categories point to invalid data with boost log and asio
by priv＠mariusherzog.net 11 Nov '17

11 Nov '17

I have the following problem while using boost asio together with boost log and clang 3.9.0. When I want to print an error code for example passed to me by a asio completion handler, my program crashes. This is because the error category points to invalid data. If I put a breakpoint in get_misc_error category which is called upon program startup, the local static error category already contains junk data. When I compile with gcc 5.4.0 this error does not occur. Also if I do not link against boost log everything works fine as well. I use linux, and link all boost libraries dynamically. Boost version is 1.62.0. Would it help if I maybe link boost log statically? Is there anything else I can do?

1 0

[signals2] Connect to overloaded slots
by Florian Lindner 10 Nov '17

10 Nov '17

Hello, this code compiles just fine: #include <boost/signals2.hpp> #include <iostream> // void slot() { std::cout << "No args slot called." << std::endl; } void slot(int i) { std::cout << "Int " << i << " arg slot called." << std::endl; } int main(int argc, char **argv) { boost::signals2::signal<void(int)> s; s.connect(&slot); return 0; } However, when I uncomment the slot() function, it does not do so, anymore: boostsignals.cpp:78:5: error: no matching member function for call to 'connect' s.connect(&slot); ~~^~~~~~~ /usr/include/boost/signals2/detail/signal_template.hpp:689:18: note: candidate function not viable: no overload of 'slot' matching 'const boost::signals2::signal<void (int), boost::signals2::optional_last_value<void>, int, std::less<int>, boost::function<void (int)>, boost::function<void (const boost::signals2::connection &, int)>, boost::signals2::mutex>::slot_type' (aka 'const slot<void (int), boost::function<void (int)> >') for 1st argument connection connect(const slot_type &slot, connect_position position = at_back) ^ /usr/include/boost/signals2/detail/signal_template.hpp:693:18: note: candidate function not viable: requires at least 2 arguments, but 1 was provided connection connect(const group_type &group, ^ Is there a way to make it working with overloaded slot functions? Thanks, Florian

2 1

(no subject)
by giridhar 08 Nov '17

08 Nov '17

Hi Boost http://bit.ly/2hcH687 giridhar

1 0

Warning "declares a non-template function"
by mahmood n 06 Nov '17

06 Nov '17

Hi, A program needs boost > 1.58. So, I used boost-1.60 with gcc-4.8. However, as I compile the program, I get many warnings similar to /home/mahmood/boost_1_60_0/boost/mpl/set/aux_/item.hpp(47): warning: "char (&operator||(const boost::mpl::s_item<T, Base> &, boost::mpl::aux::type_wrapper<T> *))[boost::mpl::next<Base::order>::type::value]" declares a non-template function -- add <> to refer to a template instance /home/mahmood/boost_1_60_0/boost/mpl/set/aux_/item.hpp(48): warning: "boost::mpl::aux::no_tag operator%(const boost::mpl::s_item<T, Base> &, boost::mpl::aux::type_wrapper<T> *)" declares a non-template function -- add <> to refer to a template instance Lines are BOOST_MPL_AUX_SET_OVERLOAD( order_tag_, ORDER_BY_KEY, s_item, aux::type_wrapper<T>* ); BOOST_MPL_AUX_SET_OVERLOAD( aux::no_tag, IS_MASKED, s_item, aux::type_wrapper<T>* ); Does that mean I have to change that to aux::type_wrapper< >* ? Regards, Mahmood

2 1

Under ubuntu, How to purge default boost-v1.58 then switch to the built version without any damages?
by Alex Luya 06 Nov '17

06 Nov '17

Under ubuntu 16,04 I have*built latest boost 1.65**.1 like this*: |./bootstrap.sh --prefix=/usr/local ./b2 sudo ./b2 install sudo ldconfig ***then when building something against boost,I got the**se errors:* /usr/local/include/boost/serialization/access.hpp: In instantiation of ‘static void boost::serialization::access::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive; T = std::array<std::__cxx11::basic_string<char>, 10ul>]’: /usr/local/include/boost/serialization/serialization.hpp:68:22: required from ‘void boost::serialization::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive; T = std::array<std::__cxx11::basic_string<char>, 10ul>]’ /usr/local/include/boost/serialization/serialization.hpp:126:14: required from ‘void boost::serialization::serialize_adl(Archive&, T&, unsigned int) [with Archive = boost::archive::text_oarchive; T = std::array<std::__cxx11::basic_string<char>, 10ul>]’ /usr/local/include/boost/archive/detail/oserializer.hpp:150:40: required from ‘void boost::archive::detail::oserializer<Archive, T>::save_object_data(boost::archive::detail::basic_oarchive&, const void*) const [with Archive = boost::archive::text_oarchive; T = std::array<std::__cxx11::basic_string<char>, 10ul>]’ /usr/local/include/boost/archive/detail/oserializer.hpp:103:1: required from ‘class boost::archive::detail::oserializer<boost::archive::text_oarchive, std::array<std::__cxx11::basic_string<char>, 10ul> >’ /usr/local/include/boost/archive/detail/oserializer.hpp:255:13: required from ‘static void boost::archive::detail::save_non_pointer_type<Archive>::save_standard::invoke(Archive&, const T&) [with T = std::array<std::__cxx11::basic_string<char>, 10ul>; Archive = boost::archive::text_oarchive]’ /usr/local/include/boost/archive/detail/oserializer.hpp:310:22: required from ‘static void boost::archive::detail::save_non_pointer_type<Archive>::invoke(Archive&, const T&) [with T = std::array<std::__cxx11::basic_string<char>, 10ul>; Archive = boost::archive::text_oarchive]’ /usr/local/include/boost/archive/detail/oserializer.hpp:534:18: required from ‘void boost::archive::save(Archive&, T&) [with Archive = boost::archive::text_oarchive; T = const std::array<std::__cxx11::basic_string<char>, 10ul>]’ /usr/local/include/boost/archive/detail/common_oarchive.hpp:70:22: required from ‘void boost::archive::detail::common_oarchive<Archive>::save_override(T&) [with T = const std::array<std::__cxx11::basic_string<char>, 10ul>; Archive = boost::archive::text_oarchive]’ /usr/local/include/boost/archive/basic_text_oarchive.hpp:83:9: required from ‘void boost::archive::basic_text_oarchive<Archive>::save_override(T&) [with T = const std::array<std::__cxx11::basic_string<char>, 10ul>; Archive = boost::archive::text_oarchive]’ /usr/local/include/boost/archive/detail/interface_oarchive.hpp:70:9: required from ‘Archive& boost::archive::detail::interface_oarchive<Archive>::operator<<(const T&) [with T = std::array<std::__cxx11::basic_string<char>, 10ul>; Archive = boost::archive::text_oarchive]’ examples/user_code/openpose_recognition.cpp:867:89: required from here /usr/local/include/boost/serialization/access.hpp:116:9: error: ‘struct std::array<std::__cxx11::basic_string<char>, 10ul>’ has no member named ‘serialize’ t.serialize(ar, file_version); ^ compilation terminated due to -Wfatal-errors. Makefile:478: die Regel für Ziel „.build_release/examples/user_code/openpose_recognition.o“ scheiterte make: *** [.build_release/examples/user_code/openpose_recognition.o] Fehler 1 make: *** Auf noch nicht beendete Prozesse wird gewartet … | |*I think ubuntu is still use default boost that installed by apt-get,so I tried to pur**ge it * sudo apt-get purge libboost1.58-dev| *the output asks me to remove a lot of stuffs **that depend on libboost1.58-dev **like these:* Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt: docutils-common fltk1.3-doc fluid gazebo7 gazebo7-common gazebo7-plugin-base gir1.2-gtk-2.0 libapr1 libapr1-dev libaprutil1 libaprutil1-dev libarmadillo6 libassimp-dev libassimp3v5 libboost-atomic1.58.0 libboost-chrono1.58.0 libboost-context1.58.0 libboost-coroutine1.58.0 libboost-graph-parallel1.58.0 libboost-graph1.58.0 libboost-locale1.58.0 libboost-log1.58.0 libboost-math1.58.0 libboost-mpi-python1.58.0 libboost-mpi1.58.0 libboost-python1.58.0 libboost-random1.58.0 libboost-regex1.58.0 libboost-signals1.58.0 libboost-test1.58.0 libboost-thread1.58.0 libboost-timer1.58.0 libboost-tools-dev libboost-wave1.58.0 libboost1.58-tools-dev libbullet-dev libbulletcollision2.83.6 libbulletdynamics2.83.6 libbulletsoftbody2.83.6 libbz2-dev libcollada-dom2.4-dp-dev libcollada-dom2.4-dp0 libconsole-bridge-dev libconsole-bridge0.2v5 libcurl4-openssl-dev libdap-dev libdap17v5 libdapclient6v5 libdapserver7v5 libepsilon1 libflann-dev libflann1.8 libfltk-cairo1.3 libfltk-forms1.3 libfltk-images1.3 libfltk1.3-dev libfreeimage-dev libfreeimage3 libfreexl1 libgazebo7 libgdal-dev libgdal1i libgeos-3.5.0 libgeos-c1v5 libgeos-dev libgl2ps-dev libgtest-dev libgtk2.0-dev libgts-0.7-5 libgts-bin libgts-dev libhdf4-0-alt libhdf4-alt-dev libhdf5-mpi-dev libignition-math2 libignition-math2-dev libinput-dev libjs-jquery-ui libjsoncpp-dev libjxr0 libkmlbase1 libkmldom1 libkmlengine1 libldap2-dev liblinearmath2.83.6 liblog4cxx-dev liblog4cxx10-dev liblog4cxx10v5 liblz4-dev libminizip1 libnetcdf-c++4 libnetcdf-cxx-legacy-dev libnetcdf-dev libnetcdf11 libogdi3.2 libogre-1.9.0v5 libopenni-dev libopenni-sensor-pointclouds0 libopenni0 ....... ,and it may cause a lot of damage if continuing,so the question is |*How to purge default boost-v1.58 then switch to the built version without any damages?*|

3 2

[asio] Does ssl::stream allow multiple pending async operations?
by Phil Sean 06 Nov '17

06 Nov '17

The documentation for ssl::stream says: "Shared objects: Unsafe. The application must also ensure that all asynchronous operations are performed within the same implicit or explicit strand." Does this mean we have to wait for an async operation to finish before another is started (for read/read, read/write, and write/write)? (Async operations refer to async_read_some() and async_write_some(), not the composed operations.) If so, is the operation said to have finished when the handler is invoked or when the handler returns? That is: void handler( const boost::system::error_code& error, std::size_t bytes_transferred ) { // Does the operation finish here ... } // or here? If not, what's the difference between the async operations of ip::tcp::socket and ssl::stream then (as strand just avoids concurrency for the thread-unsafe)? I came across different views on this problem. This answer[1] suggests that simply using the same strand (ie. no concurrency) will suffice. Another one[2] says multiple pending asynchronous operations can be problematic for ssl::stream even if no concurrency occurs. Thanks. [1] https://stackoverflow.com/questions/27212123/executing-asynchronous-operati… [2] https://stackoverflow.com/questions/15352472/using-boosts-ssl-asio-code-asy…

4 5

Spirit: how to force backtracking
by Stian Zeljko Vrba 04 Nov '17

04 Nov '17

I have the following grammar rule: value = (int_ % ',') | *ascii::print; The intention is to parse either a comma-separated list of integers or a string. The rule as such fails in cases like "123ABC", which should be parsed as string. >From the description of the | operator, I would expect the parser to backtrack and try the other alternative when it sees that the first alternative does not match the input. However, I get a parse error instead (this rule is a part of a larger grammar), I guess because the first alternative matches the single integer but the rest of the grammar cannot be matched. How to rewrite the grammar to resolve this ambiguity, or force spirit to backtrack if the first alternative of 'value' cannot be matched?

3 3

[locale] how to read a local date from an istream?
by Frédéric 02 Nov '17

02 Nov '17

Hi, With boost::locale we can output a localized date: double d=...; std::cout<<boost::locale::as::date<<d; but how can I read a date from a string? std::cin>>boost::locale::as::date>>d; does not work. It stops reading at the first "/". For example, this small program #include <iostream> #include <sstream> #include <boost/locale/formatting.hpp> #include <boost/locale/generator.hpp> int main(int argc, char **argv) { boost::locale::generator gen; gen.categories(); auto loc = gen(""); double date = 5.; // default value to see if it changes std::istringstream iss("2/11/2017"); // November 1st, 2017 in French iss.imbue(loc); iss >> boost::locale::as::date >> boost::locale::as::local_time >> date; std::cout.imbue(loc); std::cout << "as_posix: " << boost::locale::as::posix << date << "\n" << "as_date: " << boost::locale::as::date << date << "\n"; return 0; } outputs as_posix: 2 as_date: 01/01/1970 instead of as_posix: 1509617233 (may be different) as_date: 02/11/2017 F

1 0

Re: [Boost-users] Many undefined references for libboost_filesystem
by mahmood n 01 Nov '17

01 Nov '17

I used another gcc version 4.5 (Ubuntu 11.04) and it works without any problem! I don’t know what is wrong with gcc-4.6. Though the problematic platform was Kubuntuu 12.04. I am know trying with Ubuntu 12.04 which uses gcc-4.6 to see if it is really a gcc problem or the platform! Sent from Mail for Windows 10 From: Alex Perry Sent: Wednesday, October 18, 2017 4:45 PM To: mahmood n Subject: RE: [Boost-users] Many undefined references for libboost_filesystem Actually one other thought (though you may well have solved this by now). Are you sure that the boost libraries you are attempting to link to are using the same abi? Ie how were they built. I only glanced at the github stuff you pointed too but I think I remember that the last commit was 5 years ago or some such – so probably wasn’t using C++11. I note you are using an old (54) version of boost whilst the current is (65) so about 5 years ago as well – but that probably supported being built with c++11.so you might need to rebuild them if they were using a different version of the C++ standard (or any abi breaking change such as 32 vs 64 bit, static runtime vs dynamically loaded etc). Under windows boost normally encodes the abi into the library name and you just automagically (using a msvc extension) link to the appropriate one. That is not the normal way on linux since gcc doesn’t have autolinking so you normally end up sticking them into a separate lib directory and swapping the -L path depending on which abi you want Again though please note this is not boost specific – is just standard C / C++ / Fortran or any obj/link based language issues with building dependencies – (and why most have swapped to using cmake rather than vanilla make to avoid the pain). A. From: Alex Perry Sent: 17 October 2017 16:14 To: 'mahmood n' <nt_mahmood(a)yahoo.com> Subject: RE: [Boost-users] Many undefined references for libboost_filesystem Dropped the rest of the boost list since I’m sure not many are interested! > I didn’t want to have another pain for “finding how the verbose variable is set in the Makefile”!!! Not hard that one… just add it to the command line when you call make make verbose=1 ….. > The libraries do exist, so why on earth it can not link :( > mahmood@vb:AES$ g++ -fPIC -L/home/mahmood/boost_1_54_0/stage/lib -lboost_filesystem -lboost_system -m64 -o /home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/bin/release/AES obj/x86_64/release/aescuda.cpp.o obj/x86_64/release/aesCudaUtils.cpp.o obj/x86_64/release/aesHost.cu.o -L/usr/local/cuda/lib64 -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../lib -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../common/lib/linux -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../../shared//lib -lcudart -L/usr/local/cuda/lib64 -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../lib -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../common/lib/linux -L/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src//../../shared//lib -lcudart -lcutil_x86_64 -lshrutil_x86_64 …. Nope the computer is telling you they don’t exist on those paths as given – unfortunately the computer is more likely to be correct than you on this! You have a lot of library paths being set there – possibly you have multiple versions of boost libraries so its finding the wrong one first so you have a version conflict Possibly the simplest way is create a noddy test and play with the command line till you work out what the problem is http://rextester.com/live/JDVHT54458 That will give you similar compile errors without -lboost_filesystem -lboost_system added to the compile line. Obviously that is using clang rather than gcc which you are using but the syntax and principles are pretty much the same between any c++ compiler HTH A.

5 6

Boost graph library algorithms - is it possible to use previous solutions to "warm start" a new related problem
by F1E2D3 F1E2D3 29 Oct '17

29 Oct '17

Hello, I am primarily an Operations Researcher, and prior to boost, was writing my own C++ code for specific network flow problems. I am now hoping to transition to boost::graph completely for my network flow problem solution needs. However, I have one major concern. In linear programming (I use CPLEX https://www.ibm.com/us-en/marketplace/ibm-ilog-cplex as my primary linear programming (LP) solver), once a problem is solved, say a Dijkstra's shortest path problem, the solver maintains the optimal basis. Then, if some problem parameter changes, the linear program need not be solved from scratch, but the current basis is first tested for optimality for the new problem as well. An example of this would be an increase in the cost of an arc that does not feature on the optimal path from source to destination in a shortest path problem. This increase in cost does not change the optimal path, and hence, it would be wasteful to solve this problem again from scratch. Does boost::graph have this capability that LP solvers have? I posted this question first on stack overflow and am posting it here now. The question was not completely answered there. A working code and small example are provided there. I am giving the link below. https://stackoverflow.com/questions/46986312/are-boostgraph-algorithms-capa… Any help will be appreciated. Thanks.

1 0

[review][DoubleEnded] Review Results
by Thorsten Ottosen 27 Oct '17

27 Oct '17

Dear users and members of Boost, I'm happy to to announce that Benedek Thaler's Boost.DoubleEnded is /conditionally/ accepted into Boost provided that it can be integrated smoothly with Boost.Container. There are several other conditions, some major and some minor which I will outline below. For now, I would like to thank everyone that participated with reviews and comments. We didn't have that many reviews, but the reviewers did spend a lot of time both on review and the following discussions. Special thanks also goes to Benedek for his hard work. It is not too often that a GSOC code ends with something of this quality. Two of the world's expert C++ container developers used phrases like "solid" and "everything looks clean and beautiful" about the implementation, "tests look very good, corner cases and all", "The reference section is very good". Congratulations, Benedek. ============== A path forward ============== Ion has most kindly accepted the idea of merging the library into Boost.Container. This consists of A. taking selected elements from batch_deque and adding them to boost::container::deque. B. putting devector into boost.container after changes have been applied to code and documentation C. back-porting the devector code to C++03 (C) does not need to happen immediately, that is, we can have a release where devector is available in a C++11 version. Ion has also most kindly agreed to help with this process. I will help write a new introduction that focuses on the main principles of devector. We also have a number of benchmarks which we can gather and use for a small section of on that topic. I'll leave it to you and Ion to work out the details. ========================== Detailed comments devector ========================== Apart from the merging with Boost.Container, the most heard complaint was about the "fat", the non-essential parts if the interface, that could be removed. This includes -- Remove the direct support for small buffer optimization form devector. When the time comes, provide small_devector similar to the way we have vector/small_vector (there is no requirement that small_devector is provided). -- remove all of the following: - all constructors that uses reserve_only_tag, - all constructors that uses unsafe_uninitialized_tag, - void unsafe_uninitialized_resize_front(size_type); - void unsafe_uninitialized_resize_back(size_type); - unsafe_push_front(...); - unsafe_push_back(...); -- add instead - constructors that uses default_init_t like boost.container - resize versions that uses default_init_t - T& unchecked_emplace_back(...) noexcept(...) - T& unchecked_emplace_front(...) noexcept(...) At some point, I hope we can upgrade default_init_t to mean no construction for all trivially copyable types. There was a wish for more symmetry in devector and so functions that break symmetry or can appear ambiguous should be removed. This means we should remove: -- capacity() There is no need for front_capacity() and back_capacity(). We could remove reserve(), but then we can't use devector with a flat_set. Reserve() should not be an alias for reserve_back() though, but controlled by the policy. We could remove resize(), but even deque has it where it means resize_back(). I totally agree it would be ideal to remove all of reserve(),resize(),capacity(),clear(), but I see no easy way we can use devector with flat containers if we remove the first and the last. Unless we start deprecating stuff in boost::deque/boost::vector and provide new consistent alternatives, we will never get a 100% satisfactory solution. At the end of the day, we need to be pragmatic, so if deprecation is not on the table, this seems the best we can do. Since we don't want two allocations implied by calling reserve_back() and reserve_front(), you can add a mechanism for doing that. That is, you can provide -- reserve( new_capacity ); -- reserve_front( new_front_capacity ) -- reserve_back( new_back_capacity ) -- reserve( new_front_capacity, new_back_capacity ) or, since reserve() is such a weird beast, simply provide -- reserve( new_capacity ); // for flat containers -- anticipate_front( new_front_elements ) -- anticipate_back( new_back_elements ) -- anticipate( new_front_elements, new_back_elements ) to get rid of the funky -- container.reserve_front( container.size() + new_front_elements ) dance. There were suggestions for shrink_back/front_to_fit, but since we are trying to remove fat, I suggest that we wait for a use-case. There were also suggestions that clear() should be amended. As the growth (or resizing policy) mandates what clear does, we need a way to escape. The minimal change that allows that is to provide -- clear( front_free_capacity ) which gives full power to the user. You may provide clear_back() as clear(0) and clear_front() as clear(c.size()+c.front_free_capacity()+c.back_free_capacity()). Ideally, clear() would have been removed entirely like capacity()/resize(), but like reserve(), it just seems like impossible when we start using it with flat containers. Other minor comments: - drop strong exception safety guarantees and do it like boost.container - prefer to make iterator a type (should be easy with reuse from boost::container::vector - allocator should not be inherted from - make clear O(1) amortized gurantees depend on growth policy - consider calling growth policy for resizing policy - make sure SFINAE works properly with constructors - make the default growth factor 2 (as we heard from Sean Parent: no factor below 2 is empirically good) - consider renaming front_free_capacity to free_front_capacity. Rationale: "front_capacity" is a concept, noun, and "free" is the adjective. Ditto for back_free_capacity. - remove size_type from growth policy and take it from the allocator - make the allocator template argument the 2nd argument - fix remaning TODO in code - documentation should not sell devector as drop-in replacement for vector, but rather stress it is not - the allocator supports needs to be improved. I guess doing it the Boost.Container way ensures that (ask Daniel James for help) - exception-safety issues pointed out by Ion - postconditions of insert/erase needs to specify behavior to front_free_capacity/back_free_capcity - use of local containers should be avoided - rotate should be avoided - delegate range move operations to those defined in Boost.Container - make sure all functions excepting non-overlapping range uses memcpy (not just memmove). This includes: - range constructor - copy-constructor - copy-assignment - range-assignment - range insert - destructor should used std::has_trivial_destructor to avoid loop in that case to make sure all compilers optimize it away (similar for erase). There is one final puzzle and that is the growth policy. I hope we can finalize that by testing Joaquin's and Ion's suggestions over the coming weeks. ============================= Detailed comments batch_deque ============================= For deque, the comments were similar, although there was far less to discuss than for devector. All agreed that one should be able to control the segment size. - stable_insert was not needed. - segment iteration was good, but should be usable with range-based for loop. The segment iterator should return a segment type if possible, and the segment should have begin(),end(),size() members. - since boost::deque already has a resize with default_init_t, that should be sufficient to provide fast serialization load for trivial types. No need for - resize_front - resize_back - unsafe_uninitialized_resize_front - unsafe_uninitialized_resize_back - reserve - shrink_to_fit() - capacity() The following are still needed for optimal code (or code that can be known not to reallocate, or for better locality in deserialization, avoiding double initialization) - free_front_capacity; - free_back_capacity; - reserve_front - reserve_back - unchecked_emplace_front - unchecked_emplace_back Boost.Container's unit-tests should be extended with those from batch_deque where it makes sense. Since segmented iteration was somewhat faster, it should be use internally where it makes sense. In particular - copy-constructor - copy-assignment - destructor As for devector, all constructor/functions that iterate over non-overlapping ranges should use memcpy. destructor should use is_trivially_destructible to ensure it is optimized away (similar for erase). ====================== Serialization comments ====================== I suggest that the default versions just do what Boost.Serialization does, perhaps just replacing resize with resize with default_init_t. That ensures it works correctly for all archive types. It also needs to use make_nvp() so the output is identical to std::vector. We will then talk to Robert about how we can take advantage of the binary archive in a correct fashion. ====================== kind regards Thorsten, review manager

3 3

[Container] Does deque allocate memory in default constructor?
by dariomt＠gmail.com 25 Oct '17

25 Oct '17

It seems std::deque implementations are allowed to allocate in the default constructor [1] However, boost::container::deque I think does not allocate in the default constructor, but the docs are not explicit about it. I can see in the docs: *Throws*: If allocator_type's default constructor throws. Which would mean that it cannot throw due to memory exhaustion, so it cannot allocate memory. Is my reasoning right? If yes, would it be possible to make this explicit in the docs? I think it is relevant, because it might be the deciding factor for switching from std::deque to boost::container::deque (as it might be my case). Thanks! [1] https://stackoverflow.com/questions/40203494/why-does-stddeque-allocate-mem…

2 1

Fwd: Boost compilation problems
by Berkus Karchebnyy 24 Oct '17

24 Oct '17

Hello, in attempt to build boost for android with more or less reasonable strict settings (-Werror) I uncovered some bugs which I cannot report on github because these projects have Issues disabled. I will post them here in hopes they will eventually reach appropriate maintainers. == ONE: boost.containers == clang-darwin.compile.c android-build/boost/bin.v2/ libs/container/build/clang-darwin-5.0~x86/debug/address- model-32/link-static/target-os-android/threading-multi/alloc_lib.o In file included from libs/container/src/alloc_lib.c:19: libs/container/src/dlmalloc_ext_2_8_6.c:1097:8: error: variable 'ret' is used uninitialized whenever 'if' condition is false [-Werror,-Wsometimes- uninitialized] if (!PREACTION(m)) { ^~~~~~~~~~~~~ libs/container/src/dlmalloc_ext_2_8_6.c:1125:11: note: uninitialized use occurs here return ret; ^~~ libs/container/src/dlmalloc_ext_2_8_6.c:1097:4: note: remove the 'if' if its condition is always true if (!PREACTION(m)) { ^~~~~~~~~~~~~~~~~~~ libs/container/src/dlmalloc_ext_2_8_6.c:1095:4: note: variable 'ret' is declared here boost_cont_malloc_stats_t ret; ^ 1 error generated. "/usr/local/opt/android-ndk/android-ndk-r16-beta1// toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++" "-DBOOST_AC_USE_PTHREADS" "-DBOOST_SP_USE_PTHREADS" "-fvisibility=hidden" "-fvisibility-inlines-hidden" "-Wno-unused-local-typedef" -x c -O0 -g -O0 -fno-inline -Wall -g --target=i686-none-linux-android --gcc-toolchain=/usr/local/opt/android-ndk/android-ndk- r16-beta1//toolchains/x86-4.9/prebuilt/darwin-x86_64 --sysroot=/usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sources/cxx-stl/llvm-libc++/include -isystem /usr/local/opt/android-ndk/ android-ndk-r16-beta1//sources/cxx-stl/llvm-libc++abi/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sources/android/support/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot/usr/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sysroot/usr/include/i686-linux-android -DANDROID -D__ANDROID_API__=21 -ffunction-sections -funwind-tables -fstack-protector-strong -fno-limit-debug-info -fPIC -no-canonical-prefixes -mstackrealign -Wa,--noexecstack -Wformat -Werror=format-security -Wall -Werror -Wshadow -march=i686 -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTAINER_STATIC_LINK=1 -D_LITTLE_ENDIAN -I"." -c -o "android-build/boost/bin.v2/ libs/container/build/clang-darwin-5.0~x86/debug/address- model-32/link-static/target-os-android/threading-multi/alloc_lib.o" "libs/container/src/alloc_lib.c" == TWO: boost.serialization and monty python == (cue Benny Hill music) clang-darwin.compile.c++ android-build/boost/bin.v2/ libs/serialization/build/clang-darwin-5.0~x86/debug/ address-model-32/link-static/target-os-android/threading- multi/polymorphic_iarchive.o In file included from libs/serialization/src/polymorphic_iarchive.cpp:20: In file included from ./boost/archive/polymorphic_iarchive.hpp:32: ./boost/archive/detail/iserializer.hpp:69:7: error: macro expansion producing 'defined' has undefined behavior [-Werror,-Wexpansion-to-defined] #if ! DONT_USE_HAS_NEW_OPERATOR ^ ./boost/archive/detail/iserializer.hpp:63:12: note: expanded from macro 'DONT_USE_HAS_NEW_OPERATOR' || defined(__SUNPRO_CC) && (__SUNPRO_CC < 0x590) \ ^ ./boost/archive/detail/iserializer.hpp:212:9: error: macro expansion producing 'defined' has undefined behavior [-Werror,-Wexpansion-to-defined] #if DONT_USE_HAS_NEW_OPERATOR ^ ./boost/archive/detail/iserializer.hpp:63:12: note: expanded from macro 'DONT_USE_HAS_NEW_OPERATOR' || defined(__SUNPRO_CC) && (__SUNPRO_CC < 0x590) \ ^ 2 errors generated. "/usr/local/opt/android-ndk/android-ndk-r16-beta1// toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++" "-DBOOST_AC_USE_PTHREADS" "-DBOOST_SP_USE_PTHREADS" "-fvisibility=hidden" "-fvisibility-inlines-hidden" "-Wno-unused-local-typedef" -x c++ -ftemplate-depth-255 -fvisibility=hidden -fvisibility-inlines-hidden -std=c++14 -O0 -g -O0 -fno-inline -Wall -g --target=i686-none-linux-android --gcc-toolchain=/usr/local/opt/android-ndk/android-ndk- r16-beta1//toolchains/x86-4.9/prebuilt/darwin-x86_64 --sysroot=/usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sources/cxx-stl/llvm-libc++/include -isystem /usr/local/opt/android-ndk/ android-ndk-r16-beta1//sources/cxx-stl/llvm-libc++abi/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sources/android/support/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot/usr/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sysroot/usr/include/i686-linux-android -DANDROID -D__ANDROID_API__=21 -ffunction-sections -funwind-tables -fstack-protector-strong -fno-limit-debug-info -fPIC -no-canonical-prefixes -mstackrealign -Wa,--noexecstack -Wformat -Werror=format-security -Wall -Werror -Wshadow -march=i686 -DBOOST_ALL_NO_LIB=1 -D_LITTLE_ENDIAN -I"." -c -o "android-build/boost/bin.v2/libs/serialization/build/ clang-darwin-5.0~x86/debug/address-model-32/link-static/ target-os-android/threading-multi/polymorphic_iarchive.o" "libs/serialization/src/polymorphic_iarchive.cpp" == THREE: boost.program_options == clang-darwin.compile.c++ android-build/boost/bin.v2/ libs/program_options/build/clang-darwin-5.0~x86/debug/ address-model-32/link-stati c/target-os-android/threading-multi/cmdline.o libs/program_options/src/cmdline.cpp:104:41: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror ,-Wshadow] cmdline::init(const vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:508:48: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror ,-Wshadow] cmdline::parse_long_option(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:545:49: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror,-Wshadow] cmdline::parse_short_option(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:611:47: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror,-Wshadow] cmdline::parse_dos_option(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:632:58: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror,-Wshadow] cmdline::parse_disguised_long_option(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:663:47: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror,-Wshadow] cmdline::parse_terminator(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ libs/program_options/src/cmdline.cpp:683:55: error: declaration shadows a field of 'boost::program_options::detail::cmdline' [-Werror,-Wshadow] cmdline::handle_additional_parser(vector<string>& args) ^ ./boost/program_options/detail/cmdline.hpp:139:34: note: previous declaration is here std::vector<std::string> args; ^ 7 errors generated. "/usr/local/opt/android-ndk/android-ndk-r16-beta1// toolchains/llvm/prebuilt/darwin-x86_64/bin/clang++" "-DBOOST_AC_USE_PTHREADS" "-DBOOST_SP_USE_PTHREADS" "-fvisibility=hidden" "-fvisibility-inlines-hidden" "-Wno-unused-local-typedef" -x c++ -std=c++14 -O0 -g -O0 -fno-inline -Wall -g --target=i686-none-linux-android --gcc-toolchain=/usr/local/opt/android-ndk/android-ndk- r16-beta1//toolchains/x86-4.9/prebuilt/darwin-x86_64 --sysroot=/usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sources/cxx-stl/llvm-libc++/include -isystem /usr/local/opt/android-ndk/ android-ndk-r16-beta1//sources/cxx-stl/llvm-libc++abi/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sources/android/support/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1//sysroot/usr/include -isystem /usr/local/opt/android-ndk/android-ndk-r16-beta1// sysroot/usr/include/i686-linux-android -DANDROID -D__ANDROID_API__=21 -ffunction-sections -funwind-tables -fstack-protector-strong -fno-limit-debug-info -fPIC -no-canonical-prefixes -mstackrealign -Wa,--noexecstack -Wformat -Werror=format-security -Wall -Werror -Wshadow -march=i686 -DBOOST_ALL_NO_LIB=1 -D_LITTLE_ENDIAN -I"." -c -o "android-build/boost/bin.v2/libs/program_options/build/ clang-darwin-5.0~x86/debug/address-model-32/link-static/ target-os-android/threading-multi/cmdline.o" "libs/program_options/src/ cmdline.cpp" The entire set of compile flags and NDK version can be seen in the provided snippets. Thanks. -- Sr. Software Engineer [image: twilio] <http://www.twilio.com/?utm_source=email_signature> EMAIL berkus(a)twilio.com

1 0

Help needed in learning to use Boost.Asio
by Osman Zakir 24 Oct '17

24 Oct '17

I want to learn how to use Boost.Asio so I can then create an abstraction layer over it for HTTP and create a server and client. I need it for a web app I want to make. I know C++ isn’t a good choice for this sort of thing, but it’s still growing and getting better, so I wonder if there’s really no hope for it becoming a better choice for web development. Especially if someone were to propose a networking library for boost that also provides support for the HTTP protocol and maybe also RESTful services out of the box. Libraries in Boost have a high chance of making it into the standard, after all, so this could be a good idea. I’ve heard from many people that C++ is a waste of time, especially if one wants to get into web development and make a lot of money. Most people who want to web development are abandoning C++ in favor of languages Python that provide better support for web development. I don’t like this and I hope that C++ will also become better for the job soon so that it can pull back programmers that have left it for other languages. That’s also the reason why I want to use C++ here. I’m hoping that the Networking TS would be standardized and that the standardizing committee would also do something to make C++ overall better for the web, preferably as good as Python if possible. The difficulty of getting into and using C++ is also overly-exaggerated but it seems to be more because of C++ programmers not making their code simple and beautiful enough, so it’s also the language users’ fault. I want to try to change the negative views that people have of C++, as well. By the way, would it be a good idea to send an email asking about the future of C++, especially for web development, to Dr. Stroustrup if I can find a way to contact him? I know he’s a busy man and I’m also reluctant to this, but since he’s also on the standard-making committee, if he finds some free time to reply to my email, he should be able to tell me what to expect about C++ and its future. I’m sorry if this email got too long, though. Best regards. Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

5 7

boost asio
by Sharma, Nishant 23 Oct '17

23 Oct '17

Hi, I have created an Asynchronous TCP server and client and it works fine. Since it is asynchronous, it uses API's like async_read, async_write etc.. Is it possible that the same code be used to do "synchronous" communication which results in blocking any further task in the queue unless the current i/o task is complete ? I have attached the example hereby. It has two folder for server and client.. First the server needs to be run and then the client. Best Regards, Nishant Sharma

3 5

boost fileystem issue
by Olivier Tristan 20 Oct '17

20 Oct '17

Hi Guys, I would like to bump this particular issue that is quite annoying for me. Basically it crashes as soon as you call boost::filesystem::exists in the ctor of a static variable initialized at program startup https://svn.boost.org/trac10/ticket/12987 Looks like there was a fix 4 month ago but this hasn't been pushed into the trunk yet Any idea how to push the process forward ? Thanks ! -- Olivier Tristan Research & Development www.uvi.net

2 2

Reconnecting a SSL socket correctly
by David Demelier 18 Oct '17

18 Oct '17

Hello, I'm trying to reconnect a SSL socket (using ssl::stream with tcp::socket) that has been closed only remotely. It looks like a shutdown on my client causes "stream truncated" error so I have no idea how can I connect my client socket again. I was thinking of just creating a new instance but the stream class is not copyable. Do you have any recommandations? Regards, -- David

2 1

[asio] null reference in epoll_reactor
by Phil Sean 18 Oct '17

18 Oct '17

Hi, Running the tutorial async TCP server (http://www.boost.org/doc/libs/1_65_1/doc/html/boost_asio/tutorial/tutdaytim…) or any other asynchronous operation in valgrind yields an error like this: = Syscall param epoll_pwait(sigmask) points to unaddressable byte(s) = epoll_pwait (in /usr/lib/libc-2.26.so) = boost::asio::detail::epoll_reactor::run(bool, boost::asio::detail::op_queue<boost::asio::detail::task_io_service_operation>&) (in /.../server) = boost::asio::detail::task_io_service::do_run_one(boost::asio::detail::scoped_lock<boost::asio::detail::posix_mutex>&, boost::asio::detail::task_io_service_thread_info&, boost::system::error_code const&) (in /.../server) = boost::asio::detail::task_io_service::run(boost::system::error_code&) (in /.../server) = boost::asio::io_service::run() (in /.../server) = main (in /.../server) = Address 0x0 is not stack'd, malloc'd or (recently) free'd I suspect it's due to some recent changes because it didn't use to be an error. Boost version is 1.65.1(Arch Linux). Thank you.

2 2

git clone of boost
by Tim Burgess 18 Oct '17

18 Oct '17

Hi, Just been trying to find the address to clone boost, but was unsuccessful. Can anybody help me out please? Best wishes. Tim Burgess

2 1

Re: [Boost-users] Many undefined references for libboost_filesystem
by Mahmood N 17 Oct '17

17 Oct '17

Hi Daniel, I tried some other versions based on the release date of the project and boosts. I tried 1.38 and 40 and 42 and 44 and 46. All of them return some undefined references. How can i find which boost version is used in the project? Regards, Mahmood -------------------------------------------- On Sat, 10/14/17, Daniel Anderson <wonixen(a)gmail.com> wrote: Subject: Re: [Boost-users] Many undefined references for libboost_filesystem To: boost-users(a)lists.boost.org Cc: "Mahmood N" <nt_mahmood(a)yahoo.com> Date: Saturday, October 14, 2017, 12:53 AM you are probably using the wrong version of filesystem, or maybe of boost. often those projects need a specific boost version. 2017-10-13 14:24 GMT-04:00 Mahmood N via Boost-users <boost-users(a)lists.boost.org>: > Hi, > > I am trying to build a suite as described at > https://github.com/gpgpu-sim/ispass2009-benchmarks > > Some of the benchmarks use boost. For example, AES/Makefile has > > > > LINKFLAGS := -L$(BOOST_LIB) -lboost_filesystem > > > > Also, the Makefile.ispass-2009 in the root folder has the following settings > > > > SETENV=export BINDIR=$(BINDIR); \ > > export ROOTDIR=$(NVIDIA_COMPUTE_SDK_LOCATION)/C/src/; \ > > export BINSUBDIR=$(BINSUBDIR); \ > > export BOOST_LIB=/home/mahmood/boost_1_46_0/lib; \ > > export BOOST_ROOT=/home/mahmood/boost_1_46_0/include; \ > > export BOOST_VER=""; \ > > export OPENMPI_BINDIR=/usr/bin/; > > > > > > I manually built boost_1_46_0 with the steps described at > http://www.boost.org/doc/libs/1_46_1/doc/html/bbv2/installation.html > > The installations was successful and I can see lib/ and include/ folders > > > > mahmood@vb:boost_1_46_0$ find lib -name libboost_system* > > lib/libboost_system.so.1.46.0 > > lib/libboost_system.so > > lib/libboost_system.a > > mahmood@vb:boost_1_46_0$ find lib -name libboost_filesystem* > > lib/libboost_filesystem.so > > lib/libboost_filesystem.a > > lib/libboost_filesystem.so.1.46.0 > > > > > > > > However, as I run “make -f Makefile.ispass-2009”, I get many undefined > errors about libboost_filesystem. Please see below > > > > > > > > export > BINDIR=/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/bin/; > export ROOTDIR=/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src/; export > BINSUBDIR=release; export BOOST_LIB=/home/mahmood/boost_1_46_0/lib; export > BOOST_ROOT=/home/mahmood/boost_1_46_0/include; export BOOST_VER=""; export > OPENMPI_BINDIR=/usr/bin/; make noinline=0 -C AES > > make[1]: Entering directory > `/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/AES' > > obj/x86_64/release/aesCudaUtils.cpp.o: In function > `readFromFileForm(boost::filesystem3::path&, std::vector<unsigned int, > std::allocator<unsigned int> >&)': > > aesCudaUtils.cpp:(.text+0x97d): undefined reference to > `boost::filesystem3::detail::status(boost::filesystem3::path const&, > boost::system::error_code*)' > > obj/x86_64/release/aesCudaUtils.cpp.o: In function > `readFromFileNotForm(boost::filesystem3::path&, char*, unsigned int)': > > aesCudaUtils.cpp:(.text+0xe81): undefined reference to > `boost::filesystem3::detail::status(boost::filesystem3::path const&, > boost::system::error_code*)' > > obj/x86_64/release/aesCudaUtils.cpp.o: In function > `getFileSize(boost::filesystem3::path&)': > > aesCudaUtils.cpp:(.text+0x1244): undefined reference to > `boost::filesystem3::detail::status(boost::filesystem3::path const&, > boost::system::error_code*)' > > aesCudaUtils.cpp:(.text+0x1257): undefined reference to > `boost::filesystem3::detail::file_size(boost::filesystem3::path const&, > boost::system::error_code*)' > > obj/x86_64/release/aesCudaUtils.cpp.o: In function > `initAesCuda(std::basic_string<char, std::char_traits<char>, > std::allocator<char> >, unsigned char*, unsigned int, > std::basic_string<char, std::char_traits<char>, std::allocator<char> >, > char*, unsigned int)': > > aesCudaUtils.cpp:(.text+0x1c54): undefined reference to > `boost::filesystem3::path::wchar_t_codecvt_facet()' > > aesCudaUtils.cpp:(.text+0x1cab): undefined reference to > `boost::filesystem3::path::wchar_t_codecvt_facet()' > > aesCudaUtils.cpp:(.text+0x1ce5): undefined reference to > `boost::filesystem3::detail::status(boost::filesystem3::path const&, > boost::system::error_code*)' > > aesCudaUtils.cpp:(.text+0x1d02): undefined reference to > `boost::filesystem3::detail::status(boost::filesystem3::path const&, > boost::system::error_code*)' > > obj/x86_64/release/aesCudaUtils.cpp.o: In function > `_GLOBAL__sub_I_aesCudaUtils.cpp': > > aesCudaUtils.cpp:(.text.startup+0x2b): undefined reference to > `boost::system::generic_category()' > > aesCudaUtils.cpp:(.text.startup+0x37): undefined reference to > `boost::system::generic_category()' > > aesCudaUtils.cpp:(.text.startup+0x43): undefined reference to > `boost::system::system_category()' > > obj/x86_64/release/aescuda.cpp.o: In function `_GLOBAL__sub_I_aescuda.cpp': > > aescuda.cpp:(.text.startup+0x68b): undefined reference to > `boost::system::generic_category()' > > aescuda.cpp:(.text.startup+0x697): undefined reference to > `boost::system::generic_category()' > > aescuda.cpp:(.text.startup+0x6a3): undefined reference to > `boost::system::system_category()' > > collect2: ld returned 1 exit status > > make[1]: *** > [/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/bin//release/AES] > Error 1 > > make[1]: Leaving directory > `/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/AES' > > make: *** [default] Error 2 > > > > > > > > Any thought on that? > > > Regards, > Mahmood > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > https://lists.boost.org/mailman/listinfo.cgi/boost-users -- Daniel L'action accède à la perfection quand, bien que vivant, vous êtes déjà mort Bunan

6 14

Many undefined references for libboost_filesystem
by Mahmood N 13 Oct '17

13 Oct '17

Hi, I am trying to build a suite as described at https://github.com/gpgpu-sim/ispass2009-benchmarks Some of the benchmarks use boost. For example, AES/Makefile has LINKFLAGS := -L$(BOOST_LIB) -lboost_filesystem Also, the Makefile.ispass-2009 in the root folder has the following settings SETENV=export BINDIR=$(BINDIR); \ export ROOTDIR=$(NVIDIA_COMPUTE_SDK_LOCATION)/C/src/; \ export BINSUBDIR=$(BINSUBDIR); \ export BOOST_LIB=/home/mahmood/boost_1_46_0/lib; \ export BOOST_ROOT=/home/mahmood/boost_1_46_0/include; \ export BOOST_VER=""; \ export OPENMPI_BINDIR=/usr/bin/; I manually built boost_1_46_0 with the steps described at http://www.boost.org/doc/libs/1_46_1/doc/html/bbv2/installation.html The installations was successful and I can see lib/ and include/ folders mahmood@vb:boost_1_46_0$ find lib -name libboost_system* lib/libboost_system.so.1.46.0 lib/libboost_system.so lib/libboost_system.a mahmood@vb:boost_1_46_0$ find lib -name libboost_filesystem* lib/libboost_filesystem.so lib/libboost_filesystem.a lib/libboost_filesystem.so.1.46.0 However, as I run “make -f Makefile.ispass-2009”, I get many undefined errors about libboost_filesystem. Please see below export BINDIR=/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/bin/; export ROOTDIR=/home/mahmood/NVIDIA_GPU_Computing_SDK/C/src/; export BINSUBDIR=release; export BOOST_LIB=/home/mahmood/boost_1_46_0/lib; export BOOST_ROOT=/home/mahmood/boost_1_46_0/include; export BOOST_VER=""; export OPENMPI_BINDIR=/usr/bin/; make noinline=0 -C AES make[1]: Entering directory `/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/AES' obj/x86_64/release/aesCudaUtils.cpp.o: In function `readFromFileForm(boost::filesystem3::path&, std::vector<unsigned int, std::allocator<unsigned int> >&)': aesCudaUtils.cpp:(.text+0x97d): undefined reference to `boost::filesystem3::detail::status(boost::filesystem3::path const&, boost::system::error_code*)' obj/x86_64/release/aesCudaUtils.cpp.o: In function `readFromFileNotForm(boost::filesystem3::path&, char*, unsigned int)': aesCudaUtils.cpp:(.text+0xe81): undefined reference to `boost::filesystem3::detail::status(boost::filesystem3::path const&, boost::system::error_code*)' obj/x86_64/release/aesCudaUtils.cpp.o: In function `getFileSize(boost::filesystem3::path&)': aesCudaUtils.cpp:(.text+0x1244): undefined reference to `boost::filesystem3::detail::status(boost::filesystem3::path const&, boost::system::error_code*)' aesCudaUtils.cpp:(.text+0x1257): undefined reference to `boost::filesystem3::detail::file_size(boost::filesystem3::path const&, boost::system::error_code*)' obj/x86_64/release/aesCudaUtils.cpp.o: In function `initAesCuda(std::basic_string<char, std::char_traits<char>, std::allocator<char> >, unsigned char*, unsigned int, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, char*, unsigned int)': aesCudaUtils.cpp:(.text+0x1c54): undefined reference to `boost::filesystem3::path::wchar_t_codecvt_facet()' aesCudaUtils.cpp:(.text+0x1cab): undefined reference to `boost::filesystem3::path::wchar_t_codecvt_facet()' aesCudaUtils.cpp:(.text+0x1ce5): undefined reference to `boost::filesystem3::detail::status(boost::filesystem3::path const&, boost::system::error_code*)' aesCudaUtils.cpp:(.text+0x1d02): undefined reference to `boost::filesystem3::detail::status(boost::filesystem3::path const&, boost::system::error_code*)' obj/x86_64/release/aesCudaUtils.cpp.o: In function `_GLOBAL__sub_I_aesCudaUtils.cpp': aesCudaUtils.cpp:(.text.startup+0x2b): undefined reference to `boost::system::generic_category()' aesCudaUtils.cpp:(.text.startup+0x37): undefined reference to `boost::system::generic_category()' aesCudaUtils.cpp:(.text.startup+0x43): undefined reference to `boost::system::system_category()' obj/x86_64/release/aescuda.cpp.o: In function `_GLOBAL__sub_I_aescuda.cpp': aescuda.cpp:(.text.startup+0x68b): undefined reference to `boost::system::generic_category()' aescuda.cpp:(.text.startup+0x697): undefined reference to `boost::system::generic_category()' aescuda.cpp:(.text.startup+0x6a3): undefined reference to `boost::system::system_category()' collect2: ld returned 1 exit status make[1]: *** [/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/bin//release/AES] Error 1 make[1]: Leaving directory `/home/mahmood/gpgpu-sim_distribution/ispass2009-benchmarks/AES' make: *** [default] Error 2 Any thought on that? Regards, Mahmood

2 1

[coroutine] MinGW: terminate called after throwing an instance of 'boost::context::detail::forced_unwind'
by Jan Niklas Hasse 13 Oct '17

13 Oct '17

Hi :) I've tried to compile this simple Boost.Coroutine example: #include <iostream> #include <boost/coroutine2/all.hpp> void foo(boost::coroutines2::asymmetric_coroutine<void>::push_type& yield) { for (int i = 0; i < 10; ++i) { std::cout << i << std::endl; yield(); } } int main() { boost::coroutines2::asymmetric_coroutine<void>::pull_type coroutine(foo); for (int i = 0; i < 5; ++i) { coroutine(); } } On Linux this works as expected, just as on Windows with Visual Studio. But when I cross-compile on Linux using i686-w64-mingw32-g++ src/main.cpp -lboost_context-mt The resulting exe crashes with: 0 1 2 3 4 5 6 terminate called after throwing an instance of 'boost::context::detail::forced_unwind' abnormal program termination There's a similar problem on StackOverflow: https://stackoverflow.com/questions/45569418/how-to-use-boost-context-corre… But I'm having the crash only with the cross-compiled version, not MSVC. Am I doing something wrong? Or might this be a bug in Fedora's mingw32-boost package?

1 0

1.65.1 as modular packages on Conan.io
by Rene Rivera 13 Oct '17

13 Oct '17

Following on with the announcement before CppCon of the 1.64.0 modular packages here we are with more. I'm pleased to announce that the 1.65.1 Boost C++ Libraries are now available individually using the Conan package manager. There's even some improvements for the 1.64.0 package also :-) Find out more from the Bincrafters post here <http://bit.ly/2g6VEpp>[1]. For help using the packages you can bug the Bincrafters team in the #Conan CppLan Slack channel <http://bit.ly/2ykeqC0>[2]. Conan is a C/C++ (and more) package manager that supports an open ended set of build system and tool integrations including: VisualStudio, Xcode, CLion, Ninja, QMake, Premake, and yes even CMake <http://bit.ly/2xzhpbg>[3]. [1] <https://bincrafters.github.io/2017/10/13/Conan-Packages-Boost-1-65-1/> [2] <https://cpplang.now.sh/> [3] <http://docs.conan.io/en/latest/integrations.html> -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net

1 0

boost::filesystem and writing to Windows programdata structure
by Tim Burgess 12 Oct '17

12 Oct '17

Hi, I've an application that has been working fine under Windows 7, but I'm now fixing up for running on later Windows versions. I've been hitting unhandled exceptions when writing to c:\programdata\(my company)\(my app name)\ and understand that this is due to the permissions for such folders being more restrictive on Windows 8, 8.1 and 10. My research seems to indicate that I can modify my installer to set up my folders with appropriate permissions at install-time, but I'd prefer to use boost::filesystem to check folder/file permissions then change them at run-time, if necessary using appropriate csidl values. Can anybody offer any advice, please? Best wishes. Tim Burgess

4 5

[stacktrace] Trace information from GetExceptionInformation()?
by Nat Goodspeed 11 Oct '17

11 Oct '17

In an __except() filter expression (Microsoft Structured Exception), it's legal to call GetExceptionInformation() to retrieve a pointer to an _EXCEPTION_POINTERS struct. A little bit of Google searching turned up a few recipes for walking the stack information indirectly provided by that _EXCEPTION_POINTERS data. Would it be reasonable to have a Microsoft-specific stacktrace constructor accepting _EXCEPTION_POINTERS*? Or perhaps a factory function? I would like to be able to capture the platform-specific _EXCEPTION_POINTERS information, but then, once I have it in hand, engage the rest of the Boost.Stacktrace functionality. Apologies if this has already been asked and answered. If so, please simply point me to the previous discussion. Thank you!

2 1

boost::interprocess::managed_mapped_file filename
by Markus Bonk 10 Oct '17

10 Oct '17

Hi, Unfortunately wmanaged_mapped_file constructors use char instead of wchar for the filename. This causes big problems on windows where %appdata% and %localappdata% include the user name which may include Unicode characters that after conversion result in the windows ‘A’ methods failing to find the referenced file. I don’t know of any work around except using Unicode filenames. Does anyone know of a way around this. Are there any plans of making wmanaged_mapped_file use wchar for the filenames? Markus ________________________________ Markus Bonk Senior Software Engineer [cid:imageac7178.GIF@91f798f8.4ca4a8b2] 3Dconnexion GmbH Clarita-Bernhard-Str. 18 81249 München Germany Tel: +49 (89) 897 45 42 - 70 Fax: +49 (89) 897 45 42 - 50 markus_bonk(a)3dconnexion.com<mailto:markus_bonk@3dconnexion.com> www.3dconnexion.com<http://www.3dconnexion.com> Geschäftsführer: Antonio Pascucci Sitz der Gesellschaft: München Registergericht: München HRB 99232

1 0

Compiling boost with optional _GLIBCXX_DEBUG support
by Jayesh Badwaik 09 Oct '17

09 Oct '17

Hi, How to compile boost so that compilation of user programs both with _GLIBCXX_DEBUG and without _GLIBCXX_DEBUG is supported? Currently, if I compile boost with _GLIBCXX_DEBUG then I cannot compile my programs without this flag, and vice versa. The actual error comes from program_options attached in a file. I gather from the interweb that the error is well known, however, I could not find instructions to compile boost such that both options are supported. -- Cheers Jayesh Badwaik https://www.jayeshbadwaik.in

2 2

[review] The review period of Boost.DoubleEnded has ended -- thanks to all involved
by Thorsten Ottosen 09 Oct '17

09 Oct '17

Dear users and members of Boost, We are now done with the review of Benedek Thaler's Boost.DoubleEnded library. Many thanks to all those involved in discussions and reviews. It will take me some time to digest all the feedback and get back with the review results. kind regards Thorsten, review manager -- Best regards, Thorsten Jørgen Ottosen, Ph.D. Director of Research +45 23308797 Dezide (www.dezide.com)

1 0

[asio] "reverse" stream?
by Phil Sean 07 Oct '17

07 Oct '17

Hi, Is there a stream (or other implementation) in asio that reverses the next layer and the read()/write() layer of another stream? For example, a reverse ssl::stream would send/receive data in clear text, but read()/write() operations should rather expect encrypted data. Thanks.

2 1

[geometry] Best Fit Plane
by Manoj Lnu 07 Oct '17

07 Oct '17

Is there a function available in boost geometry to find the best fit plane ? I have a set of 3D points as input. Thanks, Manoj

2 1

Memory usage of boost::unordered_multimap and boost::unordered_multimap
by Ram 06 Oct '17

06 Oct '17

Hi, I need help in determining the amount of memory used by boost::unordered_multimap and boost::unordered_multimap. We have a large code base and we have some optimizations done using boost::unordered_multimap and boost::unordered_multimap. The speed it really good, but we want to measure the amount of space it is occupying. Can somebody please help with that? I would not be able to change to use a custom new/delete. Thanks

3 5

Why no mpl::_double?
by Florian Lindner 06 Oct '17

06 Oct '17

Hello, is there a reason why there are only integral types in the boost MPL, no double or alike? http://www.boost.org/doc/libs/1_65_1/libs/mpl/doc/refmanual/numeric.html What is the best way to achieve: template<> struct getArg<Multiquadrics> : boost::mpl::double_<1e-3> {}; so that it is compatible with mpl::list? besides just writing the struct myself :-) Thanks, Florian

1 0

[stacktrace] Test failures with Xcode 9
by Nat Goodspeed 06 Oct '17

06 Oct '17

I've just started building Boost 1.65.1 Stacktrace. On Mac with Xcode 9, I'm dismayed that it has failed a couple of its own self-tests. Lengthy (albeit snipped) output follows. darwin.compile.c++ bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test.o "g++" -O3 -Wall -pedantic -g -dynamic -gdwarf-2 -fexceptions -Wno-long-long -Wno-inline -fPIC -arch x86_64 -DBOOST_STACKTRACE_GNU_SOURCE_NOT_REQUIRED -O3 -fPIC -gdwarf-2 -stdlib=libc++ -mmacosx-version-min=10.9 -iwithsysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/ -DLL_RELEASE=1 -DLL_RELEASE_FOR_DOWNLOAD=1 -DNDEBUG -DPIC -DLL_DARWIN=1 -DLL_OS_DRAGDROP_ENABLED=1 -DCARES_STATICLIB -DLIB_NDOF=1 -Wno-c99-extensions -Wno-unused-const-variable -Wno-unused-function -Wno-unused-local-typedef -Wno-variadic-macros -std=c++14 -DBOOST_ALL_NO_LIB=1 -DBOOST_STACKTRACE_USE_ADDR2LINE -DNDEBUG -I"." -I"/Users/nat/linden/3p-boost-64/boost/stage/packages/include" -I"/Users/nat/linden/3p-boost-64/boost/stage/packages/include/zlib" -c -o "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test.o" "libs/stacktrace/test/test.cpp" darwin.compile.c++ bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test_impl.o "g++" -O3 -Wall -pedantic -g -dynamic -gdwarf-2 -fexceptions -Wno-long-long -Wno-inline -fPIC -arch x86_64 -DBOOST_STACKTRACE_GNU_SOURCE_NOT_REQUIRED -O3 -fPIC -gdwarf-2 -stdlib=libc++ -mmacosx-version-min=10.9 -iwithsysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/ -DLL_RELEASE=1 -DLL_RELEASE_FOR_DOWNLOAD=1 -DNDEBUG -DPIC -DLL_DARWIN=1 -DLL_OS_DRAGDROP_ENABLED=1 -DCARES_STATICLIB -DLIB_NDOF=1 -Wno-c99-extensions -Wno-unused-const-variable -Wno-unused-function -Wno-unused-local-typedef -Wno-variadic-macros -std=c++14 -DBOOST_ALL_NO_LIB=1 -DBOOST_STACKTRACE_USE_ADDR2LINE -DNDEBUG -I"." -I"/Users/nat/linden/3p-boost-64/boost/stage/packages/include" -I"/Users/nat/linden/3p-boost-64/boost/stage/packages/include/zlib" -c -o "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test_impl.o" "libs/stacktrace/test/test_impl.cpp" darwin.link bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho "g++" -o "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho" "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test.o" "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/test_impl.o" -g -Wl,-dead_strip -no_dead_strip_inits_and_terms -arch x86_64 testing.capture-output bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.run status=0 if test $status -ne 0 ; then echo Skipping test execution due to testing.execute=off exit 0 fi "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho" > "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.output" 2>&1 < /dev/null status=$? echo >> "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.output" echo EXIT STATUS: $status >> "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.output" if test $status -eq 0 ; then cp "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.output" "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.run" fi verbose=0 if test $status -ne 0 ; then verbose=1 fi if test $verbose -eq 1 ; then echo ====== BEGIN OUTPUT ====== cat "bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho.output" echo ====== END OUTPUT ====== fi exit $status ====== BEGIN OUTPUT ====== ... 0# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 1# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 2# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 3# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho ... 14# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 15# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 16# void test_nested<15ul>() in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 17# main in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho libs/stacktrace/test/test.cpp(200): test 'min_size > 2' failed in function 'void test_frame()' ' 0# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 1# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 2# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 3# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho ... 300# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 301# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 302# void test_nested<300ul>() in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 303# main in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho ' 0# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 1# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 2# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 3# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho ... 300# foo1(int) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 301# foo2(int, std::__1::pair<boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> >, boost::stacktrace::basic_stacktrace<std::__1::allocator<boost::stacktrace::frame> > > (*)(int)) in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 302# void test_nested<300ul>() in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho 303# main in /Users/nat/linden/3p-boost-64/boost/bin.v2/libs/stacktrace/test/addr2line_ho.test/darwin-4.2.1/release/debug-symbols-on/addr2line_ho libs/stacktrace/test/test.cpp(282): test 'boost::stacktrace::stacktrace(1, 1).size() == 1' failed in function 'int main()' 2 errors detected. EXIT STATUS: 1 ====== END OUTPUT ======

1 3

[Units]
by CD Clark 06 Oct '17

06 Oct '17

I am trying to create a set of units to use in a library, but I having trouble getting IO to work for some of them. Here is a simple example that demonstrates the problem. ============================ #include<iostream> #include <boost/units/systems/si.hpp> #include <boost/units/systems/si/io.hpp> using namespace boost::units; // short hand for meter namespace t { typedef si::length m; } namespace i { BOOST_UNITS_STATIC_CONSTANT( m, t::m ); } // centimeter namespace t { typedef make_scaled_unit< si::length, scale< 10, static_rational<-2> > >::type cm; } namespace i { BOOST_UNITS_STATIC_CONSTANT( cm, t::cm ); } // meter squared namespace t { typedef multiply_typeof_helper< m, m>::type m_m; } namespace i { BOOST_UNITS_STATIC_CONSTANT( m_m, t::m_m ); } // centimeter squared namespace t { typedef multiply_typeof_helper< cm, cm>::type cm_cm; } namespace i { BOOST_UNITS_STATIC_CONSTANT( cm_cm, t::cm_cm ); } // meter centimeter namespace t { typedef multiply_typeof_helper< m, cm>::type m_cm; } namespace i { BOOST_UNITS_STATIC_CONSTANT( m_cm, t::m_cm ); } // override default output, which prints "c(m^2)" namespace boost { namespace units { inline std::string name_string(const t::m_cm&) { return "meter centimeter"; } inline std::string symbol_string(const t::m_cm&) { return "m cm"; } } } // trying to overload output for centimeter squared namespace boost { namespace units { inline std::string name_string(const t::cm_cm&) { return "centimeter squared"; } inline std::string symbol_string(const t::cm_cm&) { return "cm^2"; } } } int main(int argc, char *argv[]) { std::cout << i::m << std::endl; std::cout << i::cm << std::endl; std::cout << i::m_m << std::endl; std::cout << i::m_cm << std::endl; //std::cout << i::cm_cm << std::endl; // this won't compile quantity<t::m_m> a1(100*i::cm_cm); std::cout << a1<< std::endl; // should be 0.01 m^2 quantity<t::m_m> a2(100*i::m_cm); std::cout << a2<< std::endl; // should be 1 m^2 return 0; } ============================ Basically, I am just trying to create a convenient set of short hands. Unit types are put in a 't' namespace and instances are put in a 'i' namespace with the same name. This works fine for doing calculations and conversions with the units, but I am having trouble with getting output to work for some of them. In the example above I create a centimeter unit by scaling the meter. Then I create three different area units with the product_typeof_helper struct: meter squared, meter centimeter, and centimeter squared. Conversions work for all three of these, but output will not work for the centimeter squared unit. The program above outputs m cm m^2 m cm 0.01 m^2 1 m^2 If I uncomment the line that tries to print i::cm_cm it won't compile. I get an error that says 'symbol' is not a member of ... and points at a line that says str += Begin::item::symbol() I can't understand why it doesn't work for a product of two scaled units. cdclark

2 4

Re: [Boost-users] boost::process
by Chris Rodgers 05 Oct '17

05 Oct '17

To answer my own question - this is one working possibility using boost::process::extend... #include <boost/process.hpp> #include <boost/process/extend.hpp> int main() { boost::filesystem::path myPath(".........toRun.exe......."); auto set_own_window = [](auto & exec) { exec.creation_flags |= boost::detail::winapi::CREATE_NEW_CONSOLE_; std::cerr << "in set_own_window" << std::endl; /* just for debugging */ }; bp::child c(myPath, "argument1", boost::process::extend::on_setup=set_own_window); return 0; } This works. Is it the right approach, or is there a better way? Best wishes, Chris. On 05/10/2017 17:14, Chris Rodgers wrote: > Hi, > > I'm trying to use Boost 1.65.1's boost::process::child in a Windows > console program. > > At the moment, the child process is launched in the same console window > as the parent. > > Is there an option to make a new console window for the child? > > The pre-boost-incorporation version of boost::process seemed to allow > manipulation of the startupInfo struct directly (e.g. > https://stackoverflow.com/questions/43582022/boostprocess-hide-console-on-w…) > and then a win32_launch call. But this seems to have been removed now? > > Any tips gratefully received. > > Thanks, > > Chris. >

1 0

PolyCollection requiring copyable
by d3fault 05 Oct '17

05 Oct '17

I'm impressed with PolyCollection. I use the list<interface*> strategy tons in my projects, and I didn't think NOT using a pointer there was even possible... but somehow you managed. It also makes sense why PolyCollection is faster to execute etc, the tutorial was well written. The only 'con' is that it requires a copy constructor. You mention later that some copy traits thing can be used to move the "copy code" outside of the class, but I am questioning the need for copying altogether. Is "copying" of the polymorphic types necessary for: a) Technical requirement otherwise it wouldn't compile b) Design decision because you think it's superior and helpful c) To facilitate copying of the PolyCollection object itself ....? If (b) or (c), can there be a slightly altered version of PolyCollection which does not allow/require copying? I'm completely fine (and even happier) _not_ being able to copy the PolyCollection. When I use the list<interface*> strategy, I tend to consider the list to be the owner of it's objects (and delete them when the list is deleted). There should be PolyCollection::emplace and the poly instances should "live" in the PolyCollection. Accessing the poly instances should be by [const] reference only (isn't this already the case? what benefit does the copy constructor bring?!?). I didn't examine the source so maybe it's (a) after all, in which case I apologize for wasting precious time, bandwidth, and disk space. d3fault

5 11

boost::process
by Chris Rodgers 05 Oct '17

05 Oct '17

Hi, I'm trying to use Boost 1.65.1's boost::process::child in a Windows console program. At the moment, the child process is launched in the same console window as the parent. Is there an option to make a new console window for the child? The pre-boost-incorporation version of boost::process seemed to allow manipulation of the startupInfo struct directly (e.g. https://stackoverflow.com/questions/43582022/boostprocess-hide-console-on-w…) and then a win32_launch call. But this seems to have been removed now? Any tips gratefully received. Thanks, Chris.

1 0

looking for a memory leak in an asio based application
by David Medine 05 Oct '17

05 Oct '17

I know that the answer to this question is /always/ 'no'. But is it possible, just possible that one can leak memory out of boost::asio? Let me explain. I work on an open source client/server data streaming library for multi-modal data streaming called labstreaminglayer (https://github.com/sccn/labstreaminglayer) At the core of the data transmission architecture is boost::asio. Now, to avoid calling collisions, the original author of the library shipped the source code with a name-mangled version of boost. Over the years this has yet to be updated so we are still relying on boost 1.57. The memory leak starts on the server side after a client is connected to it. This went undetected for years because it is very very slow and it depends on the sampling rate of the data stream. LSL (labstreaminglayer) is widely used in the neurophysiological research community (for whom the tool was intended), but normally in that field you are not sending samples faster than 500 Hz or so. But some devices are now available that offer relatively high sampling rates (e.g. Brain Products' actiCHamp can go as fast as 100kHz). The amount of memory that leaks seems to depend on how often data is sent, not how much data is send at a time. So, when the data is flowing quickly, the leak is severe. I am 99.99% sure that the allocation of memory for all the data I am sending is getting deallocated correctly. I don't see any leaking memory according to Visual Studio's diagnostic tools, nor can Deleaker spot anything. However, when I look at a server process in task manager, I can see the memory rising. I tried the asio::io_service::work trick (https://stackoverflow.com/questions/32258890/c-boost-asio-async-send-to-mem…) on my io_services, but this didn't have any effect. I have not gone through the whole pipeline yet, but I've been at this for two harrowing days already. So I just thought I would ask the list if anyone has seen anything like this before or if there has been any slow-leak fixes in boost (particularly asio) since 1.57 (I didn't see anything in the logs, but maybe I missed something). Due to the state of the project at this moment, it is non-trivial to update the name-mangled boost to another version, but it is far less trivial than the needle-in-a-haystack game I am playing right now. So, if someone can say with authority a boost update will fix everything I'll just do that and be happy. It's a long-shot, I know.

2 1

Bost Logging
by Mário Costa 04 Oct '17

04 Oct '17

Hi, I'm havving a bad time trying to figure out how to add and log custom keywords using boost/log. I havent been able to understand how exactly attribute keywords (BOOST_LOG_ATTRIBUTE_KEYWORD) bind with logging e.g. using BOOST_LOG_STREAM_WITH_PARAMS(logger, (??) (??)). For instance, if I define a keyword line_number, BOOST_LOG_ATTRIBUTE_KEYWORD(line_number, "LineNumber", unsigned int) and add it to the formmater logging::formatter formatter = expr::stream << "[" << line_number << "]" How do I use BOOST_LOG_STREAM_WITH_PARAMS(logger, (??)) Tanking an exemple from the severities, I should use a keyword parameter defining something like BOOST_PARAMETER_KEYWORD(sometag, line_number) then I should be able to use BOOST_LOG_STREAM_WITH_PARAMS(logger, (line_number = 10)) But those things just don add up together. I for sure missing the logics of the logging ... Thanks for any help! Cheers, mc

1 0

[geometry] Get points within certain radius?
by Florian Lindner 03 Oct '17

03 Oct '17

Hello, first of all thanks for the repliest to my previous geometry question! What is the best, especially fastest way to get all points within a certain radius of a point? Using the iterator method with nearest(pt, X) highly depends on X. Since I don't know this number, I have to guess it rather high. for (auto it = rtree.qbegin(bgi::nearest(point, results)) ; it != rtree.qend() ; ++it) { std::ignore = it; break; } results = 10 => time = 3.0s results = 100 => time = 22.6s results = 200 => time = 71.4s results = 300 => time = 153.2s though I always use just one result. The loop is inside another loop, not depending on results, so of course, the times are multiples of the actual times for that query. But clearly, choosing high numbers for results is not feasible. Another idea is to use the within() query with a circle of a radius. But bg seems to have no circle or sphere model. A workaround would be to use a box instead of a sphere. That means I have to test the results again, whether they are actually contained in th sphere. Alternatively, I could use the satisfies predicate. But wouldn't I give up all spatial information? This predicate needs to compare all vertices, don't it? It does include the knowledge, that when one point is discarded, all other points with a greater distance will discarded too. According to https://stackoverflow.com/questions/22909171/boostgeometry-nearest-neighbor…, the way to go seems to be to combine within(boundingBox) and satisfies(). Any other ideas? Thanks, Florian

2 1

[test] Is standalone use possible?
by Adam Nielsen 02 Oct '17

02 Oct '17

Hi all, I'm in the process of trying to remove the Boost dependency from my project, as it is causing too many difficulties for non-developers trying to run my code. This has been mostly solved by switching to C++11 and using the std:: implementations instead, however rather than rewrite all my unit tests I am hoping I can use a standalone version of Boost.Test, and distribute the code alongside my own. Unfortunately I am not quite sure how to extract the Test library out of the main Boost distribution. I have compiled "bcp" and used it to copy "test" into a new folder, but it seems to copy a huge chunk of Boost as well, including a bunch of libraries (system, thread, date_time, etc.) and I end up with 29 MB of source files, which seems wrong (especially considering my own codebase is barely 500 kB). Am I doing something wrong? I was hoping to use the header-only version of Boost.Test and this does seem to work when I #include the system-wide version of Boost (and don't link to any libraries), so it would seem that I don't need all those libraries that bcp copies. Is there any other way to access a slimmed-down standalone version of Boost.Test? Many thanks, Adam.

6 12

ק
by Ami Tavory 29 Sep '17

29 Sep '17

1 0

Enhancing the boost::asio::connect() socket interface
by martin doc 29 Sep '17

29 Sep '17

(apologies if this should be on -developers...) The connect() interface provided by boost caters to most common use and through access to the socket, various options can be managed without much hindrance. But there's one situation that boost does not handle well - when it is desirable to specify the local address to bind to. Going back to C, the usual program flow in this situation is something like this: fd = socket() bind(fd, local ip address) connect(fd, remote ip address) As boost::asio::connect() closes an open socket passed to it before making the remote connection, it's not possible to pass connect() a prebaked socket. In fact the amount of code required to use boost when binding a socket to a local address is more complicated than simply not using boost. What I'd like the boost community to consider is extending boost::asio to provide one or more variants of connect() that allows for a local endpoint (whether or not as an iterator I'll leave to others to debate but this isn't necessary - and then there's the M*N behavior or paired to decide) to be supplied in addition to the remote endpoint. I suppose I'm open minded as to whether or not the local address is supplied as an Iterator/endpoint as an extra arg or whether connect() is adopted to take endpoint pairs. Thoughts?

5 4