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

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

My last message
by Osman Zakir 02 Jan '19

02 Jan '19

Hi, everyone. Did you guys see my last message? I really need to get a reply ASAP.

4 9

function template with a universal reference to a specific type
by Ireneusz Szcześniak 01 Jan '19

01 Jan '19

Hi, I'm writing to ask a C++ question, not specifically Boost-related, but this list is the best place I know. How can I write a function template, which has a parameter of the universal reference to a specific type? I can write a function template like this: template <typename T> void foo(T &&t) { // The primary template implementation. cout << "Primary: " << __PRETTY_FUNCTION__ << endl; } And so I can call this function with an expression of any value category, and any type, cv-qualified or not, like this: int main() { foo(1); int i = 1; foo(i); const int ci = 1; foo(ci); } In my code I need to provide different implementations of foo for different types (and these types are templated). How can I accomplish that? Best, Irek

5 11

Error: no member named 'GetModuleFileNameA' in namespace 'boost::winapi'; did you mean simply 'GetModuleFileNameA'?
by Osman Zakir 31 Dec '18

31 Dec '18

Hi again, everyone. When trying to build Boost 1.69.0 after having placed my installation of Python 3.7.1 above the one of Python 2.7.15, I got the error mentioned in the title of this email. It says at the end, " ...failed updating 4 targets... ...skipped 8 targets... ...updated 2381 targets... " The project-config.jam file I used is attached to this message.

1 0

Errors with 1.69 when compiling with /clr on MSVC
by Stian Zeljko Vrba 30 Dec '18

30 Dec '18

I get the following warning and error when compiling a C++/CLI file that includes boost 1.69. 1>c:\quinesoftwarebase\include\boost\type_traits\detail\is_member_function_pointer_cxx_11.hpp(114): error C2764: 'C': template parameter not used or deducible in partial specialization 'boost::is_member_function_pointer<Ret(Args...)>' 1>c:\quinesoftwarebase\include\boost\type_traits\detail\is_member_function_pointer_cxx_11.hpp(125): warning C4575: '__vectorcall' incompatible with the '/clr' option: converting to '__stdcall' Is there a workaround for this? -- Stian

3 3

Re: [Boost-users] [cfe-dev] [llvm-dev] Error: ISO C++17 does not allow 'register' storage class specifier [-Wregister], when building Boost 1.69.0
by Osman Zakir 25 Dec '18

25 Dec '18

