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

[type_erasure] member function return any
by Mikhail Strelnikov 06 Mar '17

06 Mar '17

Hello! I want to return type_erasure::any from a member function of a struct adapted by that same any. How can I do this? #include <boost/type_erasure/any.hpp> #include <boost/type_erasure/callable.hpp> using my_any = boost::type_erasure::any< boost::mpl::vector< boost::type_erasure::copy_constructible<>, boost::type_erasure::assignable<>, boost::type_erasure::callable<? ? ?> > >; struct s { my_any operator()(my_any v) { return v; } }; int main() { my_any t = s{}; t = t(t); } Thanks.

2 1

[boost] Unbounded integers and shared memory
by Antony Polukhin 04 Mar '17

04 Mar '17

Hello, One of the ISO WG21 C++ Study Groups is investigating the usecases of shared memory usage with wide arithmetics (Boost.Interprocess, Boost.Multiprecision, in-house solutions?). Particularly interesting: * Are there users that store unbounded numbers in shared memory? * Will bounded integers satisfy need of those users? Informal glossary: * "unbounded numbers" - numbers (integral, relational, floating point and others) that can store and operate on any huge value by dynamically allocating memory as necessary to maintain a representation of operation results. * "bounded types" - Numbers (integral, relational, floating point and others) which bounds are specified in number of bytes/bits/words at compile time and that do not allocate memory. Please, response if you are one of such users. Great thanks in advance! -- Best regards, Antony Polukhin

1 0

[spirit-qi] [attr] Invalid static_cast error
by 含露月含露月 03 Mar '17

03 Mar '17

Hi, I try to generate a string using qi::attr, and the following is the code. #include <boost/spirit/include/qi.hpp> namespace qi = boost::spirit::qi; int main(){ // ok qi::rule<char const *, std::string()> world = qi::attr("world"); qi::rule<char const *, std::string()> rule = qi::eps > world; // error: invalid static_cast from type 'const char [6]' to type 'char' // qi::rule<char const *, std::string()> rule = qi::eps > qi::attr("world"); } Do I miss something or it is a bug? How can I fix it without using extra rules or semantic actions. Platform: win7 64bit Compiler: gcc 4.9.1 Boost 1.63 Since I typed on my phone, forgive me if there are errors. Best regards, Yuan Yao

1 0

error running boost book
by Clark Sims 02 Mar '17

02 Mar '17

I get the following error when I cd to BOOST_ROOT/doc and run ../bjam My ~/user-config.jam looks fine. I pasted it bellow the error. Does anyone know how to fix this? I have spent a great deal of time trying to fix this. It looks like the doxygen.jam in the boost_1_63_0/tools/build/src/tools directory does not like the syngax of the doxygen rule in ~/user-config.jam. ---------------------------------------------------------------------------------------------------------------------------------- Building the tti docs with automatic index generation disabled. Try building with --enable-index. /home/csims/boost_1_63_0/libs/dll/doc/Jamfile.v2:66: in modules.load *** argument error * rule doxygen ( target : sources + : requirements * : default-build * : usage-requirements * ) * called with: ( autodoc_shared_library_core : : <doxygen:param>HIDE_UNDOC_MEMBERS=YES <doxygen:param>HIDE_UNDOC_CLASSES=YES <doxygen:param>HIDE_SCOPE_NAMES=YES <doxygen:param>EXTRACT_ALL=NO <doxygen:param>EXTRACT_PRIVATE=NO <doxygen:param>BUILTIN_STL_SUPPORT=YES <doxygen:param>ENABLE_PREPROCESSING=YES <doxygen:param>MACRO_EXPANSION=YES <doxygen:param>ALIASES= \ "forcedlink{1}=\xmlonly<link linkend='boost.dll.\1'>boost::dll::\1</link>\endxmlonly" \ "forcedmacrolink{1}=\xmlonly<link linkend='\1'>\1</link>\endxmlonly" <doxygen:param>PREDEFINED= \ "BOOST_RV_REF(T)=T&&" \ "BOOST_RV_REF(shared_library)=shared_library&&" \ "BOOST_COPY_ASSIGN_REF(shared_library)=const shared_library&" \ "BOOST_MOVABLE_BUT_NOT_COPYABLE(shared_library)= \ shared_library(const shared_library&) = delete; \ shared_library& operator=(const shared_library&) = delete; " \ "BOOST_DLL_IMPORT_RESULT_TYPE=result_type" \ "BOOST_DLL_MANGLED_IMPORT_RESULT_TYPE=result_type" \ "BOOST_EXPLICIT_OPERATOR_BOOL()=explicit operator bool() const noexcept;" \ "BOOST_DLL_DOXYGEN" <xsl:param>boost.doxygen.reftitle=Shared Library Reference ) * missing argument sources /home/csims/boost_1_63_0/tools/build/src/tools/doxygen.jam:622:see definition of rule 'doxygen' being called /home/csims/boost_1_63_0/tools/build/src/build/project.jam:325: in load-jamfile /home/csims/boost_1_63_0/tools/build/src/build/project.jam:64: in load /home/csims/boost_1_63_0/tools/build/src/build/project.jam:145: in project.find Jamfile.v2:96: in modules.load /home/csims/boost_1_63_0/tools/build/src/build/project.jam:325: in load-jamfile /home/csims/boost_1_63_0/tools/build/src/build/project.jam:64: in load /home/csims/boost_1_63_0/tools/build/src/build/project.jam:145: in project.find /home/csims/boost_1_63_0/tools/build/src/build-system.jam:535: in load /home/csims/boost_1_63_0/tools/build/src/kernel/modules.jam:295: in import /home/csims/boost_1_63_0/tools/build/src/kernel/bootstrap.jam:139: in boost-build /home/csims/boost_1_63_0/boost-build.jam:17: in module scope ---------------------------------------------------------------------------------------------------------------------

