Modify

Ticket #105 (closed defect: worksforme)

Opened 12 months ago

Last modified 12 months ago

All the dependencies are installed, but make fails when building graph-tool

Reported by: zrbecker@… Owned by: tiago peixoto
Priority: normal Milestone:
Component: graph-tool Version: 2.2
Keywords: Cc:

Description

When building graph-tool, I get a list of long error messages which seem to indicate function definitions are missing or incorrect. I attached a file which contains the stdout and another which contains the stderr.

Attachments

config.out Download (10.0 KB) - added by anonymous 12 months ago.
Output from configure command
config.log Download (91.5 KB) - added by anonymous 12 months ago.
config.log file

Change History

comment:1 in reply to: ↑ description Changed 12 months ago by zrbecker@…

Replying to zrbecker@…:

When building graph-tool, I get a list of long error messages which seem to indicate function definitions are missing or incorrect. I attached a file which contains the stdout and another which contains the stderr.

The error file was too large, so here are what most the errors look like

graph_rewiring.hh:285: error: no match for 'operator[]' in 'edge_index[((boost::iterator_facade<boost::transform_iterator<boost::detail::reverse_graph_edge_descriptor_maker<boost::detail::edge_desc_impl<boost::bidirectional_tag, long unsigned int> >, boost::detail::undirected_edge_iter<std::_List_iterator<boost::list_edge<long unsigned int, boost::property<boost::edge_index_t, long unsigned int, boost::no_property> > >, boost::detail::edge_desc_impl<boost::bidirectional_tag, long unsigned int>, long int>, boost::use_default, boost::use_default>, boost::detail::reverse_graph_edge_descriptor<boost::detail::edge_desc_impl<boost::bidirectional_tag, long unsigned int> >, boost::detail::iterator_category_with_traversal<std::input_iterator_tag, boost::bidirectional_traversal_tag>, boost::detail::reverse_graph_edge_descriptor<boost::detail::edge_desc_impl<boost::bidirectional_tag, long unsigned int> >, long int>*)(& e))->boost::iterator_facade<I, V, TC, R, D>::operator* [with Derived = boost::transform_iterator<boost::detail::reverse_graph_edge_descriptor_maker<boost::detail::edge_desc_impl<boost::bidirectional_tag, long unsigned int> >, boost::detail::undirected_edge_iter<std::_List_iterator<boost::list_edge<long unsigned int, boost::property<boost::edge_index_t, long unsigned int, boost::no_property> > >, boost::detail::edge_desc_impl<boost::bidirectional_tag, long unsigned int>, long int>, boost::use_default, boost::use_default>, Value = boost::detail::reverse_graph_edge_descriptor<boost::detail::edge_desc_impl<boost::bidirectional_tag, long unsigned int> >, CategoryOrTraversal = boost::detail::iterator_category_with_traversal<std::input_iterator_tag, boost::bidirectional_traversal_tag>, Reference = boost::detail::reverse_graph_edge_descriptor<boost::detail::edge_desc_impl<boost::bidirectional_tag, long unsigned int> >, Difference = long int]()]'

Here is a shorter one of the same type

graph_rewiring.hh:253: error: no match for 'operator[]' in 'edge_index[nte]'

Here is a missing function call

/usr/local/include/boost/graph/detail/adjacency_list.hpp:1270: error: no matching function for call to 'boost::bidirectional_graph_helper_with_property<boost::detail::adj_list_gen<boost::adjacency_list<boost::vecS, boost::vecS, boost::bidirectionalS, boost::no_property, boost::property<boost::edge_index_t, long unsigned int, boost::no_property>, boost::no_property, boost::listS>, boost::vecS, boost::vecS, boost::bidirectionalS, boost::no_property, boost::property<boost::edge_index_t, long unsigned int, boost::no_property>, boost::no_property, boost::listS>::config>::remove_edge(boost::detail::reverse_graph_edge_descriptor<boost::detail::edge_desc_impl<boost::bidirectional_tag, long unsigned int> >&)'

Here is the last type of error that I can find.

./../graph_util.hh:203: error: return-statement with a value, in function returning 'void'

comment:2 follow-up: ↓ 3 Changed 12 months ago by tiago peixoto (2)

Please provide sufficient information: What operating system? What compiler? What boost version?

It would be nice if you could provide the whole output of the configure script, as well as the config.log file.

Changed 12 months ago by anonymous

Output from configure command

Changed 12 months ago by anonymous

config.log file

comment:3 in reply to: ↑ 2 Changed 12 months ago by anonymous

Replying to tiago peixoto (2):

Please provide sufficient information: What operating system? What compiler? What boost version?

It would be nice if you could provide the whole output of the configure script, as well as the config.log file.

The OS is Mac OS X Lion Boost is 1.49 Compiler is gcc

I attached the information requested. Sorry for not providing more information.

comment:4 Changed 12 months ago by tiago peixoto (2)

What gcc version do you have? It is apple's or FSF's?

In any case, you should try using the Clang compiler. Apple's GCC is stuck at version 4.2 and is being deprecated. FSF's GCC does not seem to work well on the platform (it compiles graph-tool just fine, but it results in spurious nonsensical segfaults related to exception handling and RTTI). On the other hand, the clang compiler has been reported to work well.

I will mention this in the requirements page.

comment:5 Changed 12 months ago by anonymous

It is apple's 4.2 version. I attempted to use clang, but now it fails to find boost properly. This will be a project for another day since it is late. Thanks for your help.

comment:6 Changed 12 months ago by tiago peixoto (2)

  • Status changed from new to closed
  • Resolution set to worksforme

I recommend you try macports, which has a graph-tool port which works with clang. The advantage is that you don't have to install all dependencies by hand.

I'll close this ticket for now. If you still have problems with a supported compiler, feel free to reopen it.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.