Package Details: python-graph-tool 2.59-2

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-01-05 18:21 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 15 Next › Last »

paulmelis commented on 2018-06-12 08:45 (UTC)

With GCC 8 there's a compile error: https://git.skewed.de/count0/graph-tool/issues/468. Needs the commit mentioned in that issue at the bottom

manuel.osdoba commented on 2018-06-10 12:32 (UTC) (edited on 2018-06-10 12:32 (UTC) by manuel.osdoba)

If your PKGBUILD refers to python-graph-tool 2.26 and you already upgraded to use gcc 8.1.1 then you have to apply the patch https://git.skewed.de/count0/graph-tool/commit/9bd68ef9df7cadb2ca537037a425664ce14dc220.diff

Or you use my compiled packages https://drive.google.com/drive/folders/0B_2Um0ComJq7WUFGdGlRNTB4QW8

count0 commented on 2018-02-22 11:50 (UTC)

@cocconat If boost is updated, the package needs to be recompiled, there is no way around it.

This is not a bug, it is simply how shared libraries work.

cocconat commented on 2018-02-22 11:39 (UTC)

Hi, after boost update to 1.66.0 [1] the python module 'graph_tool' breaks:

ImportError: libboost_iostreams.so.1.63.0: cannot open shared object file

I tried to downgrade boost without success, I tried to update graph-tool, but no update available.

I don't want to disinstall and rebuild couse it requires hours of compilation and my ram prevent me from parallel compilation.

Please help

[1] https://www.archlinux.org/packages/?q=boost

ktw commented on 2017-12-11 15:06 (UTC)

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

lahwaacz commented on 2017-10-29 16:34 (UTC)

@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 (UTC)

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 (UTC)

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 (UTC)

@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 (UTC)

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.

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 15 Next › Last »