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

[boost.test] Colors
by Udo Steinbach 20 Feb '19

20 Feb '19

Ahoi! I use boost.test and have now updated to boost v1.68 on Windows, working in standard console. Now Test has colored output, YEAH. The result you see in the picture https://www2.pic-upload.de/img/36193998/no_error_detected.png Notice that I don't use the standard color scheme. With set BOOST_TEST_COLOR_OUTPUT=1 text is light green on gray, bad to read. set BOOST_TEST_COLOR_OUTPUT=0 does black on gray. After that the colors are set to my scheme. Now error result with set BOOST_TEST_COLOR_OUTPUT=1: https://www2.pic-upload.de/img/36193997/failure.png Light red on gray, OK to read, but reset to dark red on gray. I have to use the color command to reset the colors. With command line options it's all the same. Hmmm, how useful can colors be, if the standard output (no error detected) is only one short line? Both pics on https://www.pic-upload.de/gal-1197957/om664y/1.html -- Fahrradverkehr in Deutschland: http://radwege.udoline.de/ GPG: A245 F153 0636 6E34 E2F3 E1EB 817A B14D 3E7E 482E

2 1

Problem with boost threads on hpux
by John Parke 20 Feb '19

20 Feb '19

Hi: I am trying to use boost threads with condition variables on hpux with aCC compiler. The compiler has incomplete support of C++11 standard. It does not have <chrono> or <thread> headers. I get the following error message when compiling a program which is using condition variables: "/usr/local/include/boost/thread/pthread/thread_data.hpp", line 344: error #2135: namespace "boost::chrono" has no member "steady_clock" void sleep_until(const chrono::time_point<chrono::steady_clock, Duration>& t) ^ The c++ code is { while (bufferIsEmpty[bufferPairNo]) { boost::unique_lock<boost::mutex> lock (bufferIsEmptyMutex[bufferPairNo]); =>> zb_bufferIsEmptyCondVar[bufferPairNo].wait_for (lock, boost::chrono::microseconds (100)); } } The version of boost I am using is 1.69.0. I build boost with: ./bjam -a -j6 install --build-dir=build address-model=64 variant=release link=static \ threading=multi runtime-link=static \ define=BOOST_THREAD_DONT_USE_CHRONO \ --with-date_time --with-filesystem \ --with-system --with-thread When I look at the boost header file, I see this: boost/thread/pthread/ thread_data.hpp #ifdef BOOST_THREAD_USES_CHRONO template <class Rep, class Period> void sleep_for(const chrono::duration<Rep, Period>& d) { hidden::sleep_for_internal(detail::platform_duration(d)); } template <class Duration> line 344 >> void sleep_until(const chrono::time_point<chrono::steady_clock, Duration>& t) { sleep_for(t - chrono::steady_clock::now()); } It appears that the define=BOOST_THREAD_DONT_USE_CHRONO, had no affect. Have I built this correctly, or is there another problem? I would greatly appreciate any help on this. Best regards, John John Parke Alebra Technologies Inc. PO Box 120390 New Brighton, MN 55112 770-425-1810

2 2

[log] Warning LNK4217 when compiling using clang-cl
by Marco Craveiro 14 Feb '19

14 Feb '19

