- Boost-users - lists.boost.org

version 1.78.0 compile failed on centos 7 with compiler clang
by David Frank 15 Sep '22

15 Sep '22

error message: boost/spirit/home/classic/phoenix/closures.hpp:274:30: error: default initialization of an object of const type 'const index<0>' without a user-provided default constructor Thanks.

1 0

version 1.78.0 compile failed on centos 7
by David Frank 15 Sep '22

15 Sep '22

error message: boost/spirit/home/classic/phoenix/closures.hpp:274:30: error: default initialization of an object of const type 'const index<0>' without a user-provided default constructor Thanks.

1 0

version 1.78.0 compile failed on centos 7
by David Frank 15 Sep '22

15 Sep '22

error message: boost/spirit/home/classic/phoenix/closures.hpp:274:30: error: default initialization of an object of const type 'const index<0>' without a user-provided default constructor On Saturday, September 3, 2022 at 08:48:54 PM PDT, David Frank <david_frank95(a)yahoo.com> wrote: I'm currently using version 60, it failed to compile with openssl 3.0.5. So I need to upgrade to a version that works. Thanks.

1 0

Redefined macro on Solaris, OmniOS, and SmartOS
by Camden Narzt 11 Sep '22

11 Sep '22

Building code (on Solaris, OmniOS, and SmartOS, using gcc) which includes boost, produces warnings such as the following: In file included from src/boost/config/platform/solaris.hpp:17:0, from src/boost/config.hpp:57, from src/boost/cstdint.hpp:36, from src/code_that_includes_boost.cpp:43: src/boost/config/posix_features.hpp:27:0: warning: "BOOST_HAS_STDINT_H" redefined [enabled by default] # define BOOST_HAS_STDINT_H ^ Not a big deal, but figured I’d report it in case it hadn’t been reported yet.

1 0

which version works with openssl 3.0.5?
by David Frank 04 Sep '22

04 Sep '22

I'm currently using version 60, it failed to compile with openssl 3.0.5. So I need to upgrade to a version that works. Thanks.

2 1

How to build Boost with static ICU via Msys2 / mingw-w64 / gcc on Windows?
by crillion＠tiscali.it 03 Sep '22

03 Sep '22

Hello, I'm trying to build boost 1.80 on windows 10 with the icu provided with msys2 (my goal in particular is that boost locale will build using my installed version of icu). My build platform is msys2 with mingw-w64 / gcc 12.2. By launching pacman -Q on the msys2-msys shell I have seen that I have icu 71.1-2 : (...) glib2 2.72.2-2 gmp 6.2.1-2 gnupg 2.2.36-1 grep 1~3.0-3 gzip 1.12-2 heimdal-libs 7.7.0-3 icu 71.1-2 inetutils 1.9.4-5 info 6.8-4 less 590-2 (...) on my system I have msys2 installed in the following folder C:programsmsys64 and in C:programsmsys64mingw64 there are the following folders : bin etc include lib libexec sbin share ssl var x86_64-w64-mingw32 in the lib folder I have found that there are lib files like libicuio.a, libicudt.a and libicutest.a . I extracted boost and then I've given the usual sequence of commands from the normal cmd shell of windows : for creating b2 : bootstrap.bat gcc for the actual build of boost, I've made the following attempts : b2 --toolset=gcc address-model=64 -sICU_PATH=C:programsmsys64mingw64 b2 --toolset=gcc address-model=64 include=C:programsmsys64mingw64include library-path=C:programsmsys64mingw64lib b2 --toolset=gcc address-model=64 -sICU_PATH=C:programsmsys64mingw64 include=C:programsmsys64mingw64include library-path=C:programsmsys64mingw64lib but none of these works : the build process always writes in its initial phase : (...) has_lzma_cputhreads builds : yes [2] cxx11_decltype : yes [2] cxx11_basic_alignas : yes [2] iconv (libc) : no [2] iconv (separate) : yes [2] icu : no [2] icu (lib64) : no [2] native atomic int32 supported : yes [2] has message compiler : no [2] native syslog supported : no [2] (...) what am I supposed to do to let b2 see the ICU lib files that I have in my msys2 distribution ? Thanks, Marco Voucher MISE per P.IVA e PMI: fino a 2500€ per la Banda Ultralarga. https://casa.tiscali.it/promo/?u=https://promozioni.tiscali.it/voucher_busi…..

