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

[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