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

BLL trouble
by Persson Jonas 21 May '02

21 May '02

Hello, I've just started playing around with BLL and i have some troubles using it with containers of shared_ptr. I have isolated the problem to: void lambdaTest() { using namespace boost::lambda; boost::shared_ptr<int> x(new int(5)); (*_1)(x); } This does not compile with gcc 3.1 on cygwin. If I use plain pointers it works as expected but not for shared_ptr. What am I doing wrong? / Jonas ---------------------------------------------------------------------------- ---- ../../cygwin/usr/local/include/g++-v3/bits/stl_iterator_base_types.h: In instantiation of `std::iterator_traits<boost::s hared_ptr<int> >': ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: 224: instantiated from `boost::lambda::det ail::contentsof_type<boost::shared_ptr<int> >' ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp:50: instantiated from `boost::lambda::detail::IF_type_<b oost::lambda::detail::contentsof_type<boost::shared_ptr<int> > >' ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp:58: instantiated from `boost::lambda::detail::IF_type<tr ue, boost::lambda::detail::contentsof_type<boost::shared_ptr<int> >, boost::lambda::detail::identity_mapping<boost::lamb da::detail::unspecified> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: 317: instantiated from `boost::lambda::ret urn_type_1<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/return_type_traits.hpp:92: instantiated from `boost::lambda::return_type_1 _prot<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:84 : instantiated from `boost::lambda::detail ::unary_rt<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_fun ctor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boos t::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_ type, boost::tuples::null_type>, boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tuples:: null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:25 3: instantiated from `boost::lambda::lambd a_functor_base<boost::lambda::other_action<boost::lambda::contentsof_action> , boost::tuples::tuple<boost::lambda::lambda _functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::n ull_type, boost::tuples::null_type> >::sig<boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_t ype, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' Main.cpp:150: instantiated from here ../../cygwin/usr/local/include/g++-v3/bits/stl_iterator_base_types.h:123: no type named `iterator_category' in `class boost::shared_ptr<int>' ../../cygwin/usr/local/include/g++-v3/bits/stl_iterator_base_types.h:124: no type named `value_type' in `class boost::shared_ptr<int>' ../../cygwin/usr/local/include/g++-v3/bits/stl_iterator_base_types.h:125: no type named `difference_type' in `class boost::shared_ptr<int>' ../../cygwin/usr/local/include/g++-v3/bits/stl_iterator_base_types.h:126: no type named `pointer' in `class boost::shared_ptr<int>' ../../cygwin/usr/local/include/g++-v3/bits/stl_iterator_base_types.h:127: no type named `reference' in `class boost::shared_ptr<int>' ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: In instantiation of `boost::lambda::detail: :contentsof_type<boost::shared_ptr<int> >': ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp:50: instantiated from `boost::lambda::detail::IF_type_<b oost::lambda::detail::contentsof_type<boost::shared_ptr<int> > >' ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp:58: instantiated from `boost::lambda::detail::IF_type<tr ue, boost::lambda::detail::contentsof_type<boost::shared_ptr<int> >, boost::lambda::detail::identity_mapping<boost::lamb da::detail::unspecified> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: 317: instantiated from `boost::lambda::ret urn_type_1<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/return_type_traits.hpp:92: instantiated from `boost::lambda::return_type_1 _prot<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:84 : instantiated from `boost::lambda::detail ::unary_rt<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_fun ctor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boos t::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_ type, boost::tuples::null_type>, boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tuples:: null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:25 3: instantiated from `boost::lambda::lambd a_functor_base<boost::lambda::other_action<boost::lambda::contentsof_action> , boost::tuples::tuple<boost::lambda::lambda _functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::n ull_type, boost::tuples::null_type> >::sig<boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_t ype, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' Main.cpp:150: instantiated from here ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: 224: no type named `reference' in `struct std::iterator_traits<boost::shared_ptr<int> >' ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp: In instantiation of `boost::lambda::detail::IF_type_<boos t::lambda::detail::contentsof_type<boost::shared_ptr<int> > >': ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp:58: instantiated from `boost::lambda::detail::IF_type<tr ue, boost::lambda::detail::contentsof_type<boost::shared_ptr<int> >, boost::lambda::detail::identity_mapping<boost::lamb da::detail::unspecified> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: 317: instantiated from `boost::lambda::ret urn_type_1<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/return_type_traits.hpp:92: instantiated from `boost::lambda::return_type_1 _prot<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:84 : instantiated from `boost::lambda::detail ::unary_rt<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_fun ctor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boos t::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_ type, boost::tuples::null_type>, boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tuples:: null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:25 3: instantiated from `boost::lambda::lambd a_functor_base<boost::lambda::other_action<boost::lambda::contentsof_action> , boost::tuples::tuple<boost::lambda::lambda _functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::n ull_type, boost::tuples::null_type> >::sig<boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_t ype, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' Main.cpp:150: instantiated from here ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp:50: no type named `type' in `struct boost::lambda::detail::contentsof_type<boost::shared_ptr<int> >' ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp: In instantiation of `boost::lambda::detail::IF_type<true, boost::lambda::detail::contentsof_type<boost::shared_ptr<int> >, boost::lambda::detail::identity_mapping<boost::lambda: :detail::unspecified> >': ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: 317: instantiated from `boost::lambda::ret urn_type_1<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/return_type_traits.hpp:92: instantiated from `boost::lambda::return_type_1 _prot<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:84 : instantiated from `boost::lambda::detail ::unary_rt<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_fun ctor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boos t::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_ type, boost::tuples::null_type>, boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tuples:: null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:25 3: instantiated from `boost::lambda::lambd a_functor_base<boost::lambda::other_action<boost::lambda::contentsof_action> , boost::tuples::tuple<boost::lambda::lambda _functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::n ull_type, boost::tuples::null_type> >::sig<boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_t ype, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' Main.cpp:150: instantiated from here ../../libs/boost_1_28_0/boost/lambda/detail/lambda_traits.hpp:58: no type named `type' in `struct boost::lambda::detail::IF_type_<boost::lambda::detail::contentsof_type<boost ::shared_ptr<int> > >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: In instantiation of `boost::lambda::return_ type_1<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>': ../../libs/boost_1_28_0/boost/lambda/detail/return_type_traits.hpp:92: instantiated from `boost::lambda::return_type_1 _prot<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:84 : instantiated from `boost::lambda::detail ::unary_rt<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_fun ctor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boos t::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_ type, boost::tuples::null_type>, boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tuples:: null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:25 3: instantiated from `boost::lambda::lambd a_functor_base<boost::lambda::other_action<boost::lambda::contentsof_action> , boost::tuples::tuple<boost::lambda::lambda _functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::n ull_type, boost::tuples::null_type> >::sig<boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_t ype, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' Main.cpp:150: instantiated from here ../../libs/boost_1_28_0/boost/lambda/detail/operator_return_type_traits.hpp: 317: no type named `type' in `struct boost::lambda::detail::IF_type<true, boost::lambda::detail::contentsof_type<boost::shared_ptr<int> >, boost::lambda::detail::identity_mapping<boost::lambda::detail::unspecified> >' ../../libs/boost_1_28_0/boost/lambda/detail/return_type_traits.hpp: In instantiation of `boost::lambda::return_type_1_pr ot<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::shared_ptr<int>&>': ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:84 : instantiated from `boost::lambda::detail ::unary_rt<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_fun ctor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boos t::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_ type, boost::tuples::null_type>, boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tuples:: null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:25 3: instantiated from `boost::lambda::lambd a_functor_base<boost::lambda::other_action<boost::lambda::contentsof_action> , boost::tuples::tuple<boost::lambda::lambda _functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::n ull_type, boost::tuples::null_type> >::sig<boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_t ype, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' Main.cpp:150: instantiated from here ../../libs/boost_1_28_0/boost/lambda/detail/return_type_traits.hpp:92: no type named `type' in `struct boost::lambda::return_type_1<boost::lambda::other_action<boost::lambda::cont entsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp: In instantiation of `boost::lambda::detail::u nary_rt<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_functo r<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost:: tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_typ e, boost::tuples::null_type>, boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tuples::nul l_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::t uples::null_type, boost::tuples::null_type, boost::tuples::null_type> >': ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:25 3: instantiated from `boost::lambda::lambd a_functor_base<boost::lambda::other_action<boost::lambda::contentsof_action> , boost::tuples::tuple<boost::lambda::lambda _functor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::n ull_type, boost::tuples::null_type> >::sig<boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost ::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_t ype, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' Main.cpp:150: instantiated from here ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:84 : no type named `type' in `struct boost::lambda::return_type_1_prot<boost::lambda::other_action<boost::lambda: :contentsof_action>, boost::shared_ptr<int>&>' ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp: In instantiation of `boost::lambda::lambda_fu nctor_base<boost::lambda::other_action<boost::lambda::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_fun ctor<boost::lambda::placeholder<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boos t::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_ type, boost::tuples::null_type> >::sig<boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tu ples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >': Main.cpp:150: instantiated from here ../../libs/boost_1_28_0/boost/lambda/detail/operator_lambda_func_base.hpp:25 3: no type named `type' in `class boost::lambda::detail::unary_rt<boost::lambda::other_action<boost::lambda::c ontentsof_action>, boost::tuples::tuple<boost::lambda::lambda_functor<boost::lambda::placeholde r<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type>, boost::tuples::tuple<boost::shared_ptr<int>&, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >' Main.cpp: In function `void lambdaTest()': Main.cpp:150: no match for call to `(const boost::lambda::lambda_functor<boost::lambda::lambda_functor_base<boost::lamb da::other_action<boost::lambda::contentso f_action>, boost::tuples::tuple<boost::lambda::lambda_functor<boost::lambda::placeholde r<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> > >) (boost::shared_ptr<int>&)' ../../libs/boost_1_28_0/boost/lambda/detail/lambda_functors.hpp:142: candidates are: T::sig<boost::tuples::null_type>::type boost::lambda::lambda_functor<Base>::operator()() const [with T = boost::lambda::lambda_functor_base<boost::lambda::other_action<boost::lambda ::contentsof_action>, boost::tuples::tuple<boost::lambda::lambda_functor<boost::lambda::placeholde r<1> >, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type, boost::tuples::null_type> >]

