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

How strong is PropertyTree JSON support
by Michael Powell 09 Jan '19

09 Jan '19

Hello, I have a requirement to support parsing JSON, and while I could potentially pull together a Spirit Qi (or even X3, possibly) based grammar, I wonder with all the idiosyncrasies, i.e. particularly strings, escape sequences, Unicode, etc, is it worth it. Then there's the Boost.PropertyTree JSON support, which I think may be an adequate fit. However, just how robust is this support when it comes to handling some of the nuanced corner cases? The harder ones I think are the potential for escape sequences, Unicode, etc, embedded within a String. i.e. https://json.org/ or, http://es5.github.io/x7.html It seems with Property Tree there are also these limitations: <docs> The property tree dataset is not typed, and does not support arrays as such. Thus, the following JSON / property tree mapping is used: * JSON objects are mapped to nodes. Each property is a child node. * JSON arrays are mapped to nodes. Each element is a child node with an empty name. If a node has both named and unnamed child nodes, it cannot be mapped to a JSON representation. * JSON values are mapped to nodes containing the value. However, all type information is lost; numbers, as well as the literals "null", "true" and "false" are simply mapped to their string form. * Property tree nodes containing both child nodes and data cannot be mapped. </docs> It seems to me that much of the limitation is in adapting the PropertyTree to the JSON structure, but mostly vice versa. Not quite fitting a square peg in a round hole, but coming quite close, I think: "If a node has both named and unnamed child nodes, it cannot be mapped to a JSON representation." We're talking about the mapping from PropertyTree to JSON here? Seems like a potentially problematic issue depending on desired usage, 'all type information is lost; numbers, as well as the literals "null", "true" and "false" are simply mapped to their string form'. I'm not sure what "nodes containing both child nodes and data" means? https://www.boost.org/doc/libs/1_69_0/doc/html/property_tree/parsers.html#p… Besides these concerns, I should think a grammar is fairly straightforward to construct, if push came to shove. It's either living with the Boost.PropertyTree or rolling my own AST, which is not outside the realm of possibility for my purposes. Thoughts? Suggestions? Thanks! Michael Powell

4 3

Re: [Boost-users] How strong is PropertyTree JSON support
by Bjorn Reese 08 Jan '19

08 Jan '19

On 1/8/19 6:50 PM, Michael Powell via Boost-users wrote: > Thoughts? Suggestions? https://github.com/breese/trial.protocol http://breese.github.io/trial/protocol/trial_protocol/json.html

2 3

Boost wiki - revised Boost guidance for authors on Warnings - RFC
by Paul A. Bristow 08 Jan '19

08 Jan '19

As promised at the end of a long (hijacked!) thread on 'Warnings' http://boost.2283326.n4.nabble.com/Current-Guidance-on-Compiler-Warnings-td… starting from a query by Brian Kuhl of Wind River on Boost's policy on compiler warnings, I have spent some time revising the previous guidance document on Trac that I edited many years ago. This was a long and tedious task as Markdown, as most conveniently used on Github, is rather different from the mark-up language on Trac, leaving me slightly in fumble mode :-( I have made some updates en passant, but there is still much to do updating for the much improved granularity of warning suppression and perhaps more about other code improvement tools like Lint, UBSan. The overall structure leaves a lot to be desired, but I don't want to put any more work into this without some encouragement that it will prove useful. I have posted the result of my efforts on https://github.com/boostorg/boost/wiki/Guidelines:-Warnings and I am as promised I am starting this new thread on warning for your comments, corrections, condemnations etc. HTH Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830

2 1

[Solaris 11] wrong RUNPATH after install
by Dechaux Eric CEN (BCQ STIG) 07 Jan '19

07 Jan '19

