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

Compile error with QNX compiler
by Kito Berg-Taylor 04 Mar '09

04 Mar '09

I am using the QNX 6.4.0 development environment (based on gcc 4.2.4) to compile boost_thread-static-mt from boost 1.38, and I am getting the following errors. I was wondering if someone could tell me whether this is a compiler problem or a problem with boost. I should mention that I don't get the same error with gcc4 or mingw-gcc4. I have the latest boost from svn, but I'm unable to test that on this compiler because I'm still sorting through other build problems there. cd /path_to_build/build.qnx/Core/LIB_MISSIONPLANNER && /path_to_qnx/qnx640/host/linux/x86/usr/bin/qcc -Vgcc_ntox86 -lang-c++ -w1 -I/path_to_build/Externals/boost_1_38_0 -o CMakeFiles/MISSIONPLANNER.dir/CommTCP.cpp.obj -c /path_to_build/Core/LIB_MISSIONPLANNER/CommTCP.cpp In file included from /path_to_build/Externals/boost_1_38_0/boost/serialization/extended_type_info_typeid.hpp:33, from /path_to_build/Externals/boost_1_38_0/boost/archive/detail/iserializer.hpp:64, from /path_to_build/Externals/boost_1_38_0/boost/archive/detail/interface_iarchive.hpp:23, from /path_to_build/Externals/boost_1_38_0/boost/archive/detail/common_iarchive.hpp:20, from /path_to_build/Externals/boost_1_38_0/boost/archive/basic_text_iarchive.hpp:31, from /path_to_build/Externals/boost_1_38_0/boost/archive/text_iarchive.hpp:23, from /path_to_build/Core/LIB_MISSIONPLANNER/Connection.hpp:19, from /path_to_build/Core/LIB_MISSIONPLANNER/CommTCP.hpp:6, from /path_to_build/Core/LIB_MISSIONPLANNER/CommTCP.cpp:1: /path_to_build/Externals/boost_1_38_0/boost/serialization/factory.hpp:37: error: template declaration of 'T* boost::serialization::factory' /path_to_build/Externals/boost_1_38_0/boost/serialization/factory.hpp:37: error: 'va_list' is not a member of 'std' In file included from /path_to_build/Externals/boost_1_38_0/boost/archive/detail/iserializer.hpp:64, from /path_to_build/Externals/boost_1_38_0/boost/archive/detail/interface_iarchive.hpp:23, from /path_to_build/Externals/boost_1_38_0/boost/archive/detail/common_iarchive.hpp:20, from /path_to_build/Externals/boost_1_38_0/boost/archive/basic_text_iarchive.hpp:31, from /path_to_build/Externals/boost_1_38_0/boost/archive/text_iarchive.hpp:23, from /path_to_build/Core/LIB_MISSIONPLANNER/Connection.hpp:19, from /path_to_build/Core/LIB_MISSIONPLANNER/CommTCP.hpp:6, from /path_to_build/Core/LIB_MISSIONPLANNER/CommTCP.cpp:1: /path_to_build/Externals/boost_1_38_0/boost/serialization/extended_type_info_typeid.hpp: In member function 'void* boost::serialization::extended_type_info_typeid<T>::construct(unsigned int, ...) const': /path_to_build/Externals/boost_1_38_0/boost/serialization/extended_type_info_typeid.hpp:96: error: 'va_list' is not a member of 'std' /path_to_build/Externals/boost_1_38_0/boost/serialization/extended_type_info_typeid.hpp:96: error: expected `;' before 'ap' /path_to_build/Externals/boost_1_38_0/boost/serialization/extended_type_info_typeid.hpp:97: error: 'ap' was not declared in this scope /path_to_build/Externals/boost_1_38_0/boost/serialization/extended_type_info_typeid.hpp:100: error: 'factory' was not declared in this scope /path_to_build/Externals/boost_1_38_0/boost/serialization/extended_type_info_typeid.hpp:100: error: expected primary-expression before ',' token /path_to_build/Externals/boost_1_38_0/boost/serialization/extended_type_info_typeid.hpp:102: error: expected primary-expression before ',' token /path_to_build/Externals/boost_1_38_0/boost/serialization/extended_type_info_typeid.hpp:104: error: expected primary-expression before ',' token /path_to_build/Externals/boost_1_38_0/boost/serialization/extended_type_info_typeid.hpp:106: error: expected primary-expression before ',' token /path_to_build/Externals/boost_1_38_0/boost/serialization/extended_type_info_typeid.hpp:108: error: expected primary-expression before ',' token cc: /path_to_qnx/qnx640/host/linux/x86/usr/lib/gcc/i386-pc-nto-qnx6.4.0/4.2.4/cc1plus error 1 compiler identifies itself as gcc 4.2.4: kito@Vostok:~$ ntox86-g++ --version ntox86-g++ (GCC) 4.2.4