2 1

[serialize] using virtual inheritance causes compiler error
by Douwe Gelling 02 Mar '17

02 Mar '17

Hi all, When trying to serialize a class with a virtual base class, I'm getting compilation errors. It seems to be part of a bug in type_traits, but I'm wondering if anyone knows a workaround for making it work anyhow. ultimately, the error boils down to "error: virtual function 'A::foo' has more than one final overrider in 'boost_type_traits_internal_struct_X'", using the code listing below.. It's simplified as much as possible, but obviously I need virtual inheritance due to using diamond inheritance. #include <boost/archive/text_oarchive.hpp> #include <boost/serialization/base_object.hpp> #include <boost/serialization/export.hpp> #include <boost/serialization/serialization.hpp> struct A { virtual ~A(){}; virtual void foo() = 0; template <class Archive> void serialize(Archive& ar, const unsigned int version) { } }; struct B : public virtual A { virtual void foo() { } template <class Archive> void serialize(Archive& ar, const unsigned int version) { ar& boost::serialization::base_object<A>(*this); } }; struct C : public B { template <class Archive> void serialize(Archive& ar, const unsigned int version) { ar& boost::serialization::base_object<B>(*this); } }; BOOST_CLASS_EXPORT(C); int main() { C c; return 0; }

4 7

How compile with clang ?
by Andy 02 Mar '17

02 Mar '17

I have installed Clang at "c:\Program Files\LLVM" try: b2 clean b2 toolset=clang cxxflags="-std=c++1y -stdlib=libc++" linkflags="-stdlib=libc++" --prefix=c:\boost -j 4 stage release b2 install toolset=clang cxxflags="-std=c++1y -stdlib=libc++" linkflags="-stdlib=libc++" --prefix=c:\boost but is error: fatal error: 'corecrt.h' file not found #include <corecrt.h>

2 1

Re: [Boost-users] Fw: error running boost book
by Clark Sims 02 Mar '17

02 Mar '17