Hello, I am building boost 1.69 on a Solaris 11.4 x86_64 box. After installation the shared libraries keep the boost dependencies from the build directory. The build log is without error and attached, ldd output is the following : :/usr/local/lib$ ldd libboost_*.so.1.69.0 libboost_chrono.so.1.69.0: bin.v2/libs/system/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_system.so.1.69.0 => (file not found) libstdc++.so.6 => /usr/lib/64/libstdc++.so.6 libm.so.2 => /lib/64/libm.so.2 librt.so.1 => /lib/64/librt.so.1 libgcc_s.so.1 => /usr/lib/64/libgcc_s.so.1 libpthread.so.1 => /lib/64/libpthread.so.1 libc.so.1 => /lib/64/libc.so.1 libboost_context.so.1.69.0: libstdc++.so.6 => /usr/lib/64/libstdc++.so.6 libm.so.2 => /lib/64/libm.so.2 librt.so.1 => /lib/64/librt.so.1 libgcc_s.so.1 => /usr/lib/64/libgcc_s.so.1 libpthread.so.1 => /lib/64/libpthread.so.1 libc.so.1 => /lib/64/libc.so.1 libboost_coroutine.so.1.69.0: bin.v2/libs/context/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_context.so.1.69.0 => (file not found) bin.v2/libs/thread/build/gcc-7.3.0/release/threadapi-pthread/threading-multi/visibility-hidden/libboost_thread.so.1.69.0 => (file not found) bin.v2/libs/chrono/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_chrono.so.1.69.0 => (file not found) bin.v2/libs/system/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_system.so.1.69.0 => (file not found) libstdc++.so.6 => /usr/lib/64/libstdc++.so.6 libm.so.2 => /lib/64/libm.so.2 librt.so.1 => /lib/64/librt.so.1 libgcc_s.so.1 => /usr/lib/64/libgcc_s.so.1 libpthread.so.1 => /lib/64/libpthread.so.1 libc.so.1 => /lib/64/libc.so.1 libboost_system.so.1.69.0: libstdc++.so.6 => /usr/lib/64/libstdc++.so.6 libm.so.2 => /lib/64/libm.so.2 librt.so.1 => /lib/64/librt.so.1 libgcc_s.so.1 => /usr/lib/64/libgcc_s.so.1 libpthread.so.1 => /lib/64/libpthread.so.1 libc.so.1 => /lib/64/libc.so.1 libboost_thread.so.1.69.0: bin.v2/libs/system/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_system.so.1.69.0 => (file not found) libstdc++.so.6 => /usr/lib/64/libstdc++.so.6 libm.so.2 => /lib/64/libm.so.2 librt.so.1 => /lib/64/librt.so.1 libgcc_s.so.1 => /usr/lib/64/libgcc_s.so.1 libpthread.so.1 => /lib/64/libpthread.so.1 libc.so.1 => /lib/64/libc.so.1 As a result I can't move the library on another box without changing the RUNPATH on the .so files with elfedit. I tried to build each library on it own but the final result is the same. What can I do ? Thanks. -- Eric Ce message électronique et tous les fichiers attachés qu'il contient sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le retourner à son émetteur. La publication, l'usage, la distribution, l'impression ou la copie non autorisée de ce message et des attachements qu'il contient sont strictement interdits. En cas d'urgence, composez le 17 ou le 112. Afin de contribuer au respect de l'environnement, merci de n'imprimer cet e-mail qu'en cas de necessite. This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual to whom it is addressed. If you have received this email in error please send it back to the person that sent it to you. Unauthorized publication, use, dissemination, forwarding, printing or copying of this email and its associated attachments is strictly prohibited. In case of emergency, dial number 17 or 112. To contribute to the environmental protection, please print this e-mail only if necessary.

1 0

Re: [Boost-users] I ran b2 with the -d+2 command and redirected the output to a file
by Osman Zakir 07 Jan '19

07 Jan '19