Hi boost-users, I'm consuming boost 1.69 successfully from vcpkg, on a number of platforms, including MSVC and clang-cl on Windows. However, for some reason, whilst my MSVC is more or less clean of warnings, the clang-cl build is littered with LNK4217's. These appear to be related to boost.log, and more specifically get_tss_data and set_tss_data: warning LNK4217: locally defined symbol ?get_tss_data@detail@boost@@YAPEAXPEBX@Z (void * __cdecl boost::detail::get_tss_data(void const *)) imported in function "public: struct boost::log::v2s_mt_nt6::sinks::basic_formatting_sink_frontend<char>::formatting_context * __cdecl boost::thread_specific_ptr<struct boost::log::v2s_mt_nt6::sinks::basic_formatting_sink_frontend<char>::formatting_context>::get(void)const " (?get@?$thread_specific_ptr@Uformatting_context@?$basic_formatting_sink_frontend@D@sinks@v2s_mt_nt6@log@boost@@@boost@@QEBAPEAUformatting_context@?$basic_formatting_sink_frontend@D@sinks@v2s_mt_nt6@log@2@XZ) warning LNK4217: locally defined symbol ?set_tss_data@detail@boost@@YAXPEBXV?$shared_ptr@Utss_cleanup_function@detail@boost@@@2@PEAX_N@Z (void __cdecl boost::detail::set_tss_data(void const *,class boost::shared_ptr<struct boost::detail::tss_cleanup_function>,void *,bool)) imported in function "public: __cdecl boost::thread_specific_ptr<struct boost::log::v2s_mt_nt6::sinks::basic_formatting_sink_frontend<char>::formatting_context>::~thread_specific_ptr<struct boost::log::v2s_mt_nt6::sinks::basic_formatting_sink_frontend<char>::formatting_context>(void)" (??1?$thread_specific_ptr@Uformatting_context@?$basic_formatting_sink_frontend@D@sinks@v2s_mt_nt6@log@boost@@@boost@@QEAA@XZ) Googling revealed that this problem indicates some issue on exports (e.g. __declsepc...), but I haven't managed to figure out exactly what is causing it. Have you seen anything of this ilk? Any pointers would be greatly appreciated. Cheers -- Marco Craveiro MD, Domain Driven Consulting about: http://about.me/marcocraveiro blog: http://mcraveiro.blogspot.co.uk twitter: https://twitter.com/MarcoCraveiro That the Ideas are themselves manifestations (of the Idea-Idea) and that the Idea-Idea is a-kind-of Manifestation-Idea—which is a-kind-of itself, so that the system is completely self-describing— would have been appreciated by Plato as an extremely practical joke [Plato]. -- Alan Key

1 0

Reading a file in reverse using boost::iostreams
by Sean Farrow 13 Feb '19

13 Feb '19

Hi, Is there an easy way to read a file in reverse using boost::iostreams? I've got a case where I need to detect whether text is present and it's closer to the end of the file than the beginning. Any help appreciated. Kind regards Sean.

5 5

Boost::Process doesn't work with #define new (boost 1.69)
by Vivek Subramanian 12 Feb '19

12 Feb '19

Hello, I did #define new for debugging memory leaks, and I get this error: "no instance of boost::process::detail::windows::windows_file_codecv operator new matches arguement list" in file boost\process\local.hpp So I did #ifdef new #undef new #endif right before it and it works fine. Hope that this could be of use to someone! Thanks and Regards, Vivek S

4 5

converting a string to base64
by Sean Farrow 08 Feb '19

08 Feb '19

Hi, Does anyone know of an open source boost.iostreams filter that will convert a string (either std::string, or std::wstring) to/from base64? I know there is some code within beest, but wondered whether this had been wrapped? Similarly, I know that there were issues with boost.serialization's base64 code (from memory, I don't think it padded correctly) and don't think there was a filter for this either. Any help appreciated. Kind regards Sean.

3 3

generalize boost macros
by Gero Peterhoff 06 Feb '19

06 Feb '19