I attached my user-config.jam I also attached the output of ../b2 --debug-configuration, as the file, debug.txt. I went to the BOOST_ROOT directory and rebuilt the headers. Initially ./b2 headers, caused errors, because I had initially run b2 as "sudo ./b2 install". I chowned back to my user, and reran. After I reran I still got the same errors. Thanks again for your help, Clark -------------------------------------------- On Mon, 2/27/17, Rene Rivera <grafikrobot(a)gmail.com> wrote: Subject: Re: Fw: error running boost book To: "Clark Sims" <clark_sims_boost(a)yahoo.com> Date: Monday, February 27, 2017, 10:18 AM On Mon, Feb 27, 2017 at 9:01 AM, Clark Sims <clark_sims_boost(a)yahoo.com> wrote: Hi Rene, I saw you were one of the developers on this project. Do you know how to solve this? Sorry I missed the email firs time around. Perhaps.. But need more info.. --- On Sat, 2/25/17, Clark Sims <clark_sims_boost(a)yahoo.com> wrote: > From: Clark Sims <clark_sims_boost(a)yahoo.com> > Subject: error running boost book > To: boost-users(a)lists.boost.org > Date: Saturday, February 25, 2017, 6:53 PM > I get the following error when I cd > to BOOST_ROOT/doc and run ../bjam > My ~/user-config.jam looks fine. I pasted it bellow the > error. Does anyone know how to fix this? It seems you forgot to paste the user-config. ALso try running with --debug-configuration and paste the header output for that. > I have spent a great deal of time trying to fix this. > It looks like the doxygen.jam in the > boost_1_63_0/tools/build/src/ tools directory does not like > the syngax of the doxygen rule in ~/user-config.jam. > > ------------------------------ ------------------------------ ------------------------------ ------------------------------ ---------- > > Building the tti docs with automatic index generation > disabled. Try building with --enable-index. > /home/csims/boost_1_63_0/libs/ dll/doc/Jamfile.v2:66: in > modules.load > *** argument error > * rule doxygen ( target : sources + : requirements * : > default-build * : usage-requirements * ) > * called with: ( autodoc_shared_library_core : : At this level it looks like it's missing aources. Looking at Boost DLL doc build file <https://github.com/boostorg/dll/blob/boost-1.63.0/doc/Jamfile.v2> it does globs for filling header files for the sources. Which would suggest that the headers aren't there. And hence you should try running "b2 headers" first. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

1 0

[thread] Feature request: set_value/exception with deferred notification (not at_thread_exit)
by TONGARI J 28 Feb '17

28 Feb '17

boost::promise (so does std::promise) only supports set_value/exception and their at_thread_exit variants, while the at_thread_exit variants support deferred notification, but the point to trigger the notification is restricted to thread-exit. This is not sufficient for, e.g. coroutine usage. This is the same problem as shown in this post: https://www.reddit.com/r/cpp/comments/4ctj2a/visual_studio_2015_update_2_co… If you want to write a "correct" adaptor for boost::future, currently you have to use extra storage when you get the return-value from the coroutine, and set the promise until final_suspend is reached. To efficiently address the problem, we need something like: * promise::set_value_deferred * promise::set_exception_deferred * promise::notify_deferred Thoughts?

2 3

libc++-5 doesn't know auto_ptr anymore
by bebuch 28 Feb '17

28 Feb '17

I just tried to compile one of my projects with LLVM-TOT and got a lot of error massages in boost's shared_ptr implementation because libc++ removes std::auto_ptr. (I don't use boost::shared_ptr directly, but via parts of boost::dll and boost:spirit::x3.) Is there a workaround? -- View this message in context: http://boost.2283326.n4.nabble.com/libc-5-doesn-t-know-auto-ptr-anymore-tp4… Sent from the Boost - Users mailing list archive at Nabble.com.

4 6

serialization support for gcc ?
by Alain Miniussi 28 Feb '17

28 Feb '17

Hi, In the serialization jam file (master), I see: <toolset>gcc:<cxxflags>"-fvisibility=hidden -fvisibility-inlines-hidden" with no mention of gcc version number. gcc-3.4.4, for one, does not support that option. Does that mean that the serialization library does not support the gcc-3.x serie ? Thanks Alain

4 8

Issues building Boost 1.63.0 on Solaris 11.3 x86 using Developer Studio 12.5
by Leo Carreon 28 Feb '17

28 Feb '17

