Package Details: python-graph-tool 2.80-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-12-31 10:04 (UTC)

Latest Comments

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

freswa commented on 2013-12-18 17:23 (UTC)

Didn't get your message right. Well yes, this test does not work if there are updates after compilation of graph-tool. But I think it would be a great step forward if we would definitely know at time of compiling whether the build would be successfull. Else we build graph-tool multiple times to get it running. With a test it is one error after any dependency update and after that - one time compile graph-tool. Thats much less work and much less frustrating.

freswa commented on 2013-12-18 17:11 (UTC)

I think a PKGBUILD-buildin check would be better, but since graphtool needs about 45 Minutes to build on a 6 Core HT machine (distributed via distcc) I think it is neccessary to make shure that this build will be successfull now - even if there is a fix in PKBGUILD in the future. As I wrote about a check, I thought of something like this: for i in Dependencies{ Z= pacman -Ql i | grep ".so" X=ldd /usr/lib/$Z | grep "=> not found" if(X is not empty){ print "Package $Z has to be rebuild" } } It's just symbolic code but it may work like this. Also you should interrupt the build process if the loop prints anything... Just my 0,02$

muellner commented on 2013-12-17 17:54 (UTC)

Hi Frederik, what you report is a general problem: when a library is updated, all programs that depend on it need to be recompiled (or re-linked). I tripped over the same issue as you before, but I don't have a good solution. If I include a test in the PKGBUILD for graph-tool, this will only be noticed when graph-tool is compiled. It happens more frequently, however, that CGAL and graph-tool are installed and boost is updated afterwards. There is nothing I can do about it in the AUR package, and yet you will be unable to import the Python module. I believe that this would be a good discussion topic on the Arch Linux forums: suggesting something like a new PKGBUILD variable to indicate library dependencies and to trigger recompilation when a dependency is updated. Regards, Daniel

freswa commented on 2013-12-17 15:54 (UTC)

Hi, may you please provide a check if libCGAL.so is linked against the right libboost_thread.so? If it is linked against a libboost_thread.so, that does not exist anymore, cgal needs to be rebuild. Took me 5 hours of searching, why graph-tool can't load his corelib. Thanks

vtselfa commented on 2013-11-30 17:38 (UTC)

I compiled in a machine with 16GB of ram and 4 cores. With -j4 it started to swap. It needs ~4GB per process to compile. BTW, it crashes with all graphviz related funtions. I think it's because graphviz package is compiled for python2. I tried recompiling graphviz for python3 support but after tunning the ./configure and finnally managing to compile it didn't work.

muellner commented on 2013-11-26 16:10 (UTC)

I compile it on a machine with 8GB RAM and two parallel compiler processes, and on another machine with 16GB and four processes. I recommend using a tool like "top" or "htop" to monitor memory consumption on your computer.

xiongyaohua commented on 2013-11-26 15:35 (UTC)

Hi, muellner Thanks for the instant response. I think you are right. I rebooted into console mode to save memory and disabled the parallel compilation. Now it can go further in the compilation process before the io goes crazy. However it still can not finish. Looks like I need to plug more memory. Could I know how many RAM do you have when compiling this?