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

Fwd: building cufflinks has compiler error related to boost
by Michael Gooch 15 Jul '11

15 Jul '11

The following error is happening when I try to build cufflinks. I am on Red Hat Enterprise Linux 6.1 and I have installed every boost package available from the RHN repositories. (I would install directly from boost but RHN support is usually anal about using stuff from source when its available from them.) Cufflinks says it uses boost 1.38, and the package version is 1.41, so the version should be adequate. I'm somewhat lost now. This occurred after I noticed some of the pre-bulit binaries had issues with red-hat's version of the z-lib library, so I was trying to see if building the package would interface properly with the included z-lib from redhat, but then I ran into this boost problem. the error: cufflinks.o:(.rodata._ZTIN5boost6detail11thread_dataINS_3_bi6bind_tIvPFvRK16RefSequenceTableP9HitBundleP11BiasLearnereP8_IO_FILESC_SC_ENS2_5list7INS_17reference_wrapperIS5_EENS2_5valueIS8_EENSI_ISA_EENSI_IeEENSI_ISC_EESM_SM_EEEEEE[typeinfo for boost::detail::thread_data<boost::_bi::bind_t<void, void (*)(RefSequenceTable const&, HitBundle*, BiasLearner*, long double, _IO_FILE*, _IO_FILE*, _IO_FILE*), boost::_bi::list7<boost::reference_wrapper<RefSequenceTable const>, boost::_bi::value<HitBundle*>, boost::_bi::value<BiasLearner*>, boost::_bi::value<long double>, boost::_bi::value<_IO_FILE*>, boost::_bi::value<_IO_FILE*>, boost::_bi::value<_IO_FILE*> > > >]+0x10): undefined reference to `typeinfo for boost::detail::thread_data_base' libcufflinks.a(common.o): In function `boost::thread_specific_ptr<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >::~thread_specific_ptr()': common.cpp:(.text._ZN5boost19thread_specific_ptrISsED2Ev[_ZN5boost19thread_specific_ptrISsED5Ev]+0x35): undefined reference to `boost::detail::set_tss_data(void const*, boost::shared_ptr<boost::detail::tss_cleanup_function>, void*, bool)' libcufflinks.a(assemble.o): In function `boost::thread_specific_ptr<std::basic_string<char, std::char_traits<char>, std::allocator<char> > >::get() const': /usr/include/boost/thread/tss.hpp:82: undefined reference to `boost::detail::get_tss_data(void const*)' /usr/include/boost/thread/tss.hpp:82: undefined reference to `boost::detail::get_tss_data(void const*)' /usr/include/boost/thread/tss.hpp:82: undefined reference to `boost::detail::get_tss_data(void const*)' /usr/include/boost/thread/tss.hpp:82: undefined reference to `boost::detail::get_tss_data(void const*)' /usr/include/boost/thread/tss.hpp:82: undefined reference to `boost::detail::get_tss_data(void const*)' libcufflinks.a(assemble.o):/usr/include/boost/thread/tss.hpp:82: more undefined references to `boost::detail::get_tss_data(void const*)' follow collect2: ld returned 1 exit status make[2]: *** [cufflinks] Error 1 M.Gooch

2 1

Lean and mean boost
by Robert Bielik 12 Jul '11

12 Jul '11

Hi all, I'm sitting here developing a build script to automate my build which first of all involves checking out sources, one of which is boost. However, 99.9% of the checkout time is boost tests/documentation/examples and what have you. It would be such a good feature to split out these stuffs so that there is a way to get to the nitty gritty jucy stuff without having to wait half a day... ;) Sorry for kicking in open doors, if that's what I'm doing ? :) Regards /Rob

7 17

Re: [Boost-users] [Asio] Crash on service delete
by Marat Abrarov 09 Jul '11

09 Jul '11

Hi, Indrek. > // m_socket was associated with m_service > m_socket->cancel(); > m_socket->shutdown( boost::asio::ip::tcp::socket::shutdown_both, ec ); > m_socket->close( ec ); > delete m_socket; > m_socket = NULL; > > // Delete work on the service > delete m_work; > m_work = NULL; > > // Stop the service > m_service->stop(); > > // Join the thread this service was running on > m_thread->interrupt(); > m_thread->join(); > delete m_thread; > m_thread = NULL; > > // Crashes here > delete m_service; > m_service = NULL; > > Here's what VC10 reported: > Access violation > camc.exe!boost::asio::detail::socket_ops::send(unsigned int s, const _WSABUF > * bufs, unsigned int count, int flags, boost::system::error_code & ec) Line > 876 + 0x24 bytes C++ > camc.exe!boost::asio::detail::socket_select_interrupter::interrupt() Line > 127 + 0x18 bytes C++ > camc.exe!boost::asio::detail::select_reactor::shutdown_service() Line 73 C++ > camc.exe!boost::asio::detail::service_registry::~service_registry() Line 42 > + 0xf bytes C++ > camc.exe!boost::asio::detail::service_registry::`scalar deleting > destructor'() + 0x16 bytes C++ > camc.exe!boost::asio::io_service::~io_service() Line 51 + 0x1f bytes C++ > camc.exe!boost::asio::io_service::`scalar deleting destructor'() + 0x16 > bytes C++ May be the source of your problem is located in yours async write completion handler (it is often so - see asio-users mailing list). It seems that your completion handler tries to use destroyed m_socket. Regards, Marat Abrarov.