Hi, According to the Boost 1.63.0 release notes, Solaris Studio 12.5 and Solaris Studio 12.5 C++11 are supported. However, when I build in C++11 and C++14 modes I get the following errors during the configuration check stage of the build: a.. Possible issue with threading even when I am building with the option – threading=multi: error: No best alternative for libs/context/build/asm/make_x86_64_sysv_elf_gas.o next alternative: required properties: <threading>multi matched next alternative: required properties: <threading>multi matched error: No best alternative for libs/context/build/asm/jump_x86_64_sysv_elf_gas.o next alternative: required properties: <threading>multi matched next alternative: required properties: <threading>multi matched error: No best alternative for libs/context/build/asm/ontop_x86_64_sysv_elf_gas.o next alternative: required properties: <threading>multi matched next alternative: required properties: <threading>multi matched b.. Issue with ICU library detection even when I have installed the developer/icu and library/icu packages: - icu : no - icu (lib64) : no - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. - Boost.Locale needs either iconv or ICU library to be built. I also get the following errors during the build stage: a.. Issue with Boost.Fiber: "./boost/fiber/detail/spinlock_ttas.hpp", line 73: Error: Could not find a match for std::chrono::duration<long, std::ratio<1, 1000000>>::duration({initializer list}) needed in boost::fibers::detail::spinlock_ttas::lock(). "./boost/fiber/detail/spinlock_ttas.hpp", line 73: Error: Initializer for constexpr variable us0 must be a constant expression. "./boost/fiber/detail/spinlock_ttas_adaptive.hpp", line 77: Error: Could not find a match for std::chrono::duration<long, std::ratio<1, 1000000>>::duration({initializer list}) needed in boost::fibers::detail::spinlock_ttas_adaptive::lock(). "./boost/fiber/detail/spinlock_ttas_adaptive.hpp", line 77: Error: Initializer for constexpr variable us0 must be a constant expression. "./boost/fiber/context.hpp", line 341: Error: A declaration does not specify a tag or an identifier. "./boost/fiber/context.hpp", line 341: Error: Only non-static data members may be mutable. "./boost/fiber/context.hpp", line 341: Error: Use ";" to terminate declarations. "./boost/fiber/context.hpp", line 341: Error: "}" expected instead of "noexcept". "./boost/fiber/context.hpp", line 341: Error: Use ";" to terminate declarations. "./boost/fiber/context.hpp", line 341: Error: A declaration was expected instead of "noexcept". "./boost/fiber/context.hpp", line 342: Error: run_ is not defined. "./boost/fiber/context.hpp", line 342: Error: A template name was expected instead of 'forward'. "./boost/fiber/context.hpp", line 342: Error: ctx is not defined. "./boost/fiber/context.hpp", line 342: Error: Unexpected ")" -- Check for matching parenthesis. "./boost/fiber/context.hpp", line 342: Error: Operand expected instead of ",". "./boost/fiber/context.hpp", line 342: Error: The function "std::forward()" cannot be defined in the current scope. "./boost/fiber/context.hpp", line 343: Error: A declaration was expected instead of ",". "./boost/fiber/context.hpp", line 344: Error: Fn is not defined. "./boost/fiber/context.hpp", line 344: Error: A template name was expected instead of 'forward'. "./boost/fiber/context.hpp", line 344: Error: fn is not defined. "./boost/fiber/context.hpp", line 345: Error: Unexpected ")" -- Check for matching parenthesis. "./boost/fiber/context.hpp", line 345: Error: Operand expected instead of "}". "./boost/fiber/context.hpp", line 345: Error: The function "std::forward()" cannot be defined in the current scope. "./boost/fiber/context.hpp", line 355: Error: A declaration was expected instead of "{". "./boost/fiber/context.hpp", line 357: Error: No direct declarator preceding "(". b.. Issue with libs/log which happens in C++11 mode only: "libs/log/src/named_scope.cpp", line 118: Error: Overloading ambiguity between "boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)" and "boost::optional<boost::log::v2_mt_posix::attributes::named_scope_list>::operator=<boost::log::v2_mt_posix::attributes::named_scope_list&>(boost::log::v2_mt_posix::attributes::named_scope_list&)". 1 Error(s) detected. "CC" -std=c++11 -xO4 -mt -erroff=%none -m64 -KPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_DYN_LINK=1 -DBOOST_CHRONO_DYN_LINK=1 -DBOOST_DATE_TIME_DYN_LINK=1 -DBOOST_FILESYSTEM_DYN_LINK=1 -DBOOST_LOG_BUILDING_THE_LIB=1 -DBOOST_LOG_DLL -DBOOST_LOG_HAS_PTHREAD_MUTEX_ROBUST -DBOOST_LOG_USE_NATIVE_SYSLOG -DBOOST_LOG_WITHOUT_DEBUG_OUTPUT -DBOOST_LOG_WITHOUT_EVENT_LOG -DBOOST_SPIRIT_USE_PHOENIX_V3=1 -DBOOST_SYSTEM_DYN_LINK=1 -DBOOST_SYSTEM_NO_DEPRECATED -DBOOST_THREAD_BUILD_DLL=1 -DBOOST_THREAD_DONT_USE_CHRONO=1 -DBOOST_THREAD_POSIX -DBOOST_THREAD_USE_DLL=1 -DDATE_TIME_INLINE -DNDEBUG -D_XOPEN_SOURCE=500 -D__EXTENSIONS__ -D__STDC_CONSTANT_MACROS -D__typeof__=__typeof__ -I"." -I"libs/log/src" -c -o "bin.v2/libs/log/build/sun/release/address-model-64/threading-multi/named_scope.o" "libs/log/src/named_scope.cpp" ...failed sun.compile.c++ bin.v2/libs/log/build/sun/release/address-model-64/threading-multi/named_scope.o... c.. Issue with libs/python: "libs/python/src/numpy/dtype.cpp", line 61: Error: NPY_FLOAT16 is not defined. 1 Error(s) detected. "CC" -std=c++11 -xO4 -mt -erroff=%none -m64 -KPIC -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -I"/usr/include/python2.7" -I"/usr/lib/python2.7/vendor-packages/numpy/core/include" -c -o "bin.v2/libs/python/build/sun/release/address-model-64/threading-multi/numpy/dtype.o" "libs/python/src/numpy/dtype.cpp" ...failed sun.compile.c++ bin.v2/libs/python/build/sun/release/address-model-64/threading-multi/numpy/dtype.o... Has anyone found solutions to these issues? FYI, a set of libraries are still generated even after the above issues have occurred. I’m not sure how reliable are these libraries which I assume are unaffected by the above issues. Kinds regards, Leo