Hello, I have some ideas for config/predef, multiprecision and others. config/predef: What bothers me is the inconsistent nomenclature of several macros. For example, integer: BOOST_HAS_INT128 BOOST_NO_INT64_T float: BOOST_FLOATx_C decimal: ? I think you should definitely generalize that: BOOST_HW_TYPE_AVAILABLE: only if TYPE is supported by the hardware (based on BOOST_HW_SIMD*), but not necessarily by the compiler or selected architecture BOOST_LIB_TYPE_AVAILABLE: TYPE is available from the c++library/compiler For example, float80_t: has HW support on x86 (BOOST_HW_FLOAT80_AVAILABLE is defined), but not on MSVC (BOOST_LIB_FLOAT80_AVAILABLE is not defined then) BOOST_SW_TYPE_AVAILABLE: there is an external emulation of TYPE For example, multiprecision A's complement fixed precision integer (TODO) or "half" by sourceforge Of course, this must be set manually. At least for int/float/decimal 8..512 this should be available. BOOST_HW_MACHINE_SIZE: the real word size of HW BOOST_ARCH_MACHINE_SIZE: the word size of the architecture For example, DOS on AMD Ryzen BOOST_HW_MACHINE_SIZE = 64 and BOOST_ARCH_MACHINE_SIZE = 16 multiprecision/float128_t: there are still many features missing most values in numeric_limits<float128_t> are not constexpr math::constants: i miss log2(2/e/pi/10) etc and i miss BOOST_COMP_VECTOR_EXTENSIONS_AVAILABLE if the compiler supports __attribute__(__vector_size__(...)) and BOOST_COMP_VECTOR_EXTENDED_EXTENSIONS_AVAILABLE if the compiler supports extendet vector extensions (currently only clang/llvm?) and BOOST_ARTIFICIAL __attribute__((artificial)) if supported thx

3 9

Boost serialization calling abort
by tim＠raisedbar.net 05 Feb '19

05 Feb '19

Hi, I'm experiencing the issue described at: https://svn.boost.org/trac10/ticket/13354 I' building using VS2017 and Boost 1.69.0 (I note that the article refers to 1.66.0). Does anybody know a fix for this, or am I best to revert back to 1.65.0? Best wishes. Tim Burgess Raised Bar Ltd. E: <mailto:tim@raisedbar.net> tim(a)raisedbar.net M: +44 (0)7989 486976

2 2

Latest Boost.Test version broke runtime_config::get
by David Sommer 05 Feb '19

05 Feb '19

Hi everyone, version 1.69 of boost.test broke the line *runtime_config::get<log_level>(runtime_config::btrt_log_level)* It works with static linking, however it breaks on dynamic linking. Error message is *boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level* In particular the following program fails: * #define BOOST_TEST_MODULE example #define BOOST_TEST_DYN_LINK #include <iostream> #include <boost/test/unit_test.hpp> #include <boost/test/unit_test_parameters.hpp> BOOST_AUTO_TEST_CASE(failDyn) { using namespace boost::unit_test; std::cout << runtime_config::get<log_level>( runtime_config::btrt_log_level ) << std::endl; }* if boost.test is linked dynamically. Best regards, David Sommer

1 0

Boost, MacOSx, and 64 bit
by S. L. Garwood 04 Feb '19

04 Feb '19

I have built boost 1.68 and 1.69 on MacOSX. When I try to use the binary components in a link, I get an error about not being able to find a version for x86_64. Does anyone have any tips? Is there a 64 but specific define for the build? Boost 1.66 from MacPorts seems to be fine but they don’t have 1.68 or 1.69 available (yet). I have a lot of software build using MacPorts so a migration to Homebrew is not really doable at this time.

2 2

Windows 64 bit Libraries.
by A Z 02 Feb '19

02 Feb '19

The boost library contains links to 64 bit Windows libraries on the bintray website, at https://dl.bintray.com/boostorg/release/1.66.0/binaries/. However, these libraries are only for versions of the Microsoft Visual C++ compiler, which do not have compatible bit profiles towards GNU G++, but more particularly with 64 bit Windows TDM. Is it possible for someone at BOOST to build and post libraries for Windows 64 bit TDM C++ for public and professional downloading and usage?

1 0

issue with property_tree/json_parser
by Harikrishna 29 Jan '19

29 Jan '19