3 5

Boost.Python to-Python converter for class T already registered
by Tyler Weston 04 Jul '11

04 Jul '11

Hi All, I'm integrating a Boost.Python module into a Django project. I'm getting spammed with warnings for duplicate conversion methods. Django uses a multi-process model that loads separate copies of the python module into memory. The module does fine with multiprocess initialization. The warnings occur when, somehow, Django calls __init__ a second time on my module, within the same process. The warnings look like: C:\work\svn\sw\branches\python\imager\__init__.py:1: RuntimeWarning: to-Python converter for class std::vector<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >,class std::allocator<class basic_string<char,struct std::char_traits<char>,class std::allocator<char> > > > already registered; second conversion method ignored. I have a few questions about this, as I am new to python. I thought that modules were supposed to be process-global. How do i enforce this and prevent __init__ from being called twice? Are the warnings benign? Should I be concerned about the state of my library static globals (ie is the compiled code going through a second initialization process)?

2 1

Re: [Boost-users] [review][assign] Formal review of Assign v2 ongoing
by er 02 Jul '11

02 Jul '11

This was posted to lib.boost.devel, but I meant to post it in boost.user as well: > About your other comments: > - operator| has a similar meaning in Boost.Range under adaptors. > - Feel free to suggest another prefix than 'do'. > - Dot is borrowed from Boost.Assign (1.0). Did you mean dot or %? The dot is a small price to pay for alternating between various ways to insert elements in a container, within one statement: put( cont )( x, y, z ).for_each( range1 )( a, b ).for_each( range2 ); The answer to "[Is it] just a quest to type less when using standard containers?" is yes, as illustrated just above, but it is quite a broad definition of standard containers. Version 2.0 provides macros to broaden it further (which was used to support Boost.MultiArray, for example). As for why such a library should exist, it depends on the degree to which you value the syntax above, which is very similar to Boost.Assign (1.0), in this case. You say "I ordinarily only initialize containers to literals when writing unit tests.". In this case, I think you are right that you can't beat C++0x initializer lists. But, you still may need to fill a container, as above. And also, consider the cases below: #include <vector> #include <queue> #include <string> #include <tuple> #include <boost/assign/v2/include/csv_deque_ext.hpp> int main() { typedef std::string s_; { typedef std::tuple<s_, int> t_; typedef std::vector<t_> v_; v_ v1 = { t_( "a", 1 ), t_( "b", 2 ), t_( "c", 3 ), t_( "d", 4 ), t_( "e", 5 ) }; using namespace boost::assign::v2; v_ v2 = converter( csv_deque<t_, 2>( "a", 1, "b", 2, "c", 3, "d", 4, "e", 5) ); } { typedef std::queue<int> q_; // Not aware that an initializer list works here using namespace boost::assign::v2; q_ q = converter( csv_deque<int, 1>( 1, 2, 3, 4, 5 ) ); } return 0; } > - Prefix _ is reserved for const objects (not sure the proper word for it) And I think this convention appears elsewhere in Boost, such as Boost.Parameter. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

4 10

Problem with dijkstra_shortest_paths
by Stephen Woodbridge 01 Jul '11

01 Jul '11

Hi all, I am C programmer floundering in a C++ world! I have the function that I call from C that builds a graph, runs dijkstra_shortest_paths(), then extracts the results and passes them back to a C array of structs. Code is in pastebin: http://pastebin.com/xi7vLpTx This seems to work and everything looks ok, EXCEPT the edge ids are not correct. I suspect this is because I'm not doing something correctly and I have been messing with this for a couple weeks without success, so I think its time to ask for help. So in the function: graph_add_edge(G &graph, int id, int source, int target, float8 cost) id is the edge id source is the node id at the start of the edge target is the node_id at the end of the edge cost is the cost to traverse the edge from source to target I would really appreciate it if someone could look at this and point out what I might be doing wrong. Thanks in advance, -Steve

3 11

Meta State Machine PseudoExit transitions
by Johan Gielens 01 Jul '11

01 Jul '11