2 2

Issue with Boost.Test using Oracle Developer Studio 12.5
by Leo Carreon 28 Feb '17

28 Feb '17

Hi, This is a continuation of the issues I’ve encountered with Boost 1.63.0 using Developer Studio 12.5. I’m assuming that even with the Boost 1.63.0 build issues that libraries unaffected by the build issues are usable. Therefore, I have attempted to build one of my small projects in both C++11 and C++14 modes. The builds of this small project failed with the following error message: "/opt/boost1.63.0/include/boost/test/unit_test_log.hpp", line 218: Error: boost::unit_test::unit_test_log_t::test_unit_skipped hides the virtual function boost::unit_test::test_observer::test_unit_skipped(const boost::unit_test::test_unit&). This error was encountered compiling a source file containing the following: #define BOOST_TEST_MODULE TestImport #include <boost/test/unit_test.hpp> Is this a Boost.Test issue or is it a Developer Studio 12.5 issue? If it is a Boost.Test issue, how do I resolve it? Kind regards, Leo

1 0

[gsoc17] Boost will be participating in Google Summer of Code in 2017
by Niall Douglas 27 Feb '17

27 Feb '17

I am very pleased to inform the Boost community that Google accepted us into their Summer of Code programme this year. This was especially welcome after we were given "a year off" last year which could have caused substantial disruption to the multi year student projects had it not been due to the timely action of the steering committee and generous sponsorship of a stop gap Boost Summer of Code in 2016 by IMC Financial Markets. Last year Google completely rebuilt the Summer of Code website so it no longer is anything like it was before. Now we must individually invite those who vote on student projects, so *anyone willing to rank student project proposals* can you please email us with your details: 1. Your email address matching your Google Account so we can invite you onto the GSoC programme. 2. (Optional) your email address matching your Github Account so we can invite you onto the Boost GSoC github org for 2017 as a potential mentor. Our thanks to those who have already added project ideas to https://svn.boost.org/trac/boost/wiki/SoC2017, but we need MORE ideas and MORE potential project mentors. Follow the project idea template at https://svn.boost.org/trac/boost/wiki/GSoCIdeaTemplate and either add it straight to the wiki page or email it to us so we can add it for you. Our thanks to all in advance.

1 0

Generate SSL certificate, chain file, dh and key for boost::asio::ssl::context
by jupiter 27 Feb '17

27 Feb '17

Hi, I think I can use openssl to generate those self signed files, correct? I saw some programs use 4 use_certificate_chain_file, use_certificate_file, use_private_key_file and use_tmp_dh_file in both server and client sites, but I also saw some test program only use one ca.pem in client site and 3 use_certificate_chain_file, use_private_key_file and use_tmp_dh_file in server site, which is correct or better? Any guideline? Thank you.

2 4

Monitor lost client data connections
by jupiter 27 Feb '17

27 Feb '17

Hi, I have a server socket connected by many clients using boost::asio::ip::tcp::socket to set up server socket connection and to use boost::asio::ip::tcp::acceptor async_accept for new client connections. The client may come and go, so I need to check if the connection is still valid or not before sending message to clients. How can I check if a client connection is no longer valid? My server does not seem get any indication when a client terminate the connection. Thank you. Kind regards, - j

2 4

[context/coroutine] DLL link errors in VS2015
by Gavin Lambert 26 Feb '17

26 Feb '17

