Package Details: python-graph-tool 2.26-1

Git Clone URL: https://aur.archlinux.org/python-graph-tool.git (read-only)
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: GPL3
Conflicts: python3-graph-tool
Provides: python3-graph-tool
Replaces: python3-graph-tool
Submitter: muellner
Maintainer: count0
Last Packager: count0
Votes: 18
Popularity: 0.019347
First Submitted: 2013-11-24 19:22
Last Updated: 2017-11-09 15:24

Latest Comments

ktw commented on 2017-12-11 15:06

@fortea relevancy aside, thank you! Your solution worked for me

lahwaacz commented on 2017-10-29 16:34

@fortea This is the Arch User Repository, not Manjaro User Repository, so Manjaro-specific problems are not relevant here.

fortea commented on 2017-10-29 16:21

In Manjaro 17.0.6 with Linux 4.11.12-1 and GCC 7.2.0 it fails to compile src/graph/topology/graph_similarity.lo with the message below. I solved using commands from the dockerfile provided by the official developers, so the following:

curl -o PKGBUILD https://aur.archlinux.org/cgit/aur.git/plain/PKGBUILD?h=python-graph-tool

makepkg PKGBUILD --install --needed CXXFLAGS="-mtune=generic -O3 -pipe -flto=4 -ffunction-sections -fdata-sections" LDFLAGS="-Wl,--gc-sections"

______________________________________________________________________________
make[4]: ingresso nella directory "/tmp/pamac-build-sapo/python-graph-tool/src/graph-tool-2.25/src/graph/topology"
CXX graph_similarity.lo
{standard input}: Assembler messages:
{standard input}:618370: Warning: end of file not at end of a line; newline inserted
{standard input}:618850: Error: bad register name `%rd'
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
g++: internal compiler error: Ucciso (program cc1plus)
_______________________________________________________________________________

hasta la victoria,
fortea

ananyab commented on 2017-03-31 13:48

Thank you for confirming it atleast! I was (luckily) able to compile graph-tool with a swap partition in ~110 mins and a peak RAM usage of ~9GB. CPU usage dipped very low during the peak usage, but the compilation pulled through :)
I'm posting my observations here so someone doesn't give up the compilation (if one has 8GB RAM+swap).
And its delightful to know that the RAM usage can and will be reduced, good luck devs!

count0 commented on 2017-03-31 10:30

@ananyab: Memory usage during compilation has spiked in the newest release. This is planned to be improved in the next one.

ananyab commented on 2017-03-31 04:35

Yes, I do compile with `make -j 1` (because that's the default in the PKGBUILD).
I also notice that only one 1 CPU core is used.

lahwaacz commented on 2017-03-30 14:31

@ananyab: Do you compile with "make -j1"? Obviously parallel compilation on N threads takes up to N-times more memory.

ananyab commented on 2017-03-30 14:24

@count0 Is the pre-compiled binary distribution coming?
In your old comment (here, dated 2015-10-27) you mentioned compilation strictly takes below 3GB RAM (along with official wiki), but compilation exceeded 8GB on my i5-7200U 8GB RAM manjaro linux system.

count0 commented on 2017-01-15 19:35

Thanks, Manuel, it is fixed.

manuel.osdoba commented on 2017-01-15 14:52

There is an import issue with latest Python 3.6. Tiago Peixoto fixed that in the python-graph-tool master branch. The extracted patch "0001-Fix-dlopen-flags-problem-with-Python-3.6.patch" on

https://drive.google.com/drive/folders/0B_2Um0ComJq7WUFGdGlRNTB4QW8

fixes that problem.

All comments