- Boost-users - lists.boost.org

statechart] [gcc-4.7.2] a template state inherited from statechart::state results in compiler error
by Nikiforov Anatoly 15 Jan '13

15 Jan '13

Hi, I'm using Boost.Statechart and have come across a strange gcc-4.7.2 behavior on the attached sample code. The error is: cpp-lab/boost/statechart/main.cpp:89:23: error: expected ')' before 'ctx' If outermost_context() isn't used in Inner3() constructor and statechart::simple_state is used instead of statechart::state everything is OK. If Inner3 is not a template then everything is OK The problem occurs only if a state template class is inherited from statechart::state. Is there any workaround for the issue? Thanks in advance.

2 2

[Property Tree] Debugger visualizer for property tree
by Elizabeta 15 Jan '13

15 Jan '13

Hi I need debugger visualizer for property tree. Can't find it here https://svn.boost.org/svn/boost/sandbox/boost_docs/subprojects/DebuggerVisu…, I guess it doesn't exist. Any plans for making it in near future ?

1 0

64 bits migration problems
by simone pilozzi 15 Jan '13

15 Jan '13

Dear Users, I am experiencing a lot of issues in compiling my VC 2010 projects with a 64 bits machin (while they work happily witha 32 bits). I downloaded the 1_51 version of boost for 64bits and I obtained the following error with the serialization library: Error 495 error LNK1104: cannot open file 'libboost_serialization-vc100-mt-gd-1_51.lib Then I tried some older version ( 1_47, i ) but I received this series of compiling errors related again to the xml archive. Error 493 error LNK2019: unresolved external symbol "protected: __cdecl boost::archive::xml_oarchive_impl<class boost::archive::xml_oarchive>::xml_oarchive_impl<class boost::archive::xml_oarchive>(class std::basic_ostream<char,struct std::char_traits<char> > &,unsigned int)" ( ??0?$xml_oarchive_impl@Vxml_oarchive@archive@boost@@@archive@boost@@IEAA@AEAV?$basic_ostream@DU?$char_traits@D@std@@@std@@I@Z) referenced in function "public: __cdecl boost::archive::xml_oarchive::xml_oarchive(class std::basic_ostream<char,struct std::char_traits<char> > &,unsigned int)" ( ??0xml_oarchive@archive@boost@@QEAA@AEAV?$basic_ostream@DU?$char_traits@D@std@@@std@@I@Z ) Tried to build boost 1_51 with the 64bits using boostrap but it did not find build.bat since it is missing (I found boost-build.jam) Any suggestion?

3 5

Runtime Library Error in C++ called boost.python and custom module
by simon zhang 12 Jan '13

12 Jan '13

I have called some python in C++,then python will called a custom module that was writed by c++. This problem occured when I track, python call custom module. Error: Microsoft Visual C++ Runtime Library Runtime Error!Program:xxxxx.exe R6034An application has made an attempt to load the C runtime library incorrectly.Please contact the application's support team for more information. Detailed descriptions： Environment：　　　winxp,Mingw4.7+MSYS,Library：　　　wxwidgets2.8 static compile (called in gui code) python27 python27.dll (called in gui code) installed version boost.python static compile (called in gui code) boost.python static compile (called in custom module) libevent2.019 static compile (called in custom module) I can be successful,called only python in C++ or called custom module in python. What should I do to solve the problem?

1 0

[thread] Can Boost.Thread use Boost.Atomic without falling on a compatibility issue?
by Vicente J. Botet Escriba 12 Jan '13

12 Jan '13

Hi, in order to fix this issue, https://svn.boost.org/trac/boost/ticket/5752 : "boost::call_once() is unreliable on some platforms", I would like to use Boost.Atomic as suggested on the ticket. As Boost.Atomic is not a header-only library the user would need to link with boost_atomic. Is this an acceptable change? I'm requesting this as recently there were some people reactive to some changes in Boost.Thread. Would this be considered an compatibility issue? If yes should the fix for the call_once issue be included if the user request it using conditional compilation or even go on a separated version of Boost.Thread? Thanks, Vicente

1 0

Newbie Question
by Walker.Kyle 12 Jan '13

12 Jan '13