Hello, I'm trying to implement a PseudoExitState in my boost meta state machine. This is the situation: http://i55.tinypic.com/2a83yar.png. Currently, when going from Transport to either Situation A or B, it throws an "no_transition" in the SubState for the "convertible event" needed by the PseudoExit state. (This is event6 in the example described below) According to the documentation (http://www.boost.org/doc/libs/1_46_1/libs/msm/doc/HTML/ch03s02.html#d0e930) and the corresponding example, there should be some kind of transition triggered by "event6" from SubState2 to Substate1 (see http://www.boost.org/doc/libs/1_46_1/libs/msm/doc/HTML/examples/DirectEntry…, in the transition table for SubFsm2). I don't see an arrow in the state diagram between SubState2 and SubState1, nor can I figure out why I would want such a transition. In my SubState's transition table, I have defined the transition from Transport to PseudoExit1 and 2: g_row< Transport , Sensor , Exit1 , &SubFront::SDownstreamCheck >, g_row< Transport , Sensor , Exit2 , &SubFront::SDownstreamNoCheck > and in the TopState from PseudoExit1 and 2 to SituationA and B: _row< Sub::exit_pt< SubFront::Exit1 > , TransportDone , SituationA >, _row< Sub::exit_pt< SubFront::Exit2 > , TransportDone , SituationB >, So do i have to handle an "TransportDone" event in the SubState? And what are my Start and End states? I would appreciate your help :) Best Regards, Johan

2 7

[Range] Select forward or reverse traversal at compile time?
by Alastair Rankine 01 Jul '11

01 Jul '11

Given a bidirectional range R, is it possible to select at compile time whether we want to iterate forwards or backwards? Below is a test app. At the commented line, I would like to transparently construct a forward or reverse range, ie either [begin(range), end(range)] or [rbegin(range), rend(range)] respectively, depending on the definition of the Reversed template parameter. Just to be clear, the desired output is: forward: abc reversed: abc I can make this work by using a functor class with partial specialisation to construct the iterator_range, using begin/end or rbegin/rend respectively. But it's a bit ugly and it would seem like something that boost range would provide anyway? (Note that boost::reverse() is NOT what I am after.) #include <boost/assign/list_of.hpp> #include <boost/range/algorithm/copy.hpp> #include <boost/range.hpp> #include <vector> #include <iostream> template <typename Reversed, typename Range> std::string Print(const Range& range) { typedef boost::iterator_range< typename boost::mpl::eval_if< Reversed, boost::range_reverse_iterator<const Range>, boost::range_iterator<const Range> >::type> IterRange; // want to convert it to a forward range here IterRange forwardRange(range); std::string result; boost::copy(forwardRange, std::back_inserter(result)); return result; } int main(int argc, char* argv[]) { using boost::assign::list_of; std::vector<char> a = list_of('a')('b')('c'); std::vector<char> b = list_of('c')('b')('a'); std::cout << "forward: " << Print<boost::mpl::false_>(a) << std::endl << "reversed: " << Print<boost::mpl::true_>(b) << std::endl; return 0; }

3 5

[Graph]questions regarding boost::graph::adjacency_list constructor prototype
by Tan, Tom (Shanghai) 30 Jun '11

30 Jun '11

While studying boost.graph, I stumbled upon this constructor definition: template <class EdgeIterator> adjacency_list(EdgeIterator first, EdgeIterator last, vertices_size_type n, edges_size_type = 0, const GraphProperty& p = GraphProperty()) : Base(n, first, last), m_property(new graph_property_type(p)) { } I have 2 questions here: - What does "edges_size_type = 0," means here? Assigning a value to a TYPE, instead of a parameter? Can anyone please point me to an explanation of this grammar usage? - Why the necessary of edges_size_type = 0 parameter, since there's a range pair of "EdgeIterator first, EdgeIterator last"? Does anyone have an answer? Thanks.

2 1

ptime input_facet error with %f flag at converting string to ptime (1.36, 1.44)
by Sören Freudiger 30 Jun '11

30 Jun '11

Hello I have problems with reading the time fraction at converting from string to ptime. Here is the regarding soruce code: |#include <iostream> #include <string> #include <boost/date_time.hpp> #include <boost/date_time/posix_time/posix_time.hpp> #include <boost/date_time/gregorian/gregorian.hpp> #include <boost/date_time/posix_time/conversion.hpp> int main( int, char * ) { using namespace std; using namespace boost; using namespace boost::posix_time; using namespace boost::local_time; using namespace boost::gregorian; time_facet* output_facet= new time_facet(); time_input_facet* input_facet= new time_input_facet(); stringstream sstream; sstream.imbue(locale(locale::classic(), output_facet)); sstream.imbue(locale(sstream.getloc() , input_facet)); string format("%d/%m/%Y %H:%M:%S.%f"); //example works fine without %f!!! output_facet->format( format.c_str() ); input_facet->format( format.c_str() < /span>); ptime dt= microsec_clock().local_time(); sstream.str(""); sstream<< dt; cout<< sstream.str() << end l; string time_string= sstream.str(); ptime tgtDt( boost::date_time::not_a_date_time); sstream.str( time_string.c_str() ); sstream>> tgtDt; cout<< tgtDt<< endl; }| The program runs fine without the %f inside the format string. But with %f tgtDt is "not-a-date-time". I use boost 1.44 and the doc says %f shold work, because every input incompatible format flag is marked bei "!" in the documentation. Any ideas how to get the frac part out of a string?

1 0