Hi All, I am trying to use boost json_parser. I have included json_parser.hpp in my cpp file, I have not included any other code. But I am getting many compilation errors like error: 'boost::spirit::classic' has not been declared and In function void boost::property_tree::json_parser::read_json_internal(std::basic_istream<typename Ptree::key_type::value_type, std::char_traits<typename Ptree::key_type::value_type> >&, Ptree&, const std::string&): [exec] /usr/include/boost/property_tree/detail/json_parser_read.hpp:288: error: \u2018classic\u2019 is not a namespace-name Can you help me resolve this issue? -- Thanks Harikrishna

3 2

[Spirit] Looking for a little Qi guidance for Unicode parsing
by Michael Powell 28 Jan '19

28 Jan '19

Hello, I am turning a corner in my JSON parser. I support ASCII through and through, but now I want to support Unicode, apparently UTF-8, part of the JSON standard. From what I can tell, this is not the entire grammar, but just for Strings. Looking for a little guidance on how to approach that issue, the elements involved, etc. Such as, are we talking about C++ std::wstring? I have also seen std::u32string referenced in some forums. To begin with, it is a somewhat naive impression, would the characters not translate to unsigned char or char, but rather to std::wstring::value_type or std::u32string::value_type? Things like that come to mind approaching the issue. Additionally, how to otherwise handle symbol tables such as escape characters, i.e. from: struct escapes_t : qi::symbols<char, char> { escapes_t() { this->add("\\b", '\b') ("\\f", '\f') ("\\n", '\n') ("\\r", '\r') ("\\t", '\t') ("\\v", '\v') ("\\\\", '\\') ("\\/", '/') ("\\'", '\'') ("\\\"", '"') ; } } char_esc; And on from there. Thanks! Best regards, Michael W Powell

2 1

ASIO: Writing Composed Operations
by Cristian Morales Vega 26 Jan '19

26 Jan '19

Hi, I was looking at https://www.boost.org/doc/libs/develop/libs/beast/doc/html/beast/using_io/w… and came up with a question I can't answer: In https://github.com/boostorg/beast/blob/develop/example/echo-op/echo_op.cpp#… why does it use the AsyncStream associated executor without even looking at the potentially different (right?) Handler associated executor? Regards.

3 13

Fwd: Help needed with include path
by David Aldrich 25 Jan '19

25 Jan '19

Hi I am using Boost on Ubuntu 18.04 LTS, which has boost 1.65.1 installed. I want to use boost 1.69, which I have installed on another server. I specify that remote boost path in my makefile and make compiles my source file with: g++ -c -Wall -m64 -I/net/simdata/OpenSourceLibs/Boost/rel-1.69.0/ -fpic -O3 SINRCalculation.cpp -o _gnuRelease/SINRCalculation.o Now that source file uses boost/multi_array.hpp. The above compiler command gives error: In file included from /usr/include/boost/multi_array.hpp:30:0, from SINRCalculation.cpp:25: /net/simdata/Hudson_OpenSourceLibs/Boost/rel-1.69.0/boost/type_traits.hpp:118:10: fatal error: boost/type_traits/is_nothrow_swappable.hpp: No such file or directory #include <boost/type_traits/is_nothrow_swappable.hpp> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. Now my copy of boost 1.69 does contain is_nothrow_swappable.hpp so, at first sight, that error is surprising. I think what is happening is the is_nothrow_swappable.hpp is being searched for on the system library path (boost 1.65 does not have that file), not the one I specified using -I. Am I correct? If so, how can I force the compiler to use the boost 1.69 path consistently for all paths?

3 2

Memory mapped files
by Simon Giddings 24 Jan '19

24 Jan '19

Good morning, We are developing a system which heavily uses memory mapped files. These files are initially created under a unix system, but will then be used in portable systems such as Android and iOS. We are having some problems loading memory mapped files created under Unix into Android. Is this scenario even possible ? Are the memory mapped files compatible between systems ? Hope you will be able to shed some light on this. Best regards Simon

5 10

C++Now 2019 Registration is Open
by Jon Kalb 24 Jan '19