1 0

I Can't Compile The QuickStart Example
by Fagner Patricio 04 Mar '09

04 Mar '09

Hello!! I'm new in the list, I from Brazil, so, sorry about my english :) I have a problem, I am try to compile the QuickStart Python Example on ubuntu 8.04 using the 1.34 library version, this is the result: fagner@fagner-desktop:/usr/share/doc/libboost-doc/examples/libs/python/example/quickstart$ sudo bjam toolset=gcc --verbose-teste test --debug-configuration notice: found boost-build.jam at /usr/share/doc/libboost-doc/examples/libs/python/example/quickstart/boost-build.jam notice: loading Boost.Build from /usr/share/boost-build notice: loading site-config.jam from /etc/site-config.jam notice: loading user-config.jam from /usr/share/boost-build/user-config.jam notice: using gcc libraries :: <toolset>gcc-4.2 :: /usr/bin /usr/lib /usr/lib32 /usr/lib64 notice: using gcc archiver :: <toolset>gcc-4.2 :: /usr/bin/ar warning: toolset gcc initialization: can't find tool windres warning: initialized from notice: using rc compiler :: <toolset>gcc-4.2 :: /usr/bin/as error: Unable to find file or target named error: '/boost/python//boost_python' error: referred from project at error: '.' fagner@fagner-desktop:/usr/share/doc/libboost-doc/examples/libs/python/example/quickstart$ What's my mistake? -- Fagner Patrício João Pessoa - PB Brasil

2 1

Re: [Boost-users] Tag dispatching
by Hicham Mouline 04 Mar '09

04 Mar '09