1 0

suspendable/resumable/prioritizable task dispatcher
by chris-boostusers＠stankevitz.com 31 Aug '22

31 Aug '22

Hi, Unfortunately I don't have the vocabulary needed to ask this question, but hopefully I'll learn it here. Does Boost have something that will help me with this problem: I have a list of CPU-bound tasks I need to perform. I'll list two of them here: a) compute first zillion digits of pi (low priority) b) add two plus two (high priority) I co_spawn (a). Later, while (a) is running, I co_spawn (b). (a) will be suspended at a "co_suspension_point" so that (b) can take over. Of course when (b) completes, (a) will resume. For bonus points, it will support multiple threads (probably easy) and a task's priority can change over time (probably hard). Thank you! Chris PS: I was recently blown away by the coroutine capability of ASIO: Talking Async Ep1: Why C++20 is the Awesomest Language for Network Programming https://www.youtube.com/watch?v=icgnqFM-aY4

3 3

memory fault when passing var to a coroutine
by Piotr Gosławski 23 Aug '22

23 Aug '22

Hello, Using GCC 10.1 and Boost 1.77 I get a mem fault when executing the following code: #include <iostream> #include <boost/asio.hpp> #include <boost/asio/awaitable.hpp> struct TestStruct { std::string strField; }; boost::asio::awaitable<bool> TestFunction(TestStruct param) { std::cout << param.strField << std::endl; co_return true; } boost::asio::awaitable<void> TestCoroutine() { // This causes mem issue co_await TestFunction(TestStruct{"some string"}); } int main() { boost::asio::io_context io_context; boost::asio::co_spawn( io_context, []() { return TestCoroutine(); }, boost::asio::detached); io_context.run(); return 0; } Also tested with GCC 12.1 and Boost 1.79 - the result is the same ( https://godbolt.org/z/69MKbz7qE) Works if I use a temp variable: boost::asio::awaitable<void> TestCoroutine() { auto testStruct = TestStruct{"some string"}; co_await TestFunction(testStruct); } Or if I add a constructor to test struct: struct TestStruct { explicit TestStruct(const std::string& str) : strField(str) {} std::string strField; }; boost::asio::awaitable<void> TestCoroutine() { co_await TestFunction(TestStruct("some string")); } Is there any coroutines rule that I am violating here? If yes - is there any compiler option I can use to get a warning / error message? Full code with cmake can be found here: https://github.com/piotrgoslawski/mem_issue Thank you

1 0

re：question about compile the boost head file.
by zyx_xzy＠sina.com 23 Aug '22

23 Aug '22

Respeced Mr.Emil, Thank you for your kindly reply. >I can't reproduce this with msvc versions available on godbolt: >https://godbolt.org/z/E8vYWTPf6 Exactly on godbolt,the compilers work well. I test this by myself. Once again, I change to the Microsoft Visual Studio Community 2019 ver. 16.11.18. And compile the program ,the error still exist. >Can you provide a complete error log, including source file and line of the >error? soruce file:info.hppsource code line no:145soruce code:error_info_container_impl * c=new error_info_container_impl;error log:C2259 “boost::exception_detail::error_info_container_impl”: cannot instantiate abstract class, test_boost D:\boost_1_79_0\boost\exception\info.hpp 145 Best regards, zhiyong

2 1

question about compile the boost head file.
by zyx_xzy＠sina.com 20 Aug '22

20 Aug '22

hi anybody, I meet a problem when I try to compile the following program. #include <boost\exception\info.hpp> void main() { return; } The compile environment is Microsoft Visual Studio Community 2022 (64 位) - ver. 17.2.6.Compile error information is that C2259 “boost::exception_detail::error_info_container_impl”: cannot instantiate abstract class.I try many Boost versions,e.g.,boost 79,boost 65,boost64,boost60. They all give errors. Anybody can give me some suggestions? Best regards, zhiyong --------------------------------

2 1