24 Jan '19

Boosters, Registration for C++Nows 2019 (aka BoostCon) is now open: http://cppnow.org/announcements/2019/01/2019-registration-is-open/ Please help us to spread the word about this announcement. Thanks. Note that the Aspen Meadows Resort online registration link is also up on the lodging page. Because there will be another group in the hotel, we’ve been allocated fewer rooms this year. Please either reserve a room very soon or plan to stay at the Lamplighter or another hotel in town. See you in Aspen in May. Jon

1 0

[Format] Formatting some string chars not encoding to hex
by Michael Powell 22 Jan '19

22 Jan '19

Hello, I've got some characters that are not formatting to hex properly. They are not being interpreted correctly by the strongly typed Format. For instance, consider the format string: const char x = '$'; // also, '_', for instance const auto s = (boost::format("\\x%1$02x") % x).str(); I would expect this to encode to: "\\x24", however, instead this encodes to "\\x0$". I would expect '_' to encode: "\\x5f", however, this encodes to "\\x0_". In a few words, the encoding is "seeing" the char as a literal char instead of as an "integer". Although I could possibly trap for this as being the case, I do not think that I should. Thoughts? Format authors? Best regards, Michael Powell

2 2

Warnings from 1.69.0
by tim＠raisedbar.net 22 Jan '19

22 Jan '19

Hi, Whilst building my application using Visual Studio 2017 I get the following warnings that I wasn't getting prior to changing to 1.69.0: 1>c:\program files\boost\boost\pending\integer_log2.hpp(7): note: This header is deprecated. Use <boost/integer/integer_log2.hpp> instead. The identified header is not referenced in my own code, but is being included by the Boost logging code. Can anybody advise me as to my best way of dealing with this situation, please, as I'm trying for a warning-free build. Best wishes. Tim Burgess Raised Bar Ltd. E: <mailto:tim@raisedbar.net> tim(a)raisedbar.net M: +44 (0)7989 486976

2 1

[Spirit Qi] Failed to parse the following fixed format double
by Michael Powell 19 Jan '19

19 Jan '19

Hello, We've been here before, but it is still a problem. I formatted this one using Boost.Format, "%1$.20f", especially dealing with 64-bit floating point values: "-6454866677007257221799838306103363329054216765979693126687924767750184064408021645577150612734391912932504859271476290909819606665305867922002041825515395649967939044362235953753132737391831714484437364695236622971838510661738713863719312223765488747173369566663518205119012003640541309414736378162701139968.00000000000000000000" Grammar is defined: numeric_sign %= ( ('-' >> attr(numeric_sign_minus)) | ('+' >> attr(numeric_sign_plus)) ) ; float_lit %= real_parser<float_t, strict_ureal_policies<float_t>>{}; floating_point %= -numeric_sign >> float_lit; With rules defined as: qi::rule<iterator_type, numeric_sign_t()> numeric_sign; qi::rule<iterator_type, float_t()> float_lit; qi::rule<iterator_type, floating_point_number_t()> floating_point; Where float_t is a defined part of the AST: using float_t = double; And floating_point maps to the floating_point_number_t, basically mapping the Sign and Value. Seems like we've been here before with inadequate response, however, reading the Boost documentation, I do not see any reason any Qi should be rejecting this value: https://www.boost.org/doc/libs/1_69_0/libs/spirit/doc/html/spirit/qi/refere… Particularly the RealPolicies: sign = lit('+') | '-' ; nan = -lit("1.0#") >> no_case["nan"] >> -('(' >> *(char_ - ')') >> ')') ; inf = no_case[lit("inf") >> -lit("inity")] ; floating_literal = -sign >> ( nan | inf | fractional_constant >> -exponent_part | +digit >> exponent_part ) ; fractional_constant = *digit >> '.' >> +digit | +digit >> -lit('.') ; exponent_part = (lit('e') | 'E') >> -sign >> +digit ; Although the concern I have is that the RealPolicy grammar defined above is not implemented as Qi Rules, per se, but rather brute force. In other words, error prone in the ways that a brute force approach is error prone. Best regards, Michael Powell

