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

ASIO openSSL 3 support
by Ofer Lent 03 Jan '23

03 Jan '23

Hi, https://www.boost.org/users/history/version_1_80_0.html, "Asio" section, states: "Fixed compatibility with OpenSSL 3.0.4 and later." However, API-s which were deprecated in openSSL 3 still exist in boost_1_80_0.tar.gz<https://boostorg.jfrog.io/artifactory/main/release/1.80.0/source/boost_1_80…> --> boost/asio/ssl/impl/context.ipp: · RSA_free · DH_free · d2i_RSAPrivateKey_bio · PEM_read_bio_RSAPrivateKey · SSL_CTX_use_RSAPrivateKey · SSL_CTX_use_RSAPrivateKey_file · PEM_read_bio_DHparams Is there a plan to update them? BTW - It is possible to build an application with these deprecated API-s by using CFLAGS += -Wno-deprecated-declarations, but in my understanding it is not acceptable for FIPS compliance. Thanks! ------------------------------------------- This message is confidential. If you believe you received this message in error, please inform the sender and delete this message and all attachments.

2 1

receive handler priority
by Alexander Carôt 28 Dec '22

28 Dec '22

Hello all, I have a classical receive handling structure for an asynchronous UDP socket: void receiver::receive(){ mySocket->async_receive_from( boost::asio::buffer(input, maxInputLength), senderEndpoint, boost::bind(&receiver::handleReceiveFrom, this, boost::asio::placeholders::error, boost::asio::placeholders::bytes_transferred)); } void receiver::handleReceiveFrom(const boost::system::error_code &error, size_t bytes_recvd) { // SPECIFIC CODE HERE AND FINAK CALL OF RECEIVE FUNCTION this->receive(); } Besides this my app works with several realtime threads I have assigned maximum priority to via: pthread_t threadID = (pthread_t) sendThread.native_handle(); struct sched_param param; int policy = SCHED_FIFO; int max = sched_get_priority_max(policy); param.sched_priority = max; pthread_setschedparam(threadID, policy, &param); Now I wonder in how far these realtime threads can have an impact on the performance of my receiver process: So far I assumed that the receiver handle code is executed immediately when a packet arrives at the NIC but I am not sure if other realtime threads might possibly delay this process when scheduled first. In other words: If we think of the receiver handling process as a thread that is triggered by incoming packets does this thread also have realtime capabilities that can suffer from competing processes ? Thanks in advance for clarification, best Alex -- http://www.carot.de Email : Alexander(a)Carot.de Tel.: +49 (0)177 5719797

2 2

Abwesenheitsnachricht: boost::detail::spinlock problem
by Sören Textor 21 Dec '22

21 Dec '22

Derzeit bin ich nicht im Hause Ihre E-Mail wird nicht weitergeleitet. In dringenden Fällen bitte support(a)ditec-gmbh.de oder Telefonhotline +49-6221-31698-110 oder die Zentrale +49-6221-31698-0 kontaktieren. Mit freundlichen Grüßen Dr. Sören Textor ----------------------------------------------- DiTEC Dr. Siegfried Kahlich & Dierk Langer GmbH Im Breitspiel 19 | 69126 Heidelberg | Germany Handelsregister | Mannheim | HRB 341229 Dieses Dokument ist vertraulich zu behandeln. Die Weitergabe, sowie Vervielfältigung, Verwertung und Mitteilung seines Inhalts ist nur mit unserer ausdrücklichen Genehmigung gestattet. Alle Rechte vorbehalten, insbesondere für den Fall der Schutzrechtsanmeldung. This document has to be treated confidentially. Its contents are not to be passed on, duplicated, exploited or disclosed without our express permission. All rights reserved, especially the right to apply for protective rights.

1 0

boost::detail::spinlock problem
by Cliff Diamond 21 Dec '22

21 Dec '22

Hi I'm using boost::detail::spinlock (boost-1.81) in code that compiles on both Visual Studio and gcc. I've hit a problem on the gcc build where the underlying spinlock member (v_) in spinlock_gcc_atomic.hpp isn't an atomic variable and isn't explicitly initialised (BOOST_DETAIL_SPINLOCK_INIT is defined, but there's no initializer and no constructor). v_ is declared as a non-atomic unsigned char and atomic operations use gcc intrinsics in that file. So v_ needs to be explicitly initialized to 0. When the lock method is called, it just spins as a result. This may be work-in-progress or am I misunderstanding? It seems such a glaring omission. The STL version of the spinlock uses std::atomic which does initialize v_ because it's wrapped up in the atomic template. Also there is a scoped_lock nested class within the boost spinlock. Why have an additional lock guard? Surely std::scoped_lock should be sufficient (or is it there just for testing - if so please comment it). I can overcome the problem (without modifying spinlock_gcc_atomic.hpp) by trying to acquire the lock when I create it and releasing it regardless. Is this a bug in that file? Thanks Cliff

1 0

Boost IOStreams with CMake (CPMAddPackage) and Windows
by Richard Haney 17 Dec '22

17 Dec '22

Good afternoon, Hello everyone, I am new to this forum and new to *Boost* and *CMake* but eager to learn. So please forgive if this is a dumb question, but I am new to *Boost* and *CMake*. I have had success using *Boost.Iostreams* with Linux OS and CMake using *CPMPackageAdd* call for *boost_iostreams* library using compression and decompression with the following C++ code (the exact line of code that generates the error is shown below): #include <boost/iostreams/device/array.hpp> #include <boost/iostreams/device/back_inserter.hpp> #include <boost/iostreams/filtering_stream.hpp> #include <boost/iostreams/filter/zlib.hpp> #include <vector> #include <string> #include <iostream> #include <cstdlib> using namespace boost::iostreams; int main(int argc, char *argv[]) { // --------------------------------- // - COMPRESS DATA - // --------------------------------- std::vector<char> v; back_insert_device<std::vector<char>> snk{v}; filtering_ostream os; os.push(zlib_compressor{}); // This results in the Windows error zlib os.push(snk); os << "Boost" << std::flush; os.pop(); // --------------------------------- // - DECOMPRESS DATA - // --------------------------------- array_source src{v.data(), v.size()}; filtering_istream is; is.push(zlib_decompressor{}); is.push(src); std::string s; is >> s; std::cout << s << '\n'; return EXIT_SUCCESS; } However, when I try to use the same code on a Windows machine with MSVC compiler it generates errors explaining that* boost::iostreams::zlib is undefined *during linking. I am using *CMakeLists.txt* and would like to know if I can use *CMake* to properly build/compile for both Windows OS and Linux such that I can use the boost iostreams library with maybe an option in the *CPMAddPackage* call (maybe?). Is this possible? Can anyone point me in the correct direction with some simple example(s) if possible or links to existing solutions/hints to this same issue? I appreciate any assistance with this. Thank you for your time.

1 0

[release] Boost 1.81.0
by Marshall Clow 14 Dec '22

14 Dec '22

Release 1.81.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains one new library and numerous enhancements and bug fixes for existing libraries. * URL: A library for parsing, modifying, and printing URLs using only C++11, from Vinnie Falco and Alan de Freitas. For details, including download links, see <http://www.boost.org/users/news/version_1.81.0> You can also download directly from: <https://boostorg.jfrog.io/artifactory/main/release/1.81.0/> To install this release on your system, see <http://www.boost.org/doc/libs/release/more/getting_started/index.html> Thanks to everyone who participated in this release. -- The Boost Release Team Marshall Clow, Glen Fernandes, Michael Caisse

2 1

missing relaxed constexpr macros
by Gero Peterhoff 09 Dec '22

09 Dec '22

Hi John, i miss these for C++17/20/23 in boost/config. Can you retrofit this? thx Gero It could look like this: see https://en.cppreference.com/w/cpp/feature_test#__cpp_constexpr #if (__cpp_constexpr < 201703L) #define BOOST_NO_CXX17_CONSTEXPR #endif #if defined(BOOST_NO_CXX17_CONSTEXPR) #define BOOST_CXX17_CONSTEXPR #else #define BOOST_CXX17_CONSTEXPR constexpr #endif #if (__cpp_constexpr < 202002L) #define BOOST_NO_CXX20_CONSTEXPR #endif #if defined(BOOST_NO_CXX20_CONSTEXPR) #define BOOST_CXX20_CONSTEXPR #else #define BOOST_CXX20_CONSTEXPR constexpr #endif #if (__cpp_constexpr < 202207L) #define BOOST_NO_CXX23_CONSTEXPR #endif #if defined(BOOST_NO_CXX23_CONSTEXPR) #define BOOST_CXX23_CONSTEXPR #else #define BOOST_CXX23_CONSTEXPR constexpr #endif

1 0

Does Boost.Multiprecision have a forwards declaration header?
by Ivan Matek 04 Dec '22

04 Dec '22

I presume not since I could not find it in docs, but decided to double check. My motivation is that I would like to limit heavy includes in my header(since intrinsics for avx512 files are 20k+ LOC on my system), but I would still like to use proper types in signature of my functions (since none of them take .args by value fwd declarations would be enough). So I was hoping for something like iosfwd. If it matters what part of library I am using: cpp_int.hpp P.S. I checked if telling compiler that I do not want arch support for avx512 would help, but it looks like avx512 intrinsics headers are included regardless, and even if it was not I would still like to not get into issues when compiling for HW that supports avx512. :) regards, Ivan

2 2

[release] Boost 1.81.0 beta 1 released
by Marshall Clow 17 Nov '22

17 Nov '22

Boost release 1.81.0 beta 1 is now available at: https://boostorg.jfrog.io/artifactory/main/beta/1.81.0.beta1/source/ The SHA256 checksums are: 135f03965b50d05baae45f49e4b7f2f3c545ff956b4500342f8fb328b8207a90 boost_1_81_0_b1.tar.gz 736b041748d04c573d145613161cf2e54beb210c5511b67e6fac5510b82b6646 boost_1_81_0_b1.7z 941c568e7ac79aa448ac28c98a5ec391fd1317170953c487bcf977c6ee6061ce boost_1_81_0_b1.tar.bz2 c58d50acf58a98d4f5a7d891257d154efa50ca90312ca446586c7b4f9b7d3f14 boost_1_81_0_b1.zip Release notes (still need updates): https://www.boost.org/users/history/version_1_81_0.html Please try the beta and report any problems you encounter. Thanks to everyone who contributed to the release. -- Boost Release Team

1 0

Partial serialization of a program
by Markus Lavin 06 Nov '22

06 Nov '22

I have a simulator type program where I want to be able to save (and load) the current simulation state using Boost serialization. The program, as with most programs, consists of a part that is static during run-time and a part that is dynamic. Ideally I would like to serialize only the dynamic part but this however raises the following problem. If a serialized object in the dynamic part contains a pointer to a non-seralized object in the static part then how do I deal with that. Clearly the address cannot be serialized since it may change between builds and even between runs (ASLR). The program does contain a 'registry' though where all relevant static objects are registered with a unique identifier. So question is would it somehow be possible to have Boost serialization use this registry to serialize the unique identifier instead of trying to serialize the entire object when one of those pointers are serialized? As far as I can tell the documentation does not mention this situation and extensive web searching yields very little as well. Any advice appreciated! -Markus

3 4

Question about boost::multi_index emplace operations
by Pavel Vazharov 03 Nov '22

03 Nov '22

Hi there, Is there a way to emplace (key, value) in boost multi_index hashed index in such a way that the value is not moved/stolen if the key is already present? As far as I checked the implementation for emplace (and emplace_) the node is eagerly created and the key and the value are moved into the node and then the insertion operation takes place. If the insertion fails the node is destroyed but the outside value is lost/stolen in all cases. What I actually need is to create the value only if the key is not present, because the creation is expensive, and I'd like to avoid the find+emplace or insert empty value + modify call. (As far as I checked, the value can't be modified directly from the returned iterator because it's const and will need const_cast to work). I thought to use emplace with some machinery for lazy creation struct creator { operator value_type () { return ...; } // create the value lazily, on demand }; The creator is passed to emplace instead of the actual value. However, this doesn't help because the node is eagerly created and the above operator is always called. Thanks, Pavel.

2 4

Re: [Boost-users] Cannot open boost lib file when building CLI dll
by Michael Pogue 28 Oct '22

28 Oct '22

> > I am trying to build a CLR dll file in VS22 and dotnet 6.0 that references >> boost. When I build, I get the following error. >> LNK1104 cannot open file 'libboost_program_options-vc142-mt-x64-1_76.lib' >> >> - This file does exist. >> - I have restarted to make sure the file isn't locked. >> - I have tried building as 32 and 64 bit. >> - I have tried 3 different versions of boost >> >> The problem is reproduced by this project: >> https://github.com/MajorMajor0/boostRepro. >> Any help would be much appreciated. >> >

1 0

Norms methods
by General Magic - Teodora Bogdan 26 Oct '22

26 Oct '22

Hello, I was using the Boost library and I wanted to call the l2_norm() method from "boost/math/tools/norms.hpp", but is says that the namespace boost::math::tools doesn't contain l2_norm() method. When I looked into it, I saw that the namespaces at the beginning of the file were written"boost::math::tools" instead of "namespace boost { namespace math { namespace tools {...". Can this be fixed? Have a nice day, Teodora Bogdan CONFIDENTIALITY NOTICE: This e-mail and any attachments hereto may contain information that is privileged or confidential, and is intended for use only by the individual or entity to which it is addressed. Any disclosure, copying or distribution of the information by anyone else is strictly prohibited. If you have received this document in error, please notify us promptly by responding to this e-mail. DISCLAIMER: General Magic accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided, unless that information is subsequently confirmed in writing and duly signed on behalf of General Magic by an authorized officer. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of General Magic. No employee or agent is authorized to conclude any binding agreement on behalf of General Magic with another party by email without express written confirmation which is duly signed on behalf of General Magic by an authorized officer. Thank you.

3 3

Boost::serialization detection of Cxx Standard
by Georg Gast 14 Oct '22

14 Oct '22

Hi, I developed a patch and a test to serialize std::pmr::(w)strings in all 3 archive types. The test I set the requirement to <cxxstd>17. It works so far but when I compile the library for using it in my application the "hidden" functions behind "BOOST_NO_CXX17_MEMORY_RESOURCE" are not found by the linker as the define is set when the library is compiled. How to work around this? Bye Georg

2 2

Is there any official documentation on shutdown procedure for ASIO SSL socket?
by Ivan Matek 11 Oct '22

11 Oct '22

There is this SO answer https://stackoverflow.com/a/25703699/ with Vinnie comment from 8y ago that it should be added to documentation. :) I can not find anything in the documentation so I presume the documentation/example does not exist, but I decided to double check. regards, Ivan

3 2

Very slow destructors of binary_oarchive and filtering_streambuf
by boost.5nyej＠simplelogin.com 03 Oct '22

03 Oct '22

Hello, I just posted a question on StackOverflow, but I realised that this mailing list might be a better place. The link to the question is: https://stackoverflow.com/questions/73938656/very-slow-destructors-of-binar… Tl;dr; I have a code that serializes a big object by using binary_oarchive and filtering_bufstream. The writing on its own takes around 28 minutes, but the deconstructors of the mentioned classes take 37 and 36 minutes, respectively. It is very strange to me that they would take so much time to run, as the first deconstructor adds only 2KiB of data, and the second deconstructor doesn't change anything. Could you help me find the root cause of those execution times?

1 0

[serialisation] Strange "direct access" warning on OSX for basic_text_oprimitive
by Marco Craveiro 29 Sep '22

29 Sep '22

Hi Boost Users, First, a great thanks to the authors of the boost serialisation library, which I have used successfully across projects and has proven invaluable. Now to my problem. I have been investigating for a little while a strange warning I get when linking on OSX; the results of my investigation can be found here [1]. The TL; DR of it is as follows: my OSX debug build has a warning (indented for ease of reading): ld: warning: direct access in function 'boost::archive::basic_text_oprimitive< std::__1::basic_ostream<char, std::__1::char_traits<char> > >::~basic_text_oprimitive()' from file 'vcpkg_installed/x64-osx/debug/lib/libboost_serialization.a(basic_text_oprimitive.o)' to global weak symbol 'std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::endl<char, std::__1::char_traits<char> > (std::__1::basic_ostream<char, std::__1::char_traits<char> >&)' This warning is caused by a mismatch in visibility settings between my project and vcpkg's build of boost. However, as far as I can see, both projects are using "-fvisibility=default", meaning there should be no mismatch. Also, no other warnings show up but if I change the project settings I then get hundreds of warnings (again, for details see ticket). What I find even more puzzling is that I am using all three types of archives (Text, XML and Binary). Of these three, only Text produces this warning. As the problem is with the destructors, I did a quick inventory of the destructors to see how they differ: basic_xml_oarchive.hpp: [2] BOOST_ARCHIVE_OR_WARCHIVE_DECL ~basic_xml_oarchive() BOOST_OVERRIDE; basic_text_oarchive.hpp: [3] ~basic_text_oarchive() BOOST_OVERRIDE {} basic_binary_oarchive.hpp: [4] no destructor. So my question is, should text archive also have a BOOST_ARCHIVE_OR_WARCHIVE_DECL macro, and would that fix my warning? If so I can submit a PR. Many thanks for your time. Marco [1] https://github.com/Microsoft/vcpkg/issues/4497 [2] https://github.com/boostorg/serialization/blob/develop/include/boost/archiv… [3] https://github.com/boostorg/serialization/blob/develop/include/boost/archiv… [4] https://github.com/boostorg/serialization/blob/develop/include/boost/archiv… -- Marco Craveiro MD, Domain Driven Consulting blog: https://mcraveiro.github.io/index.html 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

Re: [Boost-users] [boost] [signals2][variant] inline warning with MSVC 2022
by Frank Mori Hess 22 Sep '22

22 Sep '22

On Thu, Sep 22, 2022 at 8:57 AM Peter Dimov <pdimov(a)gmail.com> wrote: > > That's complete nonsense. First, Microsoft invented __forceinline, so > making BOOST_FORCEINLINE be a no-op on the very compiler for which > the feature has been added would be ridiculous. Second, it does force > inlining, that's why it's called __forceinline. The whole point of the warning > is to warn about the rare cases where the compiler does not honor the > command; it exists because people want to know whether their "force > inline" orders are ignored. But no boost user wants to be warned about some internal implementation detail of a boost library. So every boost usage of BOOST_FORCEINLINE needs to add a #pragma warning(disable: 4714), awesome! Who is the maintainer of variant anyways? -- Frank

1 0

TSan error with boost::interprocess::message_queue on macOS ARM
by vl01＠jens-carl.de 22 Sep '22

22 Sep '22

Hello List, I'm using the boost::interprocess::message_queue in a project and to verify everything is working I created a test case. In that test case I'm sending and receiving data via threads. The test passes on Linux, Windows with no sanitizer and also with AddressSanitizer and ThreadSanitizer. I recently added Apple Silicon (M1) to the test matrix and now the test run with ThreadSanitizer enabled fails. Is boost::interprocess::message_queue thread-safe? Can the reported TSan error be an false-positive? If it that case, what test can I run to verify that? I looked at code of atomic_cas32() and it uses the legacy built-in __sync_val_compare_and_swap(). Can it be that that built-in isn't supported on ARM? Is there a newer built-in which should be used? The reported TSan error: -- snip ================== WARNING: ThreadSanitizer: data race (pid=4146) Atomic write of size 4 at 0x000104af4028 by thread T2: #0 __tsan_atomic32_compare_exchange_val <null>:81245684 (libclang_rt.tsan_osx_dynamic.dylib:arm64e+0x57854) #1 boost::interprocess::ipcdetail::atomic_cas32(unsigned int volatile*, unsigned int, unsigned int) atomic.hpp:581 (tsan_boost:arm64+0x100005b30) Previous read of size 4 at 0x000104af4028 by thread T1: #0 boost::interprocess::ipcdetail::spin_mutex::try_lock() mutex.hpp:100 (tsan_boost:arm64+0x100006eb0) #1 void boost::interprocess::ipcdetail::try_based_lock<boost::interprocess::ipcdetail::spin_mutex>(boost::interprocess::ipcdetail::spin_mutex&) common_algorithms.hpp:62 (tsan_boost:arm64+0x100006e28) SUMMARY: ThreadSanitizer: data race atomic.hpp:581 in boost::interprocess::ipcdetail::atomic_cas32(unsigned int volatile*, unsigned int, unsigned int) -- snap Here is a code example which demonstrates the test case -- snip #include <boost/interprocess/ipc/message_queue.hpp> #include <iostream> #include <vector> #include <thread> #include <memory> struct MessageQueueImpl { MessageQueueImpl() { boost::interprocess::permissions file_permissions; file_permissions.set_permissions(0660); queue = std::make_unique<boost::interprocess::message_queue>(boost::interprocess::create_only, "tsanqueue", 10, 15, file_permissions); } std::unique_ptr<boost::interprocess::message_queue> queue; }; class MessageQueue { public: MessageQueue() : m_impl(std::make_unique<MessageQueueImpl>()) {} void send(const std::vector<uint8_t>& buffer) { m_impl->queue->send(buffer.data(), buffer.size(), 0); } void receive(std::vector<uint8_t>& buffer) { boost::interprocess::message_queue::size_type received_size = 0; buffer.resize(m_impl->queue->get_max_msg_size()); uint32_t prio; m_impl->queue->receive(buffer.data(), buffer.size(), received_size, prio); buffer.resize(received_size); } private: std::unique_ptr<MessageQueueImpl> m_impl; }; int main() { auto uut = std::make_unique<MessageQueue>(); std::thread sender([&uut]{ for(uint8_t i = 0; i < 3; ++i) { const std::vector<uint8_t> send_buffer = {i}; uut->send(send_buffer); } }); std::thread receiver([&uut]{ for(uint8_t i = 0; i < 3; ++i) { std::vector<uint8_t> receive_buffer; uint32_t prio; uut->receive(receive_buffer); std::cout << "buffer received:\n"; for (const auto i : receive_buffer) { std::cout << i << '\n'; } } }); if(sender.joinable()) { sender.join(); } if(receiver.joinable()) { receiver.join(); } return 0; } -- snap Cheers, Jens

3 3

Re: [Boost-users] [boost] [signals2][variant] inline warning with MSVC 2022
by Frank Mori Hess 22 Sep '22

22 Sep '22

On Wed, Sep 21, 2022 at 12:32 PM Peter Dimov <pdimov(a)gmail.com> wrote: > > That's not very user friendly; maybe the user _wants_ the warning in his code, > and the above would disable it even if no Boost header that uses > BOOST_FORCEINLINE (and generates a warning) has been included. > Okay, then maybe BOOST_FORCEINLINE shouldn't be defined as __force_inline on compilers where it doesn't actually force inlining. If the compiler is just going to treat it as a suggestion, I don't see the point of boost headers using it and then suppressing the warning. -- Frank

1 0

[signals2][variant] inline warning with MSVC 2022
by Gavin Lambert 21 Sep '22

21 Sep '22

This may not be a new issue, as I'm trying to update a project from Boost 1.68 to 1.80 (big jump!), but in trying to compile I'm being hit with this lengthy warning (and this particular project is building with warnings as errors, so this is problematic): warning C4714: function 'class boost::variant<class boost::shared_ptr<void>,class boost::signals2::detail::foreign_void_shared_ptr> __cdecl boost::detail::variant::visitation_impl<struct boost::mpl::int_<0>,struct boost::detail::variant::visitation_impl_step<struct boost::mpl::l_iter<struct boost::mpl::l_item<struct boost::mpl::long_<3>,class boost::weak_ptr<class boost::signals2::detail::trackable_pointee>,struct boost::mpl::l_item<struct boost::mpl::long_<2>,class boost::weak_ptr<void>,struct boost::mpl::l_item<struct boost::mpl::long_<1>,class boost::signals2::detail::foreign_void_weak_ptr,struct boost::mpl::l_end> > > >,struct boost::mpl::l_iter<struct boost::mpl::l_end> >,class boost::detail::variant::invoke_visitor<class boost::signals2::detail::lock_weak_ptr_visitor const ,0>,void const *,struct boost::variant<class boost::weak_ptr<class boost::signals2::detail::trackable_pointee>,class boost::weak_ptr<void>,class boost::signals2::detail::foreign_void_weak_ptr>::has_fallback_type_>(int,int,class boost::detail::variant::invoke_visitor<class boost::signals2::detail::lock_weak_ptr_visitor const ,0> &,void const *,struct boost::mpl::bool_<0>,struct boost::variant<class boost::weak_ptr<class boost::signals2::detail::trackable_pointee>,class boost::weak_ptr<void>,class boost::signals2::detail::foreign_void_weak_ptr>::has_fallback_type_,struct boost::mpl::int_<0> *,struct boost::detail::variant::visitation_impl_step<struct boost::mpl::l_iter<struct boost::mpl::l_item<struct boost::mpl::long_<3>,class boost::weak_ptr<class boost::signals2::detail::trackable_pointee>,struct boost::mpl::l_item<struct boost::mpl::long_<2>,class boost::weak_ptr<void>,struct boost::mpl::l_item<struct boost::mpl::long_<1>,class boost::signals2::detail::foreign_void_weak_ptr,struct boost::mpl::l_end> > > >,struct boost::mpl::l_iter<struct boost::mpl::l_end> > *)' marked as __forceinline not inlined I'm not sure whether the Real Bug™ is in signals2 or in variant, but I don't think it's in any of my code since it doesn't name any of my types above that I can see. I tried the big stick of setting all of Boost to "external" (and set the external warning level to 0), but sadly this did not suppress the warning. Wrapping it in a #pragma suppression does hide the warning, which makes me sufficiently happy. But perhaps someone might be interested to poke at it?

2 2

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