1 0

RE: [Boost-Users] Graphs: vertex_index vs. edge_index
by Siegel, Matthew 20 May '02

20 May '02

Hi Jeremy, Thanks for the quick response. As you may or may not recall from last week, I am having the issue with MSVC++, where I can not put more than one property per edge or vertex when defining the graph, that limits the size of the template expansion. Because of this, I have to use external property maps that I create myself. Therefore I need an edge index map internal to the graph. Currently my workaround is to keep an unsigned integer in my class, that gets incremented until there's a free "slot" for the edge to go into. This is to allow the increment of the unsigned int to roll at maximum value. Here's the way I think it should work. I understand the space issues that most people would be concerned about, however if a property_map of edge_index_t is explicitly given in the list of edge properties when the graph is defined, then the map should be created automatically for me, and if an index is not provided on the add_edge() function, the index is incremented in the same fashion. If I'm explicitly adding the edge_index map to my graph, then the space is of no concern to me. Just a thought . . .thanks again, Matt -----Original Message----- From: Jeremy Siek [mailto:jsiek@cs.indiana.edu] Sent: Monday, May 20, 2002 12:01 PM To: 'Boost-Users(a)yahoogroups.com' Subject: Re: [Boost-Users] Graphs: vertex_index vs. edge_index Hi Matt, On Mon, 20 May 2002, Siegel, Matthew wrote: > Please correct me if I'm wrong. It seems as if a vertex_index gets > assigned to a vertex as it's added to the graph automatically. > However, this doesn't seem to be the case for the edge_index. > > Is this correct?? That is mostly correct. The vertex_index gets assigned automatically for adjacency_list with VertexList=vecS but not with VertexList=listS. You are right about edge_index. > I forsee the following problem. With the graph implemented using a > std::vector for both the vertex list and the edge list, if a vertex is > removed from the graph the index is corrected for the > vertex_descriptor to the new, appropriate index. However, if an edge Right. All vertices are re-indexed, so that after the removal the remaining indices go from 0 to num_vertices-1 > is removed, the index for the edge_descriptor will not be corrected > with the removal of an element in the vector. Also, this causes > headaches when using an external property map. The edge index is > linked directly to a location in my map. > > Any solutions for these problems?? The reason edge_index is not provided automatically is because it takes up space (whereas the vertex_index is does not), and some users are concerned about space issues. Anyways, one possible solution is to somehow make it possible for you to specify some code to be executed when an edge is added or removed from the graph, and this code would adjust the edge indices, and perhaps the external storage too. But before I get ahead of myself, could you describe how you currently work around this problem, and perhaps how you'd like to see it work? Cheers, Jeremy ---------------------------------------------------------------------- Jeremy Siek http://www.osl.iu.edu/~jsiek/ Ph.D. Student, Indiana Univ. B'ton email: jsiek(a)osl.iu.edu C++ Booster (http://www.boost.org) office phone: (812) 855-3608 ---------------------------------------------------------------------- Info: <http://www.boost.org> Wiki: <http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl> Unsubscribe: <mailto:boost-users-unsubscribe@yahoogroups.com> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

1 0

Graphs: vertex_index vs. edge_index
by Siegel, Matthew 20 May '02

20 May '02

Hi, Please correct me if I'm wrong. It seems as if a vertex_index gets assigned to a vertex as it's added to the graph automatically. However, this doesn't seem to be the case for the edge_index. Is this correct?? I forsee the following problem. With the graph implemented using a std::vector for both the vertex list and the edge list, if a vertex is removed from the graph the index is corrected for the vertex_descriptor to the new, appropriate index. However, if an edge is removed, the index for the edge_descriptor will not be corrected with the removal of an element in the vector. Also, this causes headaches when using an external property map. The edge index is linked directly to a location in my map. Any solutions for these problems?? Thanks, Matt

2 1

newbie question
by the_3_project 20 May '02

20 May '02

How do I compile a program that uses the libregex program? It seems that whenever I do this: $ gcc -o te1 te1.cc -lboost_regex I get: ---- /tmp/cc9r42Gv.o: In function `boost::reg_expression<char, boost::regex_traits<char>, allocator<char> >::fail(unsigned int)': /tmp/cc9r42Gv.o(.boost::reg_expression<char, boost::regex_traits<char>, allocator<char> >::gnu.linkonce.t.fail(unsigned int)+0x4e): undefined reference to `boost::bad_expression::bad_expression(basic_string<char, string_char_traits<char>, __default_alloc_template<true, 0> > const &)' /tmp/cc9r42Gv.o: In function `boost::reg_expression<char, boost::regex_traits<char>, allocator<char> >::compile_set_aux(boost::re_detail::jstack<basic_string<char, string_char_traits<char>, __default_alloc_template<true, 0> >, allocator<char> > &, boost::re_detail::jstack<basic_string<char, string_char_traits<char>, __default_alloc_template<true, 0> >, allocator<char> > &, boost::re_detail::jstack<unsigned int, allocator<char> > &, boost::re_detail::jstack<basic_string<char, string_char_traits<char>, __default_alloc_template<true, 0> >, allocator<char> > &, bool, boost::re_detail::_narrow_type const &)': . . . ---- Here is the source to te1.cc ---- #include <iostream> #include <string> #include <boost/regex.hpp> using namespace boost; int main(int argc, char *argv[]) { cmatch what; string str = "XXyX"; regex expression("(\\S\\S){[Ayw]}(\\S)/"); if(regex_match(str,what,expression)) { cout << "what" << endl; } else { cout << "Shit\n"; } return 0; } -------- What am I doing wrong?

3 2

adjacency_list.cpp
by Louis Lavery 20 May '02

20 May '02

Hello, I've bought the book (BGL) and am trying to compile boost_1_27_0/boost/libs/example/adjacency_list.cpp but... ...MSVC6 spits out the dreaded "fatal error C1001: INTERNAL COMPILER ERROR". Intel 5's first (of many) error is e:/boost_1_27_0/boost/detail/iterator.hpp(204) : error: class "std::list<_Ty, _A>::iterator [with _Ty=boost::list_edge<boost::detail::adj_list_gen<boost::adjacency_list<boost ::vecS, boost::listS, boost::undirectedS, boost::property<boost::vertex_ind ex_t, size_t={unsigned int}, boost::property<boost::vertex_color_t, boost::default_color_type, boost::no_property>>, boost::property<boost::edge_name_t, std::string={std::basic_string<char, std::char_traits<char>, std::allocator<char>>}, boost::no_property>, boost::no_property, boost::listS>, boost::listS, boost::vecS, boost::undirectedS, boost::property<boost::vertex_index_t, size_t={unsigned int}, boost::property<boost::vertex_color_t, boost::default_color_type, boost::n o_property>>, boost::property<boost::edge_name_t, std::string={std::basic_string<char, std::char_traits<char>, std::allocator<char>>}, boost::no_property>, boost::no_property, boost::listS>::config::vertex_descriptor={boost::adjacency_list_traits<boost ::vecS, boost::listS, boost::undirectedS>::vertex_descriptor={boost::ct_if_t<boost::adjacency_list _traits<boost::vecS, boost::listS, boost::undirectedS>::is_rand_a ccess={boost::detail::is_random_access<boost::listS>::type={boost::false_typ e}}, size_t={unsigned int}, boost::adjacency_list_traits<boost::vecS, boost::listS, boost::undirectedS>::vertex_ptr={void *}>::type={boost::adjacency_list_traits<boost::vecS , boost::listS, boost::undirectedS>::vertex_ptr={void *}}}}, boost::property<boost::edge_name_t, std::string={std::basic_string<char, std::char_traits<char>, std::allocator<char>>}, boost::no_property>>, _A=std::allocator<boost::list_edge<bo ost::detail::adj_list_gen<boost::adjacency_list<boost::vecS, boost::listS, boost::undirectedS, boost::property<boost::vertex_index_t, size_t={unsigned int}, boost::property<boost::vertex_color_t, boost::default_color_type, boost::no_property>>, boost::property<boost::edge_name_t, std::string={std::basic_string<char, std::char_traits<char>, std::allocator<char>>}, boost::no_property>, boost::no_property, boost::listS>, boost::listS, boost::vecS, boost::undirectedS, boost::property <boost::vertex_index_t, size_t={unsigned int}, boost::property<boost::vertex_color_t, boost::default_color_type, boost::no_property>>, boost::property<boost::edge_name_t, std::string={std::basic_string<char, std::char_traits<char>, std::allocator<char>>}, boost::no_property>, boost::no_property, boost::listS>::config::vertex_descriptor={boost::adjacency_list_traits<boost ::vecS, boost::listS, boost::undirectedS>::vertex_descriptor={boost::ct_if_t<boost::adjacency_list _traits<boost::vecS, boost::listS, boost::undirectedS>::is_rand_access={boost::detail::is_random_access<boost:: listS>::type={boost::false_type}}, size_t={unsigned int}, boost::adjacency_list_traits<boost::vecS, boost::listS, boost::undirectedS>::vertex_ptr={void *}>::type={boost::adjacency_list_traits<boost::vecS, boost::listS, boost::undirectedS>::vertex_ptr={void *}}}}, boost::property<boost::edge_name_t, std::string={std::basic_string<char, std::char_traits <char>, std::allocator<char>>}, boost::no_property>>>]" has no member "difference_type" typedef typename Iterator::difference_type difference_type; My last hope gcc 2.95.2 comes up with... In file included from e:\boost_1_27_0\boost\detail\numeric_traits.hpp:69, from e:\boost_1_27_0\boost\counting_iterator.hpp:57, from e:\boost_1_27_0\boost\pending\integer_range.hpp:15, from e:\boost_1_27_0\boost\graph\detail\adjacency_list.hpp:34, from e:\boost_1_27_0\boost\graph\adjacency_list.hpp:293, from adjacency_list.cpp:31: e:\boost_1_27_0\boost\cstdint.hpp:163: parse error e:\boost_1_27_0\boost\cstdint.hpp:171: #error defaults not correct; you must hand modify boost/cstdint.hpp I'd like to get it working with MSVC6 or Intel5. Any help much appreciated. Louis.

3 4

BLL for other compilers than GCC and Kai C++
by tslettebo1 19 May '02

19 May '02

Hi all. Have anybody got the Boost Lambda Library to work on other compilers than GCC and Kai C++ (which are mentioned in the documentation)? I have Intel C++ 6.0, which is quite standards compliant, but I get a zillion error messages, just by trying to compile boost/libs/lambda/test/bind_tests_simple.hpp. Trying it with MSVC 6.0 gives an ICE, but that's hardly unexpected. :) Also, are there any plans, on ongoing work, to make it more portable? (I post here, rather than the Boost list, as it's about use of a library) Regards, Terje