I'm migrating some existing code that uses Boost.Coroutine from VS2013 to VS2015 and from Boost 1.55 to Boost 1.60. (Minor aside: coroutine<T>::push_type had an empty() method in 1.55 which has vanished in 1.60. This was mildly annoying but easily fixed by using operator! instead.) The code builds and runs fine as-is in VS2015 with Boost 1.60. However I wanted to try migrating to Boost.Coroutine2 as well, since Coroutine is deprecated. This however gives me the following errors: t:\boost\boost_1_60_0\boost\context\execution_context.ipp(209): warning C4251: 'boost::context::execution_context::ptr_': class 'boost::intrusive_ptr<boost::context::detail::activation_record>' needs to have dll-interface to be used by clients of class 'boost::context::execution_context' t:\boost\boost_1_60_0\boost\context\execution_context.ipp(54): note: see declaration of 'boost::intrusive_ptr<boost::context::detail::activation_record>' error LNK2001: unresolved external symbol "public: static class boost::intrusive_ptr<struct boost::context::detail::activation_record> boost::context::detail::activation_record::current_rec" (?current_rec@activation_record@detail@context@boost@@2V?$intrusive_ptr@Uactivation_record@detail@context@boost@@@4@A) I'm building with BOOST_ALL_DYN_LINK, in case that makes a difference. Is this a known issue? Is it fixed in a later Boost release? (FWIW, Boost.Coroutine also generates C4251 with a different symbol but does not generate LNK2001, so the application still works.)

2 6

Re: [Boost-users] Building Boost 1.63.0 with Oracle Developer Studio 12.5
by Leo Carreon 26 Feb '17

26 Feb '17

These are the issues I have discovered after examining the build log: a.. Error message during configuration check: error: No best alternative for libs/context/build/asm/make_x86_64_sysv_elf_gas.o next alternative: required properties: <threading>multi b.. Warning message during configuration check even after installing developer/icu and library/icu packages: - Boost.Locale needs either iconv or ICU library to be built. c.. Lots of error messages during Boost.Fiber build. d.. Error message during Boost.Python build. I am attaching a copy of the build log for your perusal. I have also adjusted the build command to include “threading=multi”. From: Leo Carreon Sent: Sunday, February 26, 2017 12:40 PM To: Boost Users Mailing List Subject: Building Boost 1.63.0 with Oracle Developer Studio 12.5 Hi, Is building Boost 1.63.0 with Oracle Developer Studio 12.5 supported? I tried building it using the following commands but I get a lot of errors: ./bootstrap.sh --with-toolset=sun ./b2 link=shared runtime-link=shared address-model=64 threading=multi variant=release cxxflags="-std=c++14" linkflags="-std=c++14" FYI, I’m building on Oracle Solaris 11.3 running on a x86-64 virtual machine. Am I missing something? Kind regards, Leo

1 0

Building Boost 1.63.0 with Oracle Developer Studio 12.5
by Leo Carreon 26 Feb '17

26 Feb '17

Hi, Is building Boost 1.63.0 with Oracle Developer Studio 12.5 supported? I tried building it using the following commands but I get a lot of errors: ./bootstrap.sh --with-toolset=sun ./b2 link=shared runtime-link=shared address-model=64 variant=release cxxflags="-std=c++14" linkflags="-std=c++14" FYI, I’m building on Oracle Solaris 11.3 running on a x86-64 virtual machine. Am I missing something? Kind regards, Leo

1 0

[Boost.Build, Coroutine2] /usr/bin/ld: cannot find -lboost_coroutine2
by Mikhail Strelnikov 24 Feb '17

24 Feb '17

Hello. My Jamroot looks like this: local BOOST_ROOT = [ modules.peek : BOOST_ROOT ] ; project my_project : requirements <define>BOOST_ALL_NO_LIB=1 : build-dir bin.v2 ; use-project /boost : $(BOOST_ROOT) ; exe my : my_source.cpp /boost//thread /boost//coroutine2 ; Command line: b2 --build-dir=whatever -sBOOST_ROOT=/path/to/boost_1_63_0 I'm getting the following error: /usr/bin/ld: cannot find -lboost_coroutine2 This happens because a library without sources: https://github.com/boostorg/coroutine2/blob/develop/build/Jamfile.v2#L29 is a pre-built library. Header-only library should use alias - http://www.boost.org/build/doc/html/bbv2/faq/header-only-libraries.html After changing "lib boost_coroutine2..." to "alias boost_coroutine2 ;" I had to add <library>/boost//context to usage-requirements of boost/coroutine2 project. Apparently reference to Context from "requirements" (at line 13) is not enough in this case. Can this be a bug in Boost.Build? But the problem with alias is that "b2 --with-coroutine2" does not build anything at all. My question: is it supported scenario by Boost.Build - header-only library depending on not-header-only library? Bonus question: can those BOOST_DISABLE_ASSERTS be removed from Jamfiles building Context, Coroutine2 and Fiber? Thanks.

