Package Details: python-graph-tool 2.79-1

Git Clone URL: https://aur.archlinux.org/python-graph-tool.git (read-only, click to copy)
Package Base: python-graph-tool
Description: A Python module for manipulation and statistical analysis of graphs
Upstream URL: https://graph-tool.skewed.de
Keywords: graphs networks science
Licenses: LGPL3
Conflicts: python3-graph-tool
Provides: python3-graph-tool
Replaces: python3-graph-tool
Submitter: muellner
Maintainer: count0
Last Packager: count0
Votes: 29
Popularity: 0.000000
First Submitted: 2013-11-24 19:22 (UTC)
Last Updated: 2024-10-27 09:12 (UTC)

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 Next › Last »

mat69 commented on 2015-12-27 17:02 (UTC)

Hi, the package does not compile for me anymore. I guess this has to do with boost 1.6. The compile error is: graph_hits.cc: In function ‘long double hits(graph_tool::GraphInterface&, boost::any, boost::any, boost::any, double, size_t)’: graph_hits.cc:71:44: error: reference to ‘placeholders’ is ambiguous (g, std::bind(get_hits_dispatch(), placeholders::_1, g.get_vertex_index(), ^ In file included from /usr/include/boost/bind/bind.hpp:2247:0, from /usr/include/boost/bind.hpp:22, from /usr/include/boost/python/exception_translator.hpp:10, from /usr/include/boost/python.hpp:28, from graph_hits.cc:20: /usr/include/boost/bind/placeholders.hpp:30:1: note: candidates are: namespace boost::placeholders { } { ^ In file included from /usr/include/c++/5.3.0/memory:79:0, from /usr/include/boost/config/no_tr1/memory.hpp:21, from /usr/include/boost/get_pointer.hpp:14, from /usr/include/boost/python/object/pointer_holder.hpp:11, from /usr/include/boost/python/to_python_indirect.hpp:10, from /usr/include/boost/python/converter/arg_to_python.hpp:10, from /usr/include/boost/python/call.hpp:15, from /usr/include/boost/python/object_core.hpp:14, from /usr/include/boost/python/object.hpp:9, from ./../graph.hh:23, from ./../graph_filtering.hh:21, from graph_hits.cc:18: /usr/include/c++/5.3.0/functional:776:3: note: namespace std::placeholders { } {

count0 commented on 2015-10-27 06:53 (UTC)

I also would welcome a binary package! I would like to point out that the soon-to-be-released version 2.11 manages to reduce the compile time and memory usage substantially, due to some useful C++14 features. It now uses strictly under 3GB with GCC during compilation, and takes around ~75 mins to finish with "make -j1". It is not quite a lightweight compilation, but it is an improvement.

guiniol commented on 2015-10-22 10:52 (UTC)

Definitely interested in a binary package. Especially after having to recompile it because boost was updated.

muellner commented on 2015-10-19 20:39 (UTC)

I share jg-you's desire for a binary package - the compilation process is really straining all resources (CPU + patience). The easiest way to get binary packages would be if graph_tool became elevated from AUR to the community repository. I'll try to bring this up in the right place in the next few days. News will get posted here... In the meantime, feel free to write me a message if you'd welcome a precompiled package, so that I have an estimate when arguing how many users will benefit from it.

jg-you commented on 2015-10-16 03:33 (UTC)

Would there be a way to distribute this package precompiled? This is starting to get out of hand: Making package: python-graph-tool 2.10-1 (Thu Oct 15 14:03:42 EDT 2015) Finished making: python-graph-tool 2.10-1 (Thu Oct 15 23:20:40 EDT 2015) On a i5 2GHz, 4GB machine DDR3 machine.

count0 commented on 2015-09-17 21:53 (UTC)

Just a heads-up that version 2.7 is out. Note the different (simpler) version scheme.

arefindk commented on 2015-05-08 18:47 (UTC)

Thank you @muellner, rebuilding works.

muellner commented on 2015-04-19 19:25 (UTC)

When CGAL is updated, you also need to rebuild graph_tool so that it links to the new library files. The package (source + PKGBUILD) itself is probably fine. Let me know if rebuilding doesn't help. (This applies to all dependencies. Eg. if there is a new version of Boost, you should rebuild graph_tool. Unfortunately, there is no mechanism that I know about that does detect those situations automatically.)

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 Next › Last »