It appears the following code has a warning detected by GCC4.7.2: /boost/include/boost-1_52/boost/property_tree/detail/ptree_utils.hpp: In instantiation of 'std::string boost::property_tree::detail::narrow(const Ch*) [with Ch = wchar_t; std::string = std::basic_string<char, std::char_traits<char>, std::allocator<char> >]': /boost/include/boost-1_52/boost/property_tree/string_path.hpp:64:36: required from here /boost/include/boost-1_52/boost/property_tree/detail/ptree_utils.hpp:76:13: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] boost-1_52\boost\property_tree\detail\ptree_utils.hpp (Starting line 70): template<class Ch> std::string narrow(const Ch *text) { std::string result; while (*text) { if (*text < 0 || *text > (std::numeric_limits<char>::max)()) Shouldn't it be: template<class Ch> std::string narrow(const Ch *text) { std::string result; while (*text) { if (*text < 0 || *text > (std::numeric_limits<Ch>::max)()) Code to reproduce this warning (just the include): #include <boost/property_tree/ptree.hpp>

2 1

Boost and -fvisibility=hidden
by Dániel Varga 12 Jan '13

12 Jan '13

Hi, I would like to add symbol visibility support to my library. Using -fvisibility=hidden option I compared the changed symbols, boost::bad_function_call typeinfo was visible previously but with hidden default visibility it is hidden. It compiles just fine, but according to gcc wiki (http://gcc.gnu.org/wiki/Visibility) exceptions must be visible as runtime error might happen because of missing typeinfo. I found bug report (https://svn.boost.org/trac/boost/ticket/2309) that exception class not exported in Boost.Thread, the problem was fixed by adding pragmas. In boost/function/function_base.hpp pragmas or other ways to change visibility isn't used, so the boost::bad_function_call typeinfo became hidden using -fvisibility=hidden. In the former boost bug report (https://svn.boost.org/trac/boost/ticket/2309) runtime error does not even mentioned, I couldn't reproduce the runtime error in my small experiments. In what situations can hidden symbol cause problems? Is it normal that boost::bad_function_call typeinfo is hidden or it is a boost bug that can cause problems and should be fixed? A made a small test library and application. The library has hidden boost::bad_function_call typeinfo, but the application seems catching the exception properly. Can this cause an error, why is it working? Makefile: CXX=g++ test_exception: test_exception.cpp libmydso.so $(CXX) -L. -lmydso $< -o $@ libmydso.so: mydso.cpp $(CXX) -fvisibility=hidden -fPIC -shared -Wl,-soname,$@ $< -o $@ mydso.h: void __attribute__ ((visibility ("default"))) test_exception(); mydso.cpp: #include <boost/function.hpp> #include "mydso.h" void test_exception() { boost::function<int (int, int)> f; f(5, 4); } test_exception.cpp: #include <iostream> #include <stdexcept> #include "mydso.h" int main() { try { test_exception(); } catch (std::runtime_error) { std::cerr << "Got std::runtime_error" << std::endl; } catch (...) { std::cerr << "Got other exception" << std::endl; } } Thanks, Dani

1 0

Re: [Boost-users] mixed 32 bit and 54 bit
by Dave Dyer 11 Jan '13

11 Jan '13

> > >You need to define an offset_ptr with 64 bit OffsetType > >typedef offset_ptr<T, std::ptrdiff_t, unsigned long long> my_offset_ptr; > >and instantiate all interprocess managed resources like >(basic_managed_shared_memory) like this: > > >typedef basic_managed_shared_memory > <char > ,rbtree_best_fit<mutex_family, my_offset_ptr> > ,iset_index> >managed_shared_memory; > >Again, this is not supported and it's still experimental. Thanks for the guidance. It may work for my pirposes, as I dont intend to use any boost facilities except some basic block allocations of memory. One suggestion; make a 32-vs-64 bit test part of the setup code, so when a known incompatible producer/consumer relationship exists, it can gracefully throw an error instead of failing mysteriously.

1 0

boost::range vs && (rvalue ref)
by Neal Becker 11 Jan '13

11 Jan '13

Passing range by ref (&) is fine, but using (&&) results in and error. Any ideas? #include <boost/range.hpp> #include <vector> template<typename out_t> void F (out_t && o) { typedef typename boost::range_value<out_t>::type T; } void G() { std::vector<int> v; F (v); } usr/local/src/boost_1_52_0/boost/mpl/eval_if.hpp:60:31: error: no type named ‘type’ in ‘boost::mpl::eval_if_c<false, boost::range_const_iterator<std::vector<int>&>, boost::range_mutable_iterator<std::vector<int>&> >::f_ {aka struct boost::range_mutable_iterator<std::vector<int>&>}’ bug.cc: In instantiation of ‘void F(out_t&&) [with out_t = std::vector<int>&]’: bug.cc:12:7: required from here bug.cc:6:52: error: no type named ‘type’ in ‘struct boost::range_value<std::vector<int>&>’

3 4

Re: [Boost-users] mixed 32bit and 64bit shared memory
by Dave Dyer 11 Jan '13

11 Jan '13

I see notes about boost supporting "customizing offset_ptr" to support shared memory where both 64 bit and 32 bit processes are sharing the memory, but I don't see a specific example of how to do that. It seems that "out of box" it doesn't work.

2 1