I'll build using C++14 mode, then. I wonder if Python 3.7.1 has this issue as well? If it doesn't, then maybe Boost should switch over to that version of Python. ________________________________ From: Matthieu Brucher <matthieu.brucher(a)gmail.com> Sent: Tuesday, December 25, 2018 2:56 PM To: Oleg Smolsky Cc: Craig Topper; Osman Zakir; clang developer list; cfe-users(a)lists.llvm.org; llvm-dev(a)lists.llvm.org Subject: Re: [cfe-dev] [llvm-dev] Error: ISO C++17 does not allow 'register' storage class specifier [-Wregister], when building Boost 1.69.0 The issue comes in part form the Python headers that have the keyword. Unfortunately, this also means that there is an issue while building user code. But it's not a Boost code issue for this library, but a Python one. Regards, Matthieu Le mar. 25 déc. 2018 à 02:08, Oleg Smolsky via cfe-dev <cfe-dev(a)lists.llvm.org<mailto:cfe-dev@lists.llvm.org>> a écrit : Yes, this keyword is no longer valid starting from C++17: https://en.cppreference.com/w/cpp/keyword/register I realize that the "why" probably doesn't help you move forth with your problem, so here are a couple suggestions how to get over it: * Build Boost in C++14 mode with -std=c++14 * Cut out "register" from the Boost source and rebuild * Try a newer Boost version, it may have been fixed Oleg. On 2018-12-23 09:26, Craig Topper via cfe-dev wrote: This seems a better question for cfe-dev or cfe-users ~Craig On Sat, Dec 22, 2018 at 12:23 PM Osman Zakir via llvm-dev <llvm-dev(a)lists.llvm.org<mailto:llvm-dev@lists.llvm.org>> wrote: When trying to build Boost using LLVM, I had this error: " error: ISO C++17 does not allow 'register' storage class specifier [-Wregister] " I attached the project-config.jam file I used to this message. Someone please help me out (if there's someone on here who can). _______________________________________________ LLVM Developers mailing list llvm-dev(a)lists.llvm.org<mailto:llvm-dev@lists.llvm.org> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev _______________________________________________ cfe-dev mailing list cfe-dev(a)lists.llvm.org<mailto:cfe-dev@lists.llvm.org> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev _______________________________________________ cfe-dev mailing list cfe-dev(a)lists.llvm.org<mailto:cfe-dev@lists.llvm.org> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev -- Quantitative analyst, Ph.D. Blog: http://blog.audio-tk.com/ LinkedIn: http://www.linkedin.com/in/matthieubrucher

2 1

Problem downloading 1.69.0 for Windows
by tim＠raisedbar.net 24 Dec '18

24 Dec '18

Hi, Windows Defender is blocking my download from https://www.boost.org/users/history/version_1_69_0.html as it is identified as being unsafe. Can anybody advise, please? Best wishes. Tim Burgess Raised Bar Ltd. E: <mailto:tim@raisedbar.net> tim(a)raisedbar.net M: +44 (0)7989 486976

2 2

[Asio/Beast] Any non-obvious reasons for no bind_executor_and_allocator?
by Sorin Fetche 23 Dec '18

23 Dec '18

Hi, As I'm looking to modernize an older C++03 project based on Boost.Asio to use C++17 and the net TS api, I am not ready yet to give up on using lambdas for completion handlers. Boost.Asio and Boost.Beast have some utilities for correctly implementing asynchronous composed operations but from them only asio::bind_executor seems to be applicable to lambdas. And the problem is that it only associates an executor with a (lambda) object; I didn't find any utility for associating an allocator too. Could there be any reason for a utility that associates both an executor and an allocator with an object to not work correctly when implementing asynchronous operations? Or is it just that this utility has not been implemented yet? I did come across the paper "Networking TS Associations for Call Wrappers"[1], but I didn't see any mention there about bind_executor or something similar for allocators or why this kind of approach wouldn't work. I would be very happy if I could write something like: asio::post( socket_.get_executor(), bind_executor_and_allocator_from( handler_, [...] { self_.handler_(...); })); and, unless I'm missing something, such a utility could be implemented similarly to the existing asio::bind_executor. Thank you, Sorin [1] http://open-std.org/JTC1/SC22/WG21/docs/papers/2018/p1133r0.html

2 7

Update for C++17 register keyword error question
by Osman Zakir 23 Dec '18

23 Dec '18

This is the error I get when trying to build Boost 1.69.0 with LLVM: "error: ISO C++17 does not allow 'register' storage class specifier [-Wregister]". I've also sent an email about this to the LLVM developer mailing list. I've attached the project-config.jam file to this message. Please let me know how to fix this. Thanks in advance.

2 2

[uuid] constexpr uuid from string and ""_uuid literal
by Tobias Loew 23 Dec '18

23 Dec '18

Hi, while searching for constexpr GUID from string generators, I found https://gist.github.com/AlexBAV/b58e92d7632bae5d6f5947be455f796f . Since I still work with VS 2015, I wrote a C++11 constexpr version incl. boost-uuid generators. If there's interest adding this to boost uuid, please have a look at https://github.com/tobias-loew/constexpr-GUID-cpp-11 Tobias -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Users-f2553780.html

2 1

Patch for using boost-1_69_0 and clang-cl
by JR Cary 23 Dec '18

23 Dec '18

I found that I had to apply the attached patch to build another project that uses boost with clang-cl, or else I got an error that complained about the non-existence of std::snprintf. John Cary

2 1

Error when trying to build Boost 1.69.0 with LLVM
by Osman Zakir 22 Dec '18

22 Dec '18

When trying to build Boost 1.69.0 with LLVM, I had an error about the "register" keyword, regarding the removal of it in C++17. I searched on the Web and found out that I can use the "-Wno-register" flag to calm down Clang 6.0.0. What do I do in Clang 8.0.0? The same?

1 0

boost_1_19_0 fails to build random using clang-cl
by JR Cary 21 Dec '18

21 Dec '18

This is now more of an FYI, as I can disable random and get the build I need. boost 1_69_0 clang version 8.0.0 (trunk 349323) Windows 10 Build command: ./b2 toolset=clang-win runtime-link=shared link=shared define=BOOST_TEST_DYN_LINK cxxflags='-DBOOST_THREAD_DONT_USE_CHRONO' linkflags='-DBOOST_THREAD_DONT_USE_CHRONO' address-model=64 threading=multi variant=release -s NO_COMPRESSION=1 --layout=system --abbreviate-paths -j2 --without-python --without-mpi --without-log --without-math stage The first error is Creating library bin.v2\libs\random\build\clng-win-8.0.0\rls\adrs-mdl-64\thrd-mlt\boost_random.lib and object bin.v2\libs\random\build\clng-win-8.0.0\rls\adrs-mdl-64\thrd-mlt\boost_random.exp^M random_device.obj : error LNK2019: unresolved external symbol __imp_CryptEnumProvidersA referenced in function "public: __cdecl boost::random::random_device::impl::impl(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (??0impl@random_device@random@boost@@QEAA@AEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z)^M random_device.obj : error LNK2019: unresolved external symbol __imp_CryptAcquireContextA referenced in function "public: __cdecl boost::random::random_device::impl::impl(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (??0impl@random_device@random@boost@@QEAA@AEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z)^M random_device.obj : error LNK2019: unresolved external symbol __imp_CryptReleaseContext referenced in function "public: __cdecl boost::random::random_device::impl::~impl(void)" (??1impl@random_device@random@boost@@QEAA@XZ)^M random_device.obj : error LNK2019: unresolved external symbol __imp_CryptGenRandom referenced in function "public: unsigned int __cdecl boost::random::random_device::operator()(void)" (??Rrandom_device@random@boost@@QEAAIXZ)^M bin.v2\libs\random\build\clng-win-8.0.0\rls\adrs-mdl-64\thrd-mlt\boost_random.dll : fatal error LNK1120: 4 unresolved externals^M clang-cl: error: linker command failed with exit code 1120 (use -v to see invocation)^M The build succeeds upon adding --without-random to the build invocation. I tried attaching the full log, but then the message was rejected for being too large. ..................John Cary

1 0

Questions about Boost.Multiprecision..
by A Z 20 Dec '18

20 Dec '18

I want to be performing some algebraic functions work on cpp_rational which I will be using templates with the following type to configure precision (and scale?) #include <boost/multiprecision/cpp_int.hpp> in order to avoid the use of floating point types. --What is the #include statement for cpp_rational? I can't manage to find it. -When using non-floating point, is there a method to obtain a variable precision pi, or do I have to use arccos(-1); ? What is the file to import for that? -If I want to import a non-floating-point (cpp_rational) library power, nth root, trigonometry, all the useful function, what is the #include and the file in boost for that?

2 1

Having some trouble with bootstrapping Boost to use LLVM
by Osman Zakir 20 Dec '18

20 Dec '18

I changed the project-config.jam file in my Boost source tree to have Boost.Build use LLVM, but then when I used "bootstrap" command after, I saw that it was still using MSVC. When I looked at the project-config.jam file again at that point, I saw that its content had been reverted back to the default one for building with MSVC. What's going on? What do I need to do? Is there an argument I need to provide to the bootstrap command here so that it'll keep the configuration file content that I want it to? And is there no help command that would let me see what arguments, if any, I can pass to the tool? Another thing I want to ask is whether or not I need to have Boost.Built emit library files with a .bc extension to be able to link them with code I want to build using the Emscripten compiler. I ask because Emscripten needs compiled libraries to have been compiled to LLVM bitcode, and when Emscripten itself does this it adds the .bc extension instead of the .lib one.

2 2

integer_log2.hpp header deprecation using Boost
by Michael Powell 19 Dec '18

19 Dec '18

Hello, I am receiving a deprecation warning: d:\dev\boost.org\boost_1_69_0\boost\pending\integer_log2.hpp(7): note: This header is deprecated. Use <boost/integer/integer_log2.hpp> instead. The immediate includes are these: #include <boost/uuid/uuid.hpp> #include <boost/uuid/uuid_io.hpp> #include <boost/uuid/random_generator.hpp> But I am also leveraging Spirit, Format, Variant, Optional, to name a few, that I can determine. I am not including "integer_log2.hpp" directly, so I wondered which library(ies) might have this as a dependency? Spirit? Phoenix, via Spirit? Format? Thoughts? Suggestions? Cheers, Michael Powell

1 1

odeint: how to solve ODE as you go without deciding upfront what the interval is?
by Yuri 19 Dec '18

19 Dec '18

The function 'integrate' solves ODE for a pre-defined interval of time. What if I don't know what the interval is? I just need a few values, and then I would like to decide if I need more values, and when to stop. I don't want to just solve for some arbitrarily large interval, because this would waste CPU. On the other hand, choosing the shorter original interval and then continuing would introduce unnecessary errors if one would do this too many times. It seems like either the 'observer' function should have another argument: 'stop', or the interface should allow continuation. Yuri

1 0

[Spirit] X3 thread-safety
by Igor R 19 Dec '18

19 Dec '18

Hello, In my project I run x3-based parsers in parallel, using openmp. I've just moved from boost 1.64 to 1.68, and the parsers now cause segfault (heap corruption) - quite consistently, every time I run the program. OTOH, with 1.64 it never crashed. Before I begin to debug it in depth, I'd like to know if there's some known issue with Spirit's thread-safety in Boost 1.68. Did anyone encounter thread-safety issie with the recent Spirit versions? Thanks.

1 0

Build boost asio http server examples single threaded using c++03
by Eric Curtin 19 Dec '18

19 Dec '18

Hi Guys, I was wondering if anyone could help me out building all the boost asio http server examples from: https://github.com/boostorg/asio/tree/develop/example/cpp03/http But catch is, I need to use c++03/98, single threaded without dependencies on std::thread, boost::thread or posix threads. I also need static linking to all the other boost libraries. Also want to compile with g++ -O3 -flto on x86_64 Linux. How can I build these examples like this? This is also a question on stackoverflow: https://stackoverflow.com/questions/53822438/building-boost-asio-without-th… Lets say the build environment is this one: curtine/dockerfiles-fat:ubuntu18.04 Regards, Eric

2 1

[Asio] Combining use_future with strands
by Sorin Fetche 19 Dec '18

19 Dec '18

Hi, Is there a way to combine the special use_future completion token with a strand? Something with the meaning of: - the asynchronous operation should pass the result to the future it returns, and - the internal operations of it (if any) should run in a strand Code snippet: asio::io_context io_context; asio::io_context::strand strand(io_context); std::future<void> f = async_my_operation(io_context, <params>, asio::use_future); //________________________________________How to add the strand here ^^^ ? The code area where I would like to apply this is in this test program: https://github.com/sorf/cpp-dev-new/blob/abf9d831a0b82fb81751eee6cfa498d3b9… The self contained program and its output is here: https://wandbox.org/permlink/pF5Hbm6jqPOmEKbO As a background, the test program I wrote is based on these Boost.Asio examples: - for strand usage (i.e. bind_executor): https://github.com/boostorg/asio/blob/develop/example/cpp03/tutorial/timer5… - for composed operations: https://github.com/boostorg/asio/blob/develop/example/cpp11/operations/comp… and implements a composed operation that runs multiple internal operations in parallel and in series. Similar to the constructor of a socket or a timer object, the operation receives as a parameter an io_context; it doesn't offer an overload that receives a strand object directly. The operation is then tested with callback completion, callback completion in a strand, future and future + strand (where the test fails). Thank you, Sorin

5 7

How to implement a visitor pattern over an AST
by Michael Powell 19 Dec '18

19 Dec '18

Hello, I have an AST successfully building, generating text file, and subsequently Spirit Qi parsing for verification purposes. Now I want to implement a visitor pattern over that AST, somehow... For "calculators" and such, "evaluating" those expressions is one thing; however, this AST is not that. It is closer akin to a parsed Xml or Json model/tree. In other words, I'd like for it to feel sort of like an iterator if that's even possible. It should have contextual awareness where it is at all times, etc, perhaps "incrementing" is a depth first analysis. In particular I have in mind to iterate the expected and actual AST results in order to perform the verification. In other words, I might do something like this: auto expected_it = ast_visitor{&expected}; auto actual_it = ast_visitor{&actual}; REQUIRE(expected_it); REQUIRE(actual_it); REQUIRE(*expected_it == *actual_it); // Rinse and repeat ++expected_it; ++actual_it; REQUIRE(*expected_it == *actual_it); I wonder if something like this is even possible from the Boost libraries? Or interested to hear any insights on the subject. For that matter, I wonder it is more appropriate to simply implement the logical operators. Thanks! Michael Powell

4 7

Understanding fibers
by Stephan Menzel 18 Dec '18

18 Dec '18

Hello @ll, I am in the process of transforming a sync server application to an async approach. The framework in use (not asio) instantiates and calls an object representing the call when a request comes in, allows me to do things, fill a response object and then expects me to call a finish() method which will send the response and start the next request. This is not what this question is about but more like my circumstances. All code is pseudocode please... void rpc_work() { const value = do_stuff(request); response.fill_value(value) parent->finish(); } Now some of the calls will imply calling methods, which block on some operations, waiting for external resources to respond. Obviously in an async server with only one thread, this will block everything. So I'm looking for a clever way to structure this. My approach so far (in the prototype) is to go boost::async() for those operations. Like this: void rpc_work() { // prepare work boost::async(launch::any, [request, response, parent]() { const value = do_blocking_stuff(request); response.fill_value(value) parent->finish(); }); } The way I understand boost::async or indeed std::async is, that normally it will just spawn a thread for the operation. The best I can hope for is a thread pool but this is not guaranteed either (on Linux x64 gcc 7.3). So I started looking into fibers but I'm having a hard time understanding them, which is why I post here. From what I gather, what I have here is a prime use case as it matches many things the docs talk about. And yet they also suggest that the fibers are very intrusive and everything underneath do_blocking_stuff() would have to be aware of being in a fiber and yield() when appropriate. Is this correct? What would this mean? Most if not all of the blocking operations are using boost::thread::futures in their blocking things. They would do things like... value_t do_blocking_stuff(request) { boost::future<value_t> fv = retrieve_value_from_somewhere(); fv.wait_for(timeout); return fv.get() } Now, considering I would use fibers in the server, would I have to use 'fiber futures' here to make this work? To make the blocking functions automatically 'fiber aware' and yield() when they would block? This would imply replacing the thread::futures? And if so, how will I know when the value is there and they are ready to continue? And how will I cause this continuation? Do I have to keep track of them and somehow poll() them in a loop or something? I am aware of the broad nature of my question but perhaps someone can chime in and give some hints that allow me to understand them better. They look like they would fit my use case perfectly but I am a bit reluctant of dragging the concept all throughout the code until I realize it won't work. Perhaps someone can eli5 this to me ;-) Cheers, Stephan

4 13

Boost Process fails on Solaris 10 in async mode
by Sanket Sharma 18 Dec '18

18 Dec '18

Hi, I tried installing boost process on my Solaris 10 Sparc machine. On compiling it using gcc-6.3.0, I ran into a static assert failure at compile time at https://github.com/boostorg/process/blob/boost-1.68.0/include/boost/process…. In order to fix that, I changed static_assert(!WIFEXITED(still_active) && !WIFSIGNALED(still_active), "Internal Error"); to static_assert(!WIFEXITED(still_active), "Internal Error"); There is some discussion about this at https://www.openwall.com/lists/musl/2018/08/10/1 Now, the following code works well onCentOS 7(where no change was made to Boost process), but fails on Solaris 10 (where I made the above change as a workaround). On Solaris 10, the return code is 127 and stdout and stderr are empty. #include <iostream>#include <thread>#include <boost/process.hpp>#include <boost/asio.hpp> namespace bp = boost::process ;int main(int argc, char** argv){ std::future<std::string> dataOut; std::future<std::string> dataErr; std::string command = "ls"; boost::asio::io_service ios; bp::child c(command, bp::std_out > dataOut, bp::std_err > dataErr, ios); ios.run(); c.wait(); int result = c.exit_code(); std::string stdOut = dataOut.get(); std::string stdErr = dataErr.get(); std::cout << "Exit Code " << result << std::endl; std::cout << "stdOut " << stdOut << std::endl; std::cout << "stdErr " << stdErr << std::endl; return 0;} Output on CentOS 7 Exit Code 0 stdOut a.out main.cppProcess.cppProcess.h simple.cpp stdErr Output on Solaris 10 Exit Code 127 stdOut stdErr 1. Has my workaround to install Boost process on Solaris 10 broken it? 2. Is Boost-1.68.0 not supported on Solaris? 3. Is there a way I can get Boost Process to work on Solaris 10 in async mode? https://stackoverflow.com/questions/53780273/boost-process-fails-on-solaris… -- Regards, Sanket

1 0