1 0

quick question about macro
by Peter Gusev 24 Feb '17

24 Feb '17

hi there! I'm using boost library occasionally and have this simpleton question to ask. i need to debug *boost::asio::io_service* by enabling *BOOST_ASIO_ENABLE_HANDLER_TRACKING* macro. so, do I have to rebuild the library like * ./b2 cxxflags="-DBOOST_ASIO_ENABLE_HANDLER_TRACKING"...* or adding * #define BOOST_ASIO_ENABLE_HANDLER_TRACKING* to my source file is enough? (this doesn't work for me, so i suspect I should go with the first option) thanks, -- Peter Gusev

2 1

[bip] alignment/padding differs
by Jan Boehme 23 Feb '17

23 Feb '17

Hi, I'm using interprocess to share mem between different processes. Unfortunately these processes were built using different compiler version (gcc3, gcc4, gcc5) and we're seeing different alignment or padding dependent on which run-time was in charge of creating the mapped files. Of course we used the same boost version (1.60) while creating the binaries. Obviously ip can't handle these different layouts and mostly runs in indefinite loops while traversing an rb-tree not finding the first shm object. Are there any template parameters that enable the code to be accessed using different run times through forcing the same layout? Thanks a lot, Jan.

2 2

Using Boost 1.63 on Windows with FindBoost.cmake
by csiga.biga＠aol.com 22 Feb '17

22 Feb '17

Does anyone have a working installation of Boost 1.63 on Windows that FindBoost.cmake can be instructed to find? I tried with both a custom build (for MSMPI mostly) that it failed to find the libraries of, and after reading through FindBoost.cmake, I saw it is dominantly tailored towards the prebuilt binaries (at least on Windows), so I grabbed that, I set BOOSTROOT to the installation root, but it still fails to find Boost::chrono I got find_package(Boost 1.63 REQUIRED COMPONENTS chrono) include_directories(${Boost_INCLUDE_DIRS}) in my top-level CMakeLists.txt file, as all of my targets depend on chrono, and after that I use target_link_libraries (${declare_trisycl_test_TARGET} $<$<BOOL:USES_OPENCL>:${OpenCL_LIBRARIES}> $<$<NOT:$<BOOL:WIN32>>:Threads::Threads> Boost::chrono) On the command-line this is what I get at configure time: CMake Error at C:/Kellekek/Kitware/CMake/3.8.0/share/cmake-3.8/Modules/FindBoost.cmake:1812 (message): Unable to find the requested Boost libraries. Boost version: 1.63.0 Boost include path: C:/Kellekek/Boost/1.63.0-prebuilt Could not find the following Boost libraries: boost_chrono Some (but not all) of the required Boost libraries were found. You may need to install these additional Boost libraries. Alternatively, set BOOST_LIBRARYDIR to the directory containing Boost libraries or BOOST_ROOT to the location of Boost. Call Stack (most recent call first): CMakeLists.txt:26 (find_package) As far as FindBoost.cmake goes, it seems to know chrono for 1.63. So how should this work?

2 1

Re: [Boost-users] [Boost.Test] Using intel MKL instead of ACML with the boost testing framework
by anandram sundar 21 Feb '17

21 Feb '17