My project-config.jam file has quotes where needed, so that's not a problem. That file isn't the problem, but probably the commands I'm running are. I'll try to see if I can get it to work without Stacktrace. ________________________________ From: Osman Zakir <osmanzakir90(a)hotmail.com> Sent: Saturday, January 5, 2019 8:50 PM To: degski Subject: Re: [Boost-users] I ran b2 with the -d+2 command and redirected the output to a file I'll just build Boost with MSVC then, for now. And I'll wait for work on clang-cl build to be completed. I'll check out the posts in the archive that you mentioned, too. Maybe I'll something that can help me. ________________________________ From: degski <degski(a)gmail.com> Sent: Saturday, January 5, 2019 8:44 PM To: Osman Zakir Subject: Re: [Boost-users] I ran b2 with the -d+2 command and redirected the output to a file Yes, I did build 1.69 successfully [with thin-lto]. That won't help you, though [as I already gave you all the info]. Getting boost to build with clang-cl has been a long-term process [I've been pushing this for close to 2 years]. It only (mostly) works since [important work, boost 1.69] has been done by Peter Dimov (relatively recent)]. You really should dig into the archives to see what progress has been made (https://lists.boost.org/Archives/boost/2018/11/244235.php, but there are many more posts), not all might be perfect yet, we are on the bleeding edge here. The whole thing of building boost with clang-cl [as clang-cl itself, which is part of the problem, while at the same time MSVC is in significant flux as well] is a WIP (work in progress), so you cannot expect things to be perfect [yet, but the commitment is there (of all parties involved) and I am sure it will be good at some point in the (near?) future]. degski -- “If something cannot go on forever, it will stop" - Herbert Stein

3 11

Re: [Boost-users] I ran b2 with the -d+2 command and redirected the output to a file
by Osman Zakir 05 Jan '19

05 Jan '19

Okay, so what commands did you use when building, then? When it also built Stacktrace. And could you also try with version 1.69.0 and let me know how that turns out? ________________________________ From: degski <degski(a)gmail.com> Sent: Saturday, January 5, 2019 6:40 PM To: Osman Zakir Subject: Re: [Boost-users] I ran b2 with the -d+2 command and redirected the output to a file On Sat, 5 Jan 2019 at 15:37, degski <degski(a)gmail.com<mailto:degski@gmail.com>> wrote: You need something like libboost_stacktrace_windbg_cached-vc141-mt-sgd-1_65_1.lib and libboost_stacktrace_windbg-vc141-mt-sgd-1_65_1.lib [but then for 1.69 of course and the release builds as well]. Whether that is relevant to you is for you to decide. FYI, I was able to build those libs with clang-cl. degski My guess is that the _noop_ versions do nothing [a no op(eration)], but are just stub-libs to satisfy your linker. degski -- “If something cannot go on forever, it will stop" - Herbert Stein

2 1

Re: [Boost-users] I ran b2 with the -d+2 command and redirected the output to a file
by Osman Zakir 05 Jan '19

05 Jan '19

The Stacktrace libs I have are: "libboost_stacktrace_noop-clangw8-mt-d-x32-1_69.lib", "libboost_stacktrace_noop-clangw8-mt-d-x64-1_69.lib", "libboost_stacktrace_noop-clangw8-mt-x32-1_69.lib", and "libboost_stacktrace_noop-clangw8-mt-x64-1_69.lib" Should I have two more of the Stacktrace libs, or is this fine? As I said in my previous message, the first error actually comes from Boost.Stacktrace and it says: "error: no member named 'GetModuleFileNameA' in namespace 'boost::winapi'; did you mean simply 'GetModuleFileNameA'?". I also still need help on this issue I opened in the Boost.Asio GitHub: https://github.com/boostorg/asio/issues/184 . [https://avatars0.githubusercontent.com/u/18173932?s=400&v=4]<https://github.com/boostorg/asio/issues/184> Server application won't bind to ports on IP address other than my internal ones · Issue #184 · boostorg/asio<https://github.com/boostorg/asio/issues/184> As the title says, my server application doesn't bind to any ports on any IP address other than my computer's internal IP addresses (the localhost and 192.168.x.x ones). The application is ... github.com

2 1

I ran b2 with the -d+2 command and redirected the output to a file
by Osman Zakir 05 Jan '19

05 Jan '19

This is a follow-up to the message where I asked for help about a failed attempt to build Boost. I ran b2 with the -d+2 command in addition to the other commands and also redirected the output to a file. It's attached to this message, as well as the project-config.jam file.

5 7

New user : Help on Solaris
by Dechaux Eric CEN (BCQ STIG) 03 Jan '19

03 Jan '19

Hello everyone, I am a Solaris user and need to build pgAgent 4.0 on a Solaris 11.4 X86_64 box. pgAgent require boost withthreading. I have build boost 1.69 with no issue : sol114:/tmp/build/boost_1_69_0$ ./b2 threading=multi -d+2 -a Performing configuration checks - default address-model : 64-bit - default architecture : x86 Building the Boost C++ Libraries. - C++11 mutex : yes - lockfree boost::atomic_flag : yes - Boost.Config Feature Check: cxx11_auto_declarations : yes - Boost.Config Feature Check: cxx11_constexpr : yes - Boost.Config Feature Check: cxx11_defaulted_functions : yes - Boost.Config Feature Check: cxx11_final : yes - Boost.Config Feature Check: cxx11_hdr_mutex : yes - Boost.Config Feature Check: cxx11_hdr_tuple : yes - Boost.Config Feature Check: cxx11_lambdas : yes - Boost.Config Feature Check: cxx11_noexcept : yes - Boost.Config Feature Check: cxx11_nullptr : yes - Boost.Config Feature Check: cxx11_rvalue_references : yes - Boost.Config Feature Check: cxx11_template_aliases : yes - Boost.Config Feature Check: cxx11_thread_local : yes - Boost.Config Feature Check: cxx11_variadic_templates : yes - has_icu builds : yes warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - zlib : yes - bzip2 : yes - lzma : yes - zstd : no - icu : yes warning: non-free usage requirements <runtime-link>shared ignored warning: in main-target build_options at libs/locale/build/Jamfile.v2:414 warning: non-free usage requirements <runtime-link>shared ignored warning: in main-target build_flags at libs/locale/build/Jamfile.v2:415 - xopen-source-600-supported : yes - native-atomic-int32-supported : yes - native-syslog-supported : yes - pthread-supports-robust-mutexes : yes - compiler-supports-ssse3 : yes - compiler-supports-avx2 : yes - gcc visibility : yes - long double support : yes 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 - addr2line builds : yes - WinDbg builds : no - WinDbgCached builds : no - BOOST_COMP_GNUC >= 4.3.0 : no - zlib : yes - bzip2 : yes - lzma : yes - zstd : no Component configuration: - atomic : building - chrono : building - container : building - context : building - contract : 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 - stacktrace : building - system : building - test : building - thread : building - timer : building - type_erasure : building - wave : building [...] "g++" -fvisibility-inlines-hidden -fPIC -m64 -pthreads -O3 -finline-functions -Wno-inline -w -fvisibility=hidden -DBOOST_ALL_DYN_LINK=1 -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/cpplexer/re2clex/cpp_re.o" "libs/wave/src/cpplexer/re2clex/cpp_re.cpp" gcc.link.dll bin.v2/libs/wave/build/gcc-7.3.0/release/threadapi-pthread/threading-multi/visibility-hidden/libboost_wave.so.1.69.0 "g++" -L"/tmp/build/boost_1_69_0/bin.v2/libs/chrono/build/gcc-7.3.0/release/threading-multi/visibility-hidden" -L"/tmp/build/boost_1_69_0/bin.v2/libs/date_time/build/gcc-7.3.0/release/threading-multi/visibility-hidden" -L"/tmp/build/boost_1_69_0/bin.v2/libs/filesystem/build/gcc-7.3.0/release/threading-multi/visibility-hidden" -L"/tmp/build/boost_1_69_0/bin.v2/libs/system/build/gcc-7.3.0/release/threading-multi/visibility-hidden" -L"/tmp/build/boost_1_69_0/bin.v2/libs/thread/build/gcc-7.3.0/release/threadapi-pthread/threading-multi/visibility-hidden" -o "bin.v2/libs/wave/build/gcc-7.3.0/release/threadapi-pthread/threading-multi/visibility-hidden/libboost_wave.so.1.69.0" -shared "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/instantiate_cpp_exprgrammar.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/instantiate_cpp_grammar.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/instantiate_cpp_literalgrs.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/instantiate_defined_grammar.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/instantiate_predef_macros.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/instantiate_re2c_lexer.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/instantiate_re2c_lexer_str.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/token_ids.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/wave_config_constant.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/cpplexer/re2clex/aq.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/cpplexer/re2clex/cpp_re.o" "bin.v2/libs/filesystem/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_filesystem.so.1.69.0" "bin.v2/libs/thread/build/gcc-7.3.0/release/threadapi-pthread/threading-multi/visibility-hidden/libboost_thread.so.1.69.0" "bin.v2/libs/date_time/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_date_time.so.1.69.0" "bin.v2/libs/chrono/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_chrono.so.1.69.0" "bin.v2/libs/system/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_system.so.1.69.0" -lrt -fPIC -m64 -pthreads -fvisibility=hidden -fvisibility-inlines-hidden -mimpure-text common.copy stage/lib/libboost_wave.so.1.69.0 cp "bin.v2/libs/wave/build/gcc-7.3.0/release/threadapi-pthread/threading-multi/visibility-hidden/libboost_wave.so.1.69.0" "stage/lib/libboost_wave.so.1.69.0" ln-UNIX stage/lib/libboost_wave.so ln -f -s 'libboost_wave.so.1.69.0' 'stage/lib/libboost_wave.so' The Boost C++ Libraries were successfully built! The following directory should be added to compiler include paths: /tmp/build/boost_1_69_0 The following directory should be added to linker library paths: /tmp/build/boost_1_69_0/stage/lib However, when I try to build pgAgent 4.0 I have the following errors : sol114:/tmp/build/pgAgent-4.0.0-Source$ make CMake Warning at cmake/FindBoost.cmake:839 (message): New Boost version may have incorrect or missing dependencies and imported targets Call Stack (most recent call first): cmake/FindBoost.cmake:950 (_Boost_COMPONENT_DEPENDENCIES) cmake/FindBoost.cmake:1618 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:112 (FIND_PACKAGE) CMake Warning at cmake/FindBoost.cmake:839 (message): New Boost version may have incorrect or missing dependencies and imported targets Call Stack (most recent call first): cmake/FindBoost.cmake:950 (_Boost_COMPONENT_DEPENDENCIES) cmake/FindBoost.cmake:1618 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:112 (FIND_PACKAGE) CMake Warning at cmake/FindBoost.cmake:839 (message): New Boost version may have incorrect or missing dependencies and imported targets Call Stack (most recent call first): cmake/FindBoost.cmake:950 (_Boost_COMPONENT_DEPENDENCIES) cmake/FindBoost.cmake:1618 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:112 (FIND_PACKAGE) CMake Warning at cmake/FindBoost.cmake:839 (message): New Boost version may have incorrect or missing dependencies and imported targets Call Stack (most recent call first): cmake/FindBoost.cmake:950 (_Boost_COMPONENT_DEPENDENCIES) cmake/FindBoost.cmake:1618 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:112 (FIND_PACKAGE) CMake Warning at cmake/FindBoost.cmake:839 (message): New Boost version may have incorrect or missing dependencies and imported targets Call Stack (most recent call first): cmake/FindBoost.cmake:950 (_Boost_COMPONENT_DEPENDENCIES) cmake/FindBoost.cmake:1618 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:112 (FIND_PACKAGE) CMake Warning at cmake/FindBoost.cmake:839 (message): New Boost version may have incorrect or missing dependencies and imported targets Call Stack (most recent call first): cmake/FindBoost.cmake:950 (_Boost_COMPONENT_DEPENDENCIES) cmake/FindBoost.cmake:1618 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:112 (FIND_PACKAGE) CMake Warning at cmake/FindBoost.cmake:839 (message): New Boost version may have incorrect or missing dependencies and imported targets Call Stack (most recent call first): cmake/FindBoost.cmake:950 (_Boost_COMPONENT_DEPENDENCIES) cmake/FindBoost.cmake:1618 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:112 (FIND_PACKAGE) -- Boost version: 1.69.0 -- Found the following Boost libraries: -- filesystem -- regex -- date_time -- thread -- system -- chrono -- atomic -- -- ================================================================================ -- Configuration summary: -- -- Project : pgagent -- Description : pgAgent is a job scheduling engine for PostgreSQL -- Version : 4.0.0 -- -- PostgreSQL version string : PostgreSQL 10.6 -- PostgreSQL version parts : 10 -- PostgreSQL path : /appli/11.4.4.4.0-20181220-10.6 -- PostgreSQL config binary : /appli/11.4.4.4.0-20181220-10.6/bin/pg_config -- PostgreSQL include path : /appli/11.4.4.4.0-20181220-10.6/include -- PostgreSQL library path : /appli/11.4.4.4.0-20181220-10.6/lib -- PostgreSQL share path : /appli/11.4.4.4.0-20181220-10.6/share/postgresql -- -- Boost version : 1.69.0 -- Boost path : /tmp/build/boost_1_69_0 -- Boost include directory : /tmp/build/boost_1_69_0 -- Boost library directory : /tmp/build/boost_1_69_0/stage/lib -- Boost Static linking : NO -- ================================================================================ -- -- Configuring done -- Generating done -- Build files have been written to: /tmp/build/pgAgent-4.0.0-Source [ 11%] Built target run [ 22%] Building CXX object CMakeFiles/pgagent.dir/connection.cpp.o In file included from /tmp/build/boost_1_69_0/boost/thread/detail/platform.hpp:17:0, from /tmp/build/boost_1_69_0/boost/thread/mutex.hpp:12, from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:22, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/config/requires_threads.hpp:47:5: error: #error "Compiler threading support is not turned on. Please set the correct command line options for threading: -pthread (Linux), -pthreads (Solaris) or -mthreads (Mingw32)" # error "Compiler threading support is not turned on. Please set the correct command line options for threading: -pthread (Linux), -pthreads (Solaris) or -mthreads (Mingw32)" ^~~~~ In file included from /tmp/build/boost_1_69_0/boost/thread/mutex.hpp:12:0, from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:22, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/thread/detail/platform.hpp:71:9: error: #error "Sorry, no boost threads are available for this platform." # error "Sorry, no boost threads are available for this platform." ^~~~~ In file included from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:22:0, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/thread/mutex.hpp:18:2: error: #error "Boost threads unavailable on this platform" #error "Boost threads unavailable on this platform" ^~~~~ In file included from /tmp/build/boost_1_69_0/boost/thread/thread.hpp:12:0, from /tmp/build/boost_1_69_0/boost/thread.hpp:13, from /tmp/build/pgAgent-4.0.0-Source/include/job.h:16, from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:37, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/thread/thread_only.hpp:19:2: error: #error "Boost threads unavailable on this platform" #error "Boost threads unavailable on this platform" ^~~~~ In file included from /tmp/build/boost_1_69_0/boost/thread/detail/thread.hpp:21:0, from /tmp/build/boost_1_69_0/boost/thread/thread_only.hpp:22, from /tmp/build/boost_1_69_0/boost/thread/thread.hpp:12, from /tmp/build/boost_1_69_0/boost/thread.hpp:13, from /tmp/build/pgAgent-4.0.0-Source/include/job.h:16, from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:37, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/thread/detail/thread_heap_alloc.hpp:19:2: error: #error "Boost threads unavailable on this platform" #error "Boost threads unavailable on this platform" ^~~~~ In file included from /tmp/build/boost_1_69_0/boost/thread/thread_only.hpp:26:0, from /tmp/build/boost_1_69_0/boost/thread/thread.hpp:12, from /tmp/build/boost_1_69_0/boost/thread.hpp:13, from /tmp/build/pgAgent-4.0.0-Source/include/job.h:16, from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:37, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/thread/condition_variable.hpp:18:2: error: #error "Boost threads unavailable on this platform" #error "Boost threads unavailable on this platform" ^~~~~ In file included from /tmp/build/boost_1_69_0/boost/thread/detail/thread_group.hpp:10:0, from /tmp/build/boost_1_69_0/boost/thread/thread.hpp:13, from /tmp/build/boost_1_69_0/boost/thread.hpp:13, from /tmp/build/pgAgent-4.0.0-Source/include/job.h:16, from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:37, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/thread/shared_mutex.hpp:31:2: error: #error "Boost threads unavailable on this platform" #error "Boost threads unavailable on this platform" ^~~~~ In file included from /tmp/build/boost_1_69_0/boost/thread.hpp:17:0, from /tmp/build/pgAgent-4.0.0-Source/include/job.h:16, from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:37, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/thread/once.hpp:31:2: error: #error "Boost threads unavailable on this platform" #error "Boost threads unavailable on this platform" ^~~~~ In file included from /tmp/build/boost_1_69_0/boost/thread.hpp:18:0, from /tmp/build/pgAgent-4.0.0-Source/include/job.h:16, from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:37, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/thread/recursive_mutex.hpp:18:2: error: #error "Boost threads unavailable on this platform" #error "Boost threads unavailable on this platform" ^~~~~ I have no idea why the boost headers won't find the availability of threads as it has built fine with pthread : $ ldd /tmp/build/boost_1_69_0/stage/lib/libboost_system.so.1.69.0 libstdc++.so.6 => /usr/lib/64/libstdc++.so.6 libm.so.2 => /lib/64/libm.so.2 librt.so.1 => /lib/64/librt.so.1 libgcc_s.so.1 => /usr/lib/64/libgcc_s.so.1 libpthread.so.1 => /lib/64/libpthread.so.1 libc.so.1 => /lib/64/libc.so.1 Can anybody help me ? Best regards -- Eric Ce message électronique et tous les fichiers attachés qu'il contient sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le retourner à son émetteur. La publication, l'usage, la distribution, l'impression ou la copie non autorisée de ce message et des attachements qu'il contient sont strictement interdits. En cas d'urgence, composez le 17 ou le 112. Afin de contribuer au respect de l'environnement, merci de n'imprimer cet e-mail qu'en cas de necessite. This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual to whom it is addressed. If you have received this email in error please send it back to the person that sent it to you. Unauthorized publication, use, dissemination, forwarding, printing or copying of this email and its associated attachments is strictly prohibited. In case of emergency, dial number 17 or 112. To contribute to the environmental protection, please print this e-mail only if necessary.

2 2

ASIO vs Beast DynamicBuffer use
by Cristian Morales Vega 02 Jan '19

02 Jan '19

Hi, I have just noticed that while ASIO passes DynamicBuffers as && (https://www.boost.org/doc/libs/1_68_0/doc/html/boost_asio/reference/async_r…) Beast passes them via reference (https://www.boost.org/doc/libs/1_68_0/libs/beast/doc/html/beast/ref/boost__…) I'm guessing this happens because ASIO thinks you are going to use dynamic_string_buffer/dynamic_vector_buffer as DynamicBuffer, while Beast thinks you are going to use flat_buffer/multi_buffer. In the second case doesn't make sense to give ownership of the DynamicBuffer to the initiation function because then you would not be able to look at the received data when the operation completes. Since ASIO DynamicBuffer implementations are just adaptors over string/vectors that you keep, it makes sense to move those adaptors, you still keep the string/vector with the data. Have I got it right? But this raises the question: what should I use in my own initiating functions? Regards.

2 3