1 2

[Format] How to format floating point values
by Michael Powell 19 Jan '19

19 Jan '19

Hello, How do I format floating point values, either double or float? I want to specify things like the precision during the formatting, i.e. how many digits to include in the fractional digits, and so forth. Currently, I am using this, for instance: General: "%1$g" Fixed: "%1$f" Scientific: "%1$e" or "%1$E" (depending on whether lower or upper case, respectively) Thanks! Best regards, Michael Powell

2 2

is boost::container::static_vector header only library?
by Sivaram L 19 Jan '19

19 Jan '19

I am working on a embedded systems project, where we are exploring options to use STL containers without dynamic memory allocation, except std::array we cannot use any of the STL, boost container has static_vector for that, on browsing the code,we found that the library has to be built, is there a way to use this library as header only library?

5 4

Atomic boost::filesystem::rename
by Lars 15 Jan '19

15 Jan '19

Hello, What is the most "atomic" way to move two files from a local disk to a server location? The meaning of atomic in this context means that either both files are moved or both files stay in original location. No intermediate files should be present once operation is finished. The two files are located in different directories; /root/file_a /root/data/file_b The solution must support both Windows and Linux environment. It appears boost::filesystem::rename(..) uses Win32 API MoveFileExW for the Windows implementation. The documentation for MoveFileExW states; "If the file is to be moved to a different volume, the function simulates the move by using the CopyFile and DeleteFile functions. If the file is successfully copied to a different volume and the original file is unable to be deleted, the function succeeds leaving the source file intact." This means boost::filesystem::rename(..) could potentially just perform a file copy which is undesirable behaviour. Our understanding is that Boost filesystem does not contain ACL permission support [1] which make it difficult to check privileges prior to performing moves. Appreciate any input on the matter. Using C++14 and Boost. [1] - https://lists.boost.org/boost-users/2018/12/89232.php

2 1

Re: [Boost-users] Server application won't bind to ports on IP address other than my internal ones
by Osman Zakir 15 Jan '19

15 Jan '19

I just tried commenting out the POST request handling code and the client_session stuff, and then tried to run it with my external IP, but the same error from bind() came up saying that the requested address is not valid in its context. I also tried using the wildcard IP 0.0.0.0 as the command line argument for the address when running the server and entering my external IP into the browser address bar, but I still couldn't visit the app in the browser (can't get to it either way). The problem is probably in the server code, and is because of Asio (probably). I need some advice on how best to confirm this and troubleshoot the problem. Thanks in advance.

8 33

C++Now 2019 Submission Deadline
by Jon Kalb 14 Jan '19

14 Jan '19

The deadline for submitting to C++Now 2019 is just a few days away. If you’ve been thinking of submitting, please do not delay: http://cppnow.org/announcements/2018/12/2019-call-for-submissions/ <http://cppnow.org/announcements/2018/12/2019-call-for-submissions/> Thanks. Jon

1 0

Boost.Optional error should be a warning
by Michael Powell 14 Jan '19

14 Jan '19

Hello, I am using Boost.Optional, and, while I do want to "include it in an output", the library which I am doing so has another mechanism to do so. Translation, for Optional purposes, the following assertion should be a warning, IMO, and not an error: BOOST_STATIC_ASSERT_MSG(sizeof(CharType) == 0, "If you want to output boost::optional, include header <boost/optional/optional_io.hpp>"); Cheers, Michael Powell

2 4

Boost.Units: Is it possible to convert on assignment without casting?
by Carel Combrink 14 Jan '19

14 Jan '19