Sending this again, since I hadnt subscribed before sending this email. One suspicious candidate from further debugging is the results_collector singleton(just because it appears in the stack and because its a singleton) On Tue, Feb 21, 2017 at 2:03 PM, anandram sundar <sundaranandram(a)gmail.com> wrote: > Hi, > I recently wrote some tests using the Boost testing framework and > everything was working fine until I used the intel MKL with my project. As > soon as I started linking these libraries, the tests started failing with a > segmentation fault. This happens after the test execution is done and when > the cleanup is happening. Looking at what valgrind outputs, it seems like > there is some memory being released which is invalid(not sure if it is > because of calling free on already freed memory). This actually happens > even if none of the code depends on the MKL. Just adding them to the linked > libraries is enough to cause this. > > GCC 4.9.3 > Boost ver 1.62 > > *==85160== Invalid read of size 4* > *==85160== at 0x10916C57: std::basic_string<char, > std::char_traits<char>, std::allocator<char> >::~basic_string() (in > /lib/libstdc++.so.6.0.20)* > *==85160== by 0x1104AEBC: __cxa_finalize (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x41981E2: ??? (in > /lib/libboost_unit_test_framework.so.1.62.0)* > *==85160== by 0x400EC5B: _dl_fini (in /lib64/ld-2.12.so > <http://ld-2.12.so>)* > *==85160== by 0x1104AB21: exit (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x11033D63: (below main) (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== Address 0x1262fab0 is 16 bytes inside a block of size 30 > free'd* > *==85160== at 0x4C26FD6: operator delete(void*) > (vg_replace_malloc.c:480)* > *==85160== by 0x1104AB21: exit (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x11033D63: (below main) (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > > > *==85160== Invalid free() / delete / delete[] / realloc()* > *==85160== at 0x4C26FD6: operator delete(void*) > (vg_replace_malloc.c:480)* > *==85160== by 0x1104AEBC: __cxa_finalize (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x41981E2: ??? (in > /lib/libboost_unit_test_framework.so.1.62.0)* > *==85160== by 0x400EC5B: _dl_fini (in /lib64/ld-2.12.so > <http://ld-2.12.so>)* > *==85160== by 0x1104AB21: exit (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x11033D63: (below main) (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== Address 0x1262faa0 is 0 bytes inside a block of size 30 free'd* > *==85160== at 0x4C26FD6: operator delete(void*) > (vg_replace_malloc.c:480)* > *==85160== by 0x1104AB21: exit (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > *==85160== by 0x11033D63: (below main) (in /lib64/libc-2.12.so > <http://libc-2.12.so>)* > > > I am not sure why this is happening. Are there any known compatibility > issues between MKL and Boost testing framework. I was using ACML before > this and the tests were working fine with them. > > > Thanks, > Anand >

1 0

[iostreams] filtering streams in a chain are continually writing the same bytes
by Andrew Ames 21 Feb '17

21 Feb '17

Perhaps someone can clarify that my use of multichar_output_filter is valid. When I debug this, even though my write method is returning 4 bytes for every write, the caller of my output filter keeps providing me the same four bytes after the first sequence of 4 bytes. This is boot version 1.62. Here is compiling code that illustrates: class fixed_size_output_filter : public boost::iostreams::multichar_output_filter { public: fixed_size_output_filter(std::streamsize size = 4) : mSize(size) {} template<typename Sink> std::streamsize write(Sink &sink, const char *s, std::streamsize n) { std::streamsize bytesAttempted = std::min(mSize, n); std::streamsize bytesActual = boost::iostreams::write(sink, s, bytesAttempted); return bytesActual; } private: std::streamsize mSize; }; BOOST_AUTO_TEST_CASE(FixedSizeOutputFilter) { #define BYTES 500 char sink_buffer[BYTES]; array_sink array_sink(sink_buffer, sizeof(sink_buffer)); std::streampos os_pos; { filtering_ostream os; os.push(fixed_size_output_filter()); os.push(array_sink); char buffer[BYTES]; for(char i = 0; i < sizeof(buffer); i++) buffer[i] = i; os.write(buffer, sizeof(buffer)); } for(char i = 0; i < sizeof(sink_buffer); i++) BOOST_CHECK(i == sink_buffer[i]); } The actual bytes that end up in the sink_buffer are as follows: 0, 1, 2, 3, 4, 5, 6, 7, 4, 5, 6, 7, 4, 5, 6, 7, 4, 5, 6, 7, ....uninitialized bytes follow through the rest of the buffer. It would appear that the indirect_streambuf in use by the filter chain is incorrectly flushing the bytes. Is my understanding of the library flawed? Does this appear to be a bug? Any help is greatly appreciated. -- Andrew Ames aames(a)tanzle.com

1 1

[thread] Ambiguity in variadic wait_for_all
by Gavin Lambert 18 Feb '17

18 Feb '17

A colleague recently ran into an interesting issue when upgrading some working code from Boost 1.55 to 1.60/1.63 (and from C++03 to C++11). The exact details are unimportant, but it was trying to get the address of boost::wait_for_all(Iterator, Iterator), for use in a Boost.Bind call. In 1.55, this worked fine, although of course it had to supply template parameters that proved the parameters were not futures (thus causing enable_if<is_future_type<F1>> to fail, disabling the two-future-args overload of the function. In 1.60/1.63, the variadic method is encountered instead, which lacks any enable_if condition and thus the ambiguity between the two remains and the compiler errors out. (When calling it directly, the variadic one manages to get disabled as long as the iterator type lacks a wait() method, but this doesn't apply when just getting the method address, as it's not part of the signature.) Should the variadic form also have enable_if? Or is this considered user error for trying to use Bind in a variadic-compatible compiler instead of using a lambda?

2 3