1 0

Boost threads compile with Sun WS6U2?
by NYSSEN Peter (BMB) 18 May '02

18 May '02

Hi all, I'm working on a multithreaded application on Sun Solaris 8 with Sun Workshop 6 update 2 installed. Currently my application uses the pthreads library. I've been looking at the Boost.threads library and I would like to use this instead of pthreads. I see that the Sun WS compiler is not in the supported toolsets list and there is no appropriate jam file available. In the Compiler Status: solaris page I see that this compiler is being tested, but no refference to the threads lib. Can anybody point me in the right direction as how I should build this lib in my environment? Is it enough if I try to create a jam file? Has anybody already done this (preferably for release 1_28)? What is the reason this compiler is not in the supported toolsets list? Kind regards, Peter Nyssen **** DISCLAIMER **** "This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the recipient(s) named above. Any use of the information contained herein (including, but not limited to, total or partial reproduction, communication or distribution in any form) by other persons than the designated recipient(s) is prohibited. If you have received this e-mail in error, please notify the sender either by telephone or by e-mail and delete the material from any computer". Thank you for your cooperation. For further information about Proximus mobile phone services please see our website at http://www.proximus.be or refer to any Proximus agent.

3 2

Graph: Multiple edge properties with MSVC
by Siegel, Matthew 18 May '02