> ----- Original Message ----- > From: "Ovanes Markarian" <om_boost(a)keywallet.com> > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] Tag dispatching > Date: Wed, 4 Mar 2009 14:12:09 +0100 > > Hicham, > > please see my comments below: > > On Wed, Mar 4, 2009 at 1:54 PM, Hicham Mouline <hicham(a)mouline.org> wrote: > > > Hello, > > > > I have a question about tag dispatching (for e.g. the std::advance() > > function in the std lib, as described for instance in > > http://www.boost.org/community/generic_programming.html#tag_dispatching) > > > > 1. The call to > > detail::advance_dispatch(i, n, category); > > I don't understand. category is a type not an object, it should be > > category(), right? > > > typename *iterator_traits<InputIterator>::iterator_category* category; > detail::advance_dispatch(i, n, *category*); > > here is no typedef used, so category is an instance of iterator_category. In > the template context you have to prefix it with typename keyword. Using: > > typename *iterator_traits<InputIterator>::iterator_category* category(); > > declares a function, which returns iterator_category, but does not create a > class instance. ah yes of course. I misread the typename as typedef, thanks. category is an auto instance. Can it be also written also as a temporary etail::advance_dispatch(i, n, iterator_traits<InputIterator>::iterator_category() ); > > 2. If I am correct, > > the tags are empty structs which I assume allows modern compilers > > (g++4, msvc8/9, intel) to optimize away the creation of that category > > object ? > > This is compiler dependent. ISO C++ 03 standard requires an instance of an > empty type to be at least 1 byte big. To check if that happens read the > documentation to the corresponding compiler. > > 3. If i am still correct, I have a tag which has no members except 1 static > > function that returns void. > > Would that optimization still apply? > > Applies the same as in 2. Whether the compiler prints sizeof(myType) as 1byte or something else has no bearing on whether it doesn't create an instance at runtime, right? need to read their docs (though it's quite hard to see where for g++ for e.g.) thanks very much, regards,

2 1

[BGL] Structure for BFSvisitor is in header file (visitor & property confusion)??
by Trevor Bain 04 Mar '09

04 Mar '09

I have my graph working with BFS, and a BFSvisitor. But, I don't want the BFSvisitor to be in the header file. Since, it is, I have to declare properties I want to use in the visitor, but then I have to pass them in in the constructor for the class that contains the graph and the visitor structure ... Here is my visitor (in .hpp): /* ... other code */ /*! Structure for creating BFSvisitor * * The property maps are being assigned in the constructor for the * Ann object - I don't know how inneficient of a method that is. * i.e. if I should be using references. */ struct propagate_node : public boost::base_visitor<propagate_node> { // getting the dynamically created VoltageMap boost::property_map<Digraph, vertex_voltage_t>::type voltmap; boost::property_map<Digraph, vertex_input_t>::type inputmap; boost::property_map<Digraph, vertex_output_t>::type outputmap; typedef boost::on_discover_vertex event_filter; /* * This is a functor For Breadth First Visit. */ template <class Vertex, class Digraph> void operator()(Vertex v, Digraph& G) { boost::graph_traits<Digraph>::out_edge_iterator ed; // getting the dynamically created VoltageMap && InputMap double volt = boost::get(voltmap, v); bool in = boost::get(inputmap, v); bool out = boost::get(outputmap, v); // mapping sigmoid (don't apply sigmoid to input/output layers) if (in == false && out == false) { // justify this sigmoid ??? volt = 1/(1+pow(MYEXP,-volt)); boost::put(voltmap, v, volt); } if (v != *vertices(G).first) { for ( ed = boost::out_edges(v, G).first; ed != boost::out_edges(v, G).second; ed++) { boost::put( voltmap, target(*ed, G), get(voltmap,target(*ed,G))+get(boost::edge_weight,G,*ed)* volt); } } } } prop; /* ... other code */ So in the c'tor I have to do (in .cpp): /* ... in initializer list */ VoltageMap(get(vertex_voltage_t(), net)), InputMap(get(vertex_input_t(), net)), OutputMap(get(vertex_output_t(), net)), /* ... other code */ prop.voltmap = VoltageMap; prop.inputmap = InputMap; prop.outputmap = OutputMap; to pass my properties from the graph to the visitor ... there has to be a better way to do this. How can I put the visitor definition into the .cpp, and only declare it in the .hpp?

2 2

Tag dispatching
by Hicham Mouline 04 Mar '09

04 Mar '09

Hello, I have a question about tag dispatching (for e.g. the std::advance() function in the std lib, as described for instance in http://www.boost.org/community/generic_programming.html#tag_dispatching) 1. The call to detail::advance_dispatch(i, n, category); I don't understand. category is a type not an object, it should be category(), right? 2. If I am correct, the tags are empty structs which I assume allows modern compilers (g++4, msvc8/9, intel) to optimize away the creation of that category object ? 3. If i am still correct, I have a tag which has no members except 1 static function that returns void. Would that optimization still apply? regards,

2 1

Unhandled exception at 0x781451eb in ********.exe: 0xC0000005: Access violation reading location 0x0129ffff.
by ddribes 04 Mar '09

04 Mar '09

Dear Boost Users, I am new with Boost and I am facing a Unhandled exception. The program I am triying to use is working fine in release mode but crashing in debug mode. Maybe compiler options are not set correctly. Is there something specific for release and/or debug version ? Something to diseable exceptions ? I am working with VStudio 8. I've set the same compiler options for both but I still have the same error. Any ideas ? Thanks, -- View this message in context: http://www.nabble.com/Unhandled-exception-at-0x781451eb-in-********.exe%3A-… Sent from the Boost - Users mailing list archive at Nabble.com.

3 2

[boost-users][bind] binding std::for_each
by Igor R 04 Mar '09

04 Mar '09

Hello, I'd like to bind std::for_each with some other functor created on the fly, like this: struct A { void f(int, int); }; vector<shared_ptr<A> > vec; void f(function<void(void)>); // I want to call f() with a functor that would call A::f for every element in vec f(bind(&for_each, vec.begin(), vec.end(), bind(&A::f, _1, 1))); // doesn't compile f(bind(&for_each, vec.begin(), vec.end(), protect(bind(&A::f, _1, 1)))); // also doesn't compile Thank you.

3 3

1.38 build cmake error
by Randy Heiland 04 Mar '09

04 Mar '09

Hello, Just downloaded 1.38 and trying to use the cmake build. I get my CMakeCache.txt setup the way I want, then: cmake . make sudo make install ... -- Installing: /usr/local/include//boost/xpressive/xpressive_static.hpp -- Installing: /usr/local/include//boost/xpressive/xpressive_typeof.hpp CMake Error at libs/preprocessor/cmake_install.cmake:31 (FILE): file INSTALL cannot find file "/Users/heiland/dev/boost_1_38_0/libs/preprocessor/include/boost" to install. Call Stack (most recent call first): libs/cmake_install.cmake:32 (INCLUDE) cmake_install.cmake:37 (INCLUDE) and sure enough, there's no .../preprocessor/include... heiland@Macintosh:~/dev/boost-build$ ls /Users/heiland/dev/ boost_1_38_0/libs/preprocessor CMakeLists.txt doc/ index.html module.cmake test/ Suggestions? OSX 10.5.6 cmake version 2.6-patch 2 thanks, Randy

2 1

Including a source library with Boost.Build
by Z. S. O. 04 Mar '09

04 Mar '09

I have a source library I'd like to include in my Boost.Build project. The library consists of an assortment of header and cpp files in a folder next to the main cpp file and jamfile. It doesn't require any elaborate precompilation, so it should work just by #including the appropriate header files in the main cpp file (i.e., #include "FolderName/FileName.h"). My question is, do I need to do anything other than that to make this work? I'm getting an "undefined symbols" error, so clearly Boost.Build not finding something correctly.

3 6

boost.serialization, asio and iostreams...
by Hajo Kirchhoff 04 Mar '09

04 Mar '09

(forwarded from asio.user as serialization questions might be more appropriate here) Hi all, I plan to use serialization and asio together to exchange 'command objects' between two applications. Basically marshalling an object and sending it to a remote application. There is a simple asio example using serialization, but there are two issues I'd like to improve. [1] I am concerned about performance. The example constructs and destructs an archive for every single object and uses stringstream, which creates and copies a string object. Wouldn't using asio::tcp::iostreams give better performance? and [2]: I would like to utilize the boost.serialize class registration system to allow peer programmers to create new objects. In the example I would need to send a 'type' and the size manually in a 'header' before I serialize and send the actual object. That would require a system wide enumeration or other 'type' mechanism. My idea is to require all objects be derived from a common polymorphic base and then serialize a pointer to the object. The archive would serialize the entire object and also send type information with it, so the receiver could reconstruct the object simply by receiving a pointer. class basic_command; class my_command:public basic_command; On the senders side: my_command dosomething; archive << &dosomething; On the receiver side: basic_command *next_command; archive >> next_command; next_command->execute(); This would have the benefit that new commands could simply be created by deriving from basic_command. It might also have performance consequences and I have one specific question: For this in order to work I would need to disable tracking for 'my_command'. Otherwise only the very first instance of archive << &dosomething would actually send something. Question: Can I 'reset' the binary archive such that the tracking information is reset, but not the type information? Or can I temporarily disable tracking for a class or for the next save/load operation? I don't want to globally disable tracking for my_command, because I cannot rule out that someone might actually want tracking for their object in a different archive (such as saving settings to disk). I'd love to hear from you and any comments are welcome. Has anyone already done this? What are your experiences? Regards Hajo

2 1