Graph-tool make error
Hello! I'm trying to compile graph-tool on CentOS 5.4 with boost 1.49.0, and I'm getting the following two errors: boost/property_map/property_map.hpp:354: error: no match for 'operator[]' in '(const boost::unchecked_vector_property_map<long double, boost::adj_list_edge_property_map<boost::bidirectional_tag, long unsigned int, long unsigned int&, long unsigned int, boost::property<boost::edge_index_t, long unsigned int, boost::no_property>, boost::edge_index_t> >&)((const boost::unchecked_vector_property_map<long double, boost::adj_list_edge_property_map<boost::bidirectional_tag, long unsigned int, long unsigned int&, long unsigned int, boost::property<boost::edge_index_t, long unsigned int, boost::no_property>, boost::edge_index_t> >*)(& pa))[k]' /homes/spivakov/n/boost_1_49_0/boost/property_map/property_map.hpp:361: error: no match for 'operator[]' in '(const boost::unchecked_vector_property_map<double, boost::adj_list_edge_property_map<boost::bidirectional_tag, long unsigned int, long unsigned int&, long unsigned int, boost::property<boost::edge_index_t, long unsigned int, boost::no_property>, boost::edge_index_t> >&)((const boost::unchecked_vector_property_map<double, boost::adj_list_edge_property_map<boost::bidirectional_tag, long unsigned int, long unsigned int&, long unsigned int, boost::property<boost::edge_index_t, long unsigned int, boost::no_property>, boost::edge_index_t> >*)(& pa))[k]' As I understand, it may be related to a problem with boost library itself (https://bugs.kde.org/show_bug.cgi?id=287772), but I'm wondering if there is any workaround. Many thanks, Mikhail -- Mikhail Spivakov, PhD European Bioinformatics Institute Hinxton, Cambridgeshire, UK
Hi Mikhail, On 04/05/2012 01:49 PM, Mikhail Spivakov wrote:
I'm trying to compile graph-tool on CentOS 5.4 with boost 1.49.0, and I'm getting the following two errors:
[...]
As I understand, it may be related to a problem with boost library itself (https://bugs.kde.org/show_bug.cgi?id=287772), but I'm wondering if there is any workaround.
Yes, there is a problem with boost 1.49. They changed some things which broke compatibility. I'll provide a fix for this soon. In the meantime, you should probably just use boost 1.48. Cheers, Tiago -- Tiago de Paula Peixoto <tiago@skewed.de>
participants (2)
-
Mikhail Spivakov -
Tiago de Paula Peixoto