Hi. I have two unit quantities defined as follow: static const auto Hz = boost::units::si::hertz; static const auto KHz = boost::units::si::kilo * Hz; using Hertz = boost::units::quantity<decltype( Hz ), double>; using Kilohertz = boost::units::quantity<decltype( KHz ), double>; Assigning one type to another does not compile: Kilohertz freqKhz = Kilohertz::from_value( 1.234 ); Hertz freqHz = freqKhz; >>> error: conversion from 'Kilohertz {aka boost::units::quantity<...>, double>}' to non-scalar type 'Hertz {aka boost::units::quantity<...>, double>}' requested [1] Is this possible, should it be enabled or is it not supported? I am using boost 01.67, Mingw 5.3 and MSVC 2017 (C++14) The following options work as expected: Hertz freq1 = static_cast<Hertz>( freqKhz ); Hertz freq2 = Hertz( freqKhz ); But this adds a bit more code to maintain and keep in sync, one thing one tries to avoid when using the library since one needs to keep the LHS and the RHS of the opertor= in sync. PS: The chrono library allows this type of conversion given there is no information lost (but for double as storage types this should not be the case) std::chrono::seconds sec = std::chrono::seconds { 10 }; std::chrono::nanoseconds nsec = sec; [1] https://gcc.godbolt.org/z/0sTHQQ Regards, Carel

3 2

Forcing boost to build zlib
by Simon Michalke 12 Jan '19

12 Jan '19

Hello, what is needed to force bjam to build zlib? Is the zlib.h enough? Also is there a way to make bjam fail compiling if I set "NO_ZLIB=0" and it does not find the zlib.h / source? It is really inconvenient that bjam silently switches off zlib without any error or warning why zlib is not being build. My commands are: ./bootstrap.sh --without-libraries=python --prefix=/home/simon/code/cfs/release_mingw_openblas/cfsdeps/boost/install --with-toolset=gcc --without-libraries=context --without-libraries=coroutine target-os=windows architecture=x86 address-model=64 release and ./b2 target-os=windows architecture=x86 address-model=64 release --user-config=user-config.jam toolset=gcc-mingw -s ZLIB_BINARY=\"/home/simon/code/cfs/release_mingw_openblas/lib64/MINGW_X86_64/libzlibstatic.a\" -s ZLIB_INCLUDE=\"/home/simon/code/cfs/release_mingw_openblas/include\" -s NO_ZLIB=0 threading=multi install (this is cross compiling, but I have the same problem building for Linux) Regards, Simon

4 6

Possible Boost.Variant issue with JSON AST
by Michael Powell 11 Jan '19

11 Jan '19

Hello, I've got an AST I am developing to support JSON parsing using the latest VC++ (15.9.5), however, I am having difficulty persuading the compiler with my forward declarations. i.e. 1>d:\dev\boost.org\boost_1_69_0\boost\mpl\sizeof.hpp(27): error C2027: use of undefined type 'kingdom::json::object_t' In terms of JSON AST modeling, the rub appears to be in a couple of places: defining the JSON AST Array, and making the JSON AST Object available to Value. Re: semantic terminology, Value is interchangeable with Element, in view of the JSON grammar. Here's my attempt at a flattened single source example: https://wandbox.org/permlink/83c3VXZ4W1DHoEBc I seem to recall there being future issues with C++ forward declarations, but this seems to be like a bad language design decision to restrict this, especially in light of this kind of approach. I'm not sure how better to sort this out. At minimum, at least Value needs a forward declaration depending on how I arrange my headers, includes, etc. But then I still run into Value forward declaration undefined type issues. I'm not sure it's as much a language issue as much as it is possible a Boost.Variant issue, per se. Suggestions? Thanks! Michael Powell

3 5

[Spirit] Incompatible skipper type?
by Michael Powell 10 Jan '19

10 Jan '19