18 May '02

Hi, First off . . . great graph library. I can not get Visual C++ 6 SP5 to compile when I try to put multiple properties on the edges. Seems like a problem with the 3rd parameter that a boost::property can take another boost::property. When the 2nd property is taken out of the edge property list, everything works fine. Thanks for the help! Matt Example: // Vertex property - name as a string typedef boost::property<boost::vertex_name_t, std::string> VertexProperties; // Edge property - name as string, weight as a double typedef boost::property< boost::edge_weight_t, double, boost::property< boost::edge_name_t, std::string> > EdgeProperties; // Graph definition typedef boost::adjacency_list< boost::vecS, // Store out-edges in a std::vector boost::vecS, // Store vertex set in a std::vector boost::directedS, // Graph is directed VertexProperties, // Vertex properties EdgeProperties> Graph; // Edge properties Produces the following compiler error: Compiling... routetable.cpp c:\dev\lib\stlport-4.5.3\stlport\stl\char_traits.h(138) : fatal error C1001: INTERNAL COMPILER ERROR (compiler file 'msc1.cpp', line 1794) Please choose the Technical Support command on the Visual C++ Help menu, or open the Technical Support help file for more information Error executing cl.exe. routing.exe - 1 error(s), 0 warning(s)

3 2

Boost in Visual C++ 6.0
by imi123_1999 17 May '02

17 May '02

I am a newbie so please help me a little. I am using Visual C++ 6.0 in order to compile a program given as an example of threads. I am also copying the program below. But the problem is that the program is giving errors of unresolved externals. Please tell me how to change the settings of VC++ options. Here is the program: #include <boost/thread/thread.hpp> #include <iostream> int count = 0; boost::mutex mutex; void increment_count() { boost::mutex::lock lock(mutex); std::cout << "count = " << ++count << std::endl; } int main(int argc, char* argv[]) { boost::thread_group threads; for (int i = 0; i < 10; ++i) threads.create_thread(&increment_count); threads.join_all(); } The errors i am getting are: C:\Windows\Desktop\threadImI\imi.cpp(9) : error C2039: 'lock' : is not a member of 'mutex' c:\program files\microsoft visual studio\vc98 \include\boost\thread\mutex.hpp(35) : see declaration of 'mutex' C:\Windows\Desktop\threadImI\imi.cpp(9) : error C2065: 'lock' : undeclared identifier C:\Windows\Desktop\threadImI\imi.cpp(9) : error C2146: syntax error : missing ';' before identifier 'lock' C:\Windows\Desktop\threadImI\imi.cpp(19) : warning C4508: 'main' : function should return a value; 'void' return type assumed Error executing cl.exe. Creating browse info file... threadImI.exe - 3 error(s), 3 warning(s)

2 4

RE: [Boost-Users] Boost threads compile with Sun WS6U2?
by schalk_cronje＠nai.com 17 May '02

17 May '02

> I'm working on a multithreaded application on Sun Solaris 8 with Sun > Workshop 6 update 2 installed. > Currently my application uses the pthreads library. > I've been looking at the Boost.threads library and I would like to use > this instead of pthreads. We use it with suncc and build it from a makefile. (We don't actually build any of the boost libs using Jam).

1 0

Call for Volunteers
by William E. Kempf 16 May '02

16 May '02

The Boost-install mail list is up and running (http://lists.boost.org/mailman/listinfo.cgi/boost-install to subscribe), and several people have subscribed. However, traffic is non-existent on the list. I'm concerned that the effort will die if we don't start some momentum. Currently, I have 4 people who volunteered to help with this effort. Hopefully these volunteers are just pressed for time right now and will start contributing shortly, but in any event we need more volunteers. So, I'm calling on people once again. The goal is to create a set of procedures for both the Boost developers and the Boost "installers" that will facilitate the creation of an installation "script" or set of "scripts" for supported platforms. The volunteers will help to define the procedures and to implement the "script(s)" for the target platforms so that Boost users can easily install Boost for use. We need volunteers with a lot of different qualifications. We need someone familiar with every supported platform (I don't mean that a single volunteer needs to know every platform) so that we can insure we define the procedures correctly and can provide an installation solution for every platform. We need people to help us document the procedures and to code the "script(s)". If you're interested in helping with this effort, please join the Boost-install list and let us know how you'd like to contribute. Thanks, Bill Kempf

1 0

Boost 1.28.0 released
by Beman Dawes 16 May '02

16 May '02

Boost release 1.28.0 is available. See the www.boost.org home page for news of what's in the release, how to download, and how to build. (Remember that only the Python, Regex, and Thread libraries currently require a build; the others are entirely implemented in the headers.) This is a major release, with both new libraries and lots of general improvements. Much effort has gone into smoothing out the build process for those who use the Python, Regex, and Thread libraries. Among other changes, the release .zip and .tar.gz files are being built via a new procedure, using CVS export. Please let me know right away if you have any problems with either file. --Beman

1 0

RE: [Boost-Users] unit testing framework for c++ in boost?
by bjorn.karlsson＠readsoft.com 16 May '02

16 May '02

Parts of this thread is becoming OT. It's fine to discuss libraries outside of Boost for comparison with their Boost equivalents, but the main topic must be about Boost. Bjorn Karlsson Moderator [Non-text portions of this message have been removed]

1 0

unit testing framework for c++ in boost?
by srivatsan raghavan 16 May '02

16 May '02

anyone know if there are plans to write a unit testing framework in boost? i've checked out unit++ , the interface doesn't seem very intuitive, and it seems rather feature limited and i kinda like CppUnit, but i get the feeling that since it's very similar to JUnit's interface, it's not as c++ friendly as it could be .. anyone know? __________________________________________________ Do You Yahoo!? LAUNCH - Your Yahoo! Music Experience http://launch.yahoo.com

6 6

boost::shared_ptr and NULL
by Andrew R. Thomas-Cramer 14 May '02

14 May '02

In this function declaration, is there a simpler way to express a null shared pointer as the default argument value? void foo( const boost::shared_ptr<T> & p = boost::shared_ptr<T>( ) ); In this function call, is there a simpler way to express a null shared pointer as the actual argument? foo( boost::shared_ptr<T>( ) ); ----------------------------------------------------------------------- Andrew R. Thomas-Cramer Work: artc(a)prism-cs.com http://www.prism-cs.com/ Home: artc(a)execpc.com http://www.execpc.com/~artc/ ----------------------------------------------------------------------- [Non-text portions of this message have been removed]

3 6

Building regex - VC6 SP5 + stlport
by boolean_dream 14 May '02

14 May '02

Hey all, In the past I've had no problems building with this combo, but recently did a system reinstall and got the latest versions and am having trouble. Using: - Boost 1.27.0 - VC6 with SP5 - STLport 4.5.3 STLport is in the INCLUDE and LIB variables as instructed and to complie I just type nmake vc6-stlport.mak from libs\regex\build. After a lot of sutff compling fine I get the below error... I was actually able to fix it by adding in some ifdefs in regex.hpp, but that caused some other problems - clearly I'm doing something wrong. Any ideas? Many thanks. cl /nologo /MTd /W3 /Gm /EHa /Zi /Od /I..\..\..\ /DWIN32 /D_MT /D_DE BUG /D_MBCS /D_LIB /YX /FD /GZ /c -Fpvc6-stlport/vc6-stlport- re300dm/vc6-stlport- re300dm.pch -Fo./vc6-stlport/vc6-stlport-re300dm/ -Fdvc6-stlport/vc6- stlport-re3 00dm.pdb ../src/cregex.cpp cregex.cpp ..\..\..\boost/regex.hpp(402) : error C2011: 'regex_iterator_traits<char *>' : ' struct' type redefinition ..\..\..\boost/regex.hpp(404) : error C2011: 'regex_iterator_traits<char const * >' : 'struct' type redefinition ..\..\..\boost/regex.hpp(407) : error C2011: 'regex_iterator_traits<unsigned sho rt *>' : 'struct' type redefinition ..\..\..\boost/regex.hpp(409) : error C2011: 'regex_iterator_traits<unsigned sho rt const *>' : 'struct' type redefinition NMAKE : fatal error U1077: 'cl' : return code '0x2' Stop.

2 1

boost::shared_ptr<const T>
by Andrew R. Thomas-Cramer 13 May '02

13 May '02

Is it legal to construct a boost::shared_ptr<const T> from a raw T*? On MSVC6, it produces errors when class T has an implicit destructor, but compiles without error otherwise. ----------------------------------------------------------------------- Andrew R. Thomas-Cramer Work: artc(a)prism-cs.com http://www.prism-cs.com/ Home: artc(a)execpc.com http://www.execpc.com/~artc/ ----------------------------------------------------------------------- [Non-text portions of this message have been removed]

2 3

Re: building Boost using Jam
by jd.schmidt＠juno.com 13 May '02

13 May '02

OK, so I invoked Jam from my Boost root directory using: c:\boost_1_27_0\boost-build\jam -sBOOST_ROOT=. -sTOOLS="msvc" Now Jam is actually doing something, but I'm still getting messages like: The system cannot find the specified path. C:\Program is not recongnized as an internal or external command, operable program or batch file Also, I get a lot of messages like: ...found 1606 targets... ...updating 381 targets... [many other messages] ...failed msvc-C++-action [many other messages] ...failed updating 168 targets... ...skipped 202 targets... ...updated 11 targets... Obviously some things are happening, but I get the idea that it didn't work 100%. Do you have any advice? ________________________________________________________________ GET INTERNET ACCESS FROM JUNO! Juno offers FREE or PREMIUM Internet access for less! Join Juno today! For your FREE software, visit: http://dl.www.juno.com/get/web/.

5 4

Re: new boost.jam prebuilt's are available
by Jon Scobie 13 May '02

13 May '02

Toon, got jam to build from the latest CVS thanks but the libraries just refuse to build with vacpp. I started fixing some of the headers but have become stumped at these :- (this is just an excerpt) "./boost/regex.hpp", line 529.13: 1540-1628 (S) Every template parameter for a c onstructor template must be used in the parameter list of the constructor. "./boost/regex/detail/instances.hpp", line 104.10: 1540-0120 (S) The out of line member definition "boost::reg_expression<char,boost::regex_traits<char>,boost:: detail::allocator<char> >" of an explicit specialization should not use a templa te prefix. "./boost/regex/detail/instances.hpp", line 105.10: 1540-0120 (S) The out of line member definition "boost::reg_expression<char,boost::regex_traits<char>,boost:: detail::allocator<char> >" of an explicit specialization should not use a templa te prefix. "./boost/regex/detail/instances.hpp", line 106.10: 1540-0120 (S) The out of line member definition "boost::reg_expression<char,boost::regex_traits<char>,boost:: detail::allocator<char> >" of an explicit specialization should not use a templa te prefix. "./boost/regex/detail/instances.hpp", line 107.10: 1540-0120 (S) The out of line member definition "boost::reg_expression<char,boost::regex_traits<char>,boost:: detail::allocator<char> >" of an explicit specialization should not use a templa te prefix. Is boost completely broken on AIX vacpp v5.0.2? Jon. --- Toon Knapen <toon.knapen(a)si-lab.com> wrote: > You can find the new links in the CVS on the RC_1_28_0 branch. The difference > > is that this time, they point to a bjam.gz (remark the leading `b`) instead > of jam.gz. > __________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com

2 1

Boost 1.27.0 on AIX 4.3.3
by scobiej 13 May '02

13 May '02

Hi, I've looked at all the documentation I can find on building boost on AIX for vacpp. However, I just can't get it to build! I'm using the prebuilt jam executable (not the one I built myself as it doesn't work - yacc stack overflow problems) and this is what I get :- bash-2.01$ jam -sBOOST_ROOT=. -sTOOLS="vacpp" status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:205: in link-fail status/Jamfile:237: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:205: in link-fail status/Jamfile:238: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:293: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:294: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:295: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:296: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:297: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:298: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:299: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:205: in link-fail status/Jamfile:300: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:197: in run-fail status/Jamfile:305: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:332: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:347: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:348: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope status/Jamfile:53: in failed-test-file warning: unknown rule FAIL_EXPECTED status/Jamfile:100: in fail-to-build ./tools/build/boost-base.jam:1407: in subvariant-target ./tools/build/boost-base.jam:1448: in main-target ./tools/build/boost-base.jam:1065: in declare-local-target status/Jamfile:35: in boost-test status/Jamfile:119: in compile-fail status/Jamfile:368: in SubInclude ./tools/build/allyourbase.jam:1141: in subinclude Jamfile:5: in module scope Unable to load Boost.Build, it seems that the build system files were located, but the build system is not defined. Attempted to use, as the bootstrap, this file: ./tools/build/boost-build.jam. This means that even though that file was loaded it either failed to directly load the build system files, or it failed to specify where to find and load the files by calling the 'build-system [path] ;' rule. Please consult the documentation at 'http://www.boost.org'. bash-2.01$ Any help would be appreciated! Thanks, Jon.

4 3

Boost.Thread (VC specific)
by judoka1981 13 May '02

13 May '02

Hi, would there be any problem in generating a .pdb file for libboost_thread? I'm using Boost 1.27.0 and VC.NET. Also, would it be possible to switch on generation of debug information for release builds as well? Regards // Johan

5 11

RE: [Boost-Users] Re: building Boost using Jam
by Tom Matelich 10 May '02

10 May '02

>Don't know which version of boost jam you are using, the version I'm >using does not support windows long file names with spaces so >virtually all targets fail due to bad include paths, and I decided >not to hack my VC installation just to let JAM build. So use the short names. It's a bit of pain to track them down, but they don't have any spaces.

3 2

RE: [Boost-Users] Re: building Boost using Jam
by Tom Matelich 10 May '02

10 May '02

For cvs, I use WinCVS. Best gui I've seen. www.cvsgui.org -----Original Message----- From: dmarsh26us [mailto:david.marsh10@ntlworld.com] Sent: Friday, May 10, 2002 9:57 AM To: Boost-Users(a)yahoogroups.com Subject: [Boost-Users] Re: building Boost using Jam Any general tips on general open source use, would be good also if you have a moment. For example are there better enviroments for a Win 2k setup? Should I use GCC instead? Where can I get a Win 2k version of cvs for source forge? The boost site is a bit light on help for us newbies! Have 6 years C++ but mainly on windows ;)

1 0

prebuild jam-exec's
by Toon Knapen 10 May '02

10 May '02

As previously only posted to the boost-ml (and not the boost-users-ml), the current prebuild jam-execs are not compatible with old revisions of boost nor can they compile the current CVS due to many usefull updates in boost.jam which will ease building boost in the future. There has been a lot of hard work done by David, Rene and Vladimir to have a stable boost.build for building the upcoming Version_1_28 of boost. On monday, updates of the prebuild exec's will be made available through the boost website. Until then, you can compile your own jam executable by just doing a`make YYACC=` in the tools/build/jam_src subdirectory of boost.

1 0

Smart pointers and overloading
by artc_prismcs 10 May '02

10 May '02

The marked call in the code below requires implicit conversion between compatible shared pointer types. At least two compilers (MSVC6 and Sun Workshop6) consider the marked call ambiguous. Remove the second overloaded() function, and the marked call is compiled without error. Replace all the shared pointers by raw, and all three calls to the overloaded methods would be resolved correctly. Is this a shortcoming of the compilers, boost::shared_ptr or the language? #include <boost/shared_ptr.hpp> class MyType { }; class DerivedType : public MyType { }; class OtherType {}; void overloaded( const boost::shared_ptr<MyType> & p ) {} void overloaded( const boost::shared_ptr<OtherType> & p ) {} int main() { boost::shared_ptr<MyType> pm( new MyType() ); boost::shared_ptr<DerivedType> pd( new DerivedType() ); boost::shared_ptr<OtherType> po( new OtherType() ); overloaded( pm ); overloaded( pd ); // Compilers complain of ambiguous call to overloaded function. overloaded( po ); return 0; }

2 1