Hello, I'm a bit confused here, not sure what this means: Severity Code Description Project File Line Suppression State Error C2664 'bool boost::function4<R,T0,T1,T2,T3>::operator ()(T0,T1,T2,T3) const': cannot convert argument 4 from 'const Skipper' to 'T3' Kingdom.Json.Parser.Tests d:\dev\boost.org\boost_1_69_0\boost\spirit\home\qi\nonterminal\rule.hpp 304 // If you are seeing a compilation error here stating that the // fourth parameter can't be converted to a required target type // then you are probably trying to use a rule or a grammar with // an incompatible skipper type. if (f(first, last, context, skipper)) {} Incompatible where? How? Requires clarification please. The default Skipper type, which I am using at the moment, is boost::spirit::qi::space_type. I aim to use the proven Comment Skipper that I leveraged in a previous iteration eventually, but I expect that compilation should work with the simple space type at least. Because as far as I can determine all of the rules in my Grammar have the same Skipper type. struct json_grammar : qi::grammar<It, value_t(), Skipper> { using iterator_type = It; using skipper_type = Skipper; using char_rule_type = qi::rule<It, char()>; json_grammar() : json_grammar::base_type(value_) { // ... } private: struct escapes_t : qi::symbols<char, char> { escapes_t() { this->add("\\b", '\b') ("\\f", '\f') ("\\n", '\n') ("\\r", '\r') ("\\t", '\t') ("\\v", '\v') ("\\\\", '\\') ("\\/", '/') ("\\'", '\'') ("\\\"", '"') ; } } char_esc; //qi::rule<iterator_type> line_cont; char_rule_type hex_esc, unicode_esc; qi::rule<iterator_type, str_t()> quot_str, tick_str, str_lit; qi::rule<iterator_type, std::vector<value_t>(), skipper_type> array_; qi::rule<iterator_type, boost::tuple<key_t, value_t>(), skipper_type> member; qi::rule<iterator_type, std::vector<boost::tuple<key_t, value_t>>(), skipper_type> object_; qi::rule<iterator_type, key_t(), skipper_type> member_key; qi::rule<iterator_type, value_t(), skipper_type> value_; qi::rule<iterator_type, numeric_sign_t(), skipper_type> numeric_sign; qi::rule<iterator_type, float_t(), skipper_type> float_lit; qi::rule<iterator_type, floating_point_number_t(), skipper_type> floating_point; qi::rule<iterator_type, int_t(), skipper_type> hex_int, oct_int, dec_int, int_lit; qi::rule<iterator_type, integer_number_t(), skipper_type> integer; qi::rule<iterator_type, boolean_t(), skipper_type> bool_lit; qi::rule<iterator_type, null_t(), skipper_type> null_lit; }; Best regards, Michael Powell

1 2

Server application won't bind to ports on IP address other than my internal ones
by Osman Zakir 10 Jan '19

10 Jan '19

I have a server application that I wrote. It currently 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 the one whose source code is on GitHub here<https://github.com/DragonOsman/currency_converter/>. I used the asynchronous server and client examples from the Boost.Beast GitHub repository for the networking code (this link for the server: link<https://github.com/boostorg/beast/blob/develop/example/http/server/async/ht…>; this link for the client: link<https://github.com/boostorg/beast/blob/develop/example/http/client/async/ht…>). But when I run it using my external IP address, I get the error documented on lines 471 and 472: // Bind to the server address acceptor_.bind(endpoint, ec); if (ec) { std::cerr << "Lines 471 and 472:\n"; fail(ec, "bind"); return; } with the error itself being: bind: The requested address is not valid in its context And I've heard from whoever has tried to download and then run the server application that it just closes on its own after a while. I also tried to deploy it to Heroku as a Docker container before and found that it wouldn't bind to any ports they tried to bind it to and they had to kill it with SIGKILL. I tried to look for the code for bind in Asio, but I don't really know where to look. Some help on that would also be appreciated. I might be able to figure it from reading that code. If I can't, I'll come back here.

5 7

C++/CLI and >=VS2015
by liong＠gmx.ch 09 Jan '19

09 Jan '19

6 5

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

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