Package Details: codeviz 1.0.12-1

Git Clone URL: (read-only)
Package Base: codeviz
Description: A call graph generation utility for C/C++
Upstream URL:
Licenses: GPL2
Submitter: stativ
Maintainer: stativ
Last Packager: stativ
Votes: 3
Popularity: 0.662405
First Submitted: 2010-07-24 18:05
Last Updated: 2016-10-23 18:47

Latest Comments

Herodotus commented on 2016-04-26 00:01

I had a compilation problem, after several hours (!) the build failed with a segmentation fault in libtool:

Also I can't find the email address of the author, otherwise I would have reported the bug. Too bad!

mikulely commented on 2013-12-10 14:01

@stativ thx for your reply,the problem is my tmpfs is 2G. After I set it to 24G, the installation success! :-)

for anyone who have the same problom with me:
Just edit your /etc/fstab and specify the tmpfs size like this

tmpfs /tmp tmpfs nodev,nosuid,size=24G 0 0

stativ commented on 2013-12-10 09:13

mikulely: How large is your /tmp (using df -h)? It is likely that it's half of the available RAM or even less, which would not be enough.

Building something this big in RAM is not a good idea if you don't have lots of memory. Rather than using swap, don't build it in /tmp (or any other RAM-backed mount point). Using swap would make the compilation really slow, even is it was on a very fast SSD.

mikulely commented on 2013-12-10 05:27

Here's `free -h` before I install it:
kcat total used free shared buffers cached
Mem: 3.8G 200M 3.6G 396K 28M 57M
-/+ buffers/cache: 114M 3.7G
Swap: 8.0G 0B 8.0G

I even didi not start a x server in order to reduce mem usage,just compile it with console.But the result is the same.After the failure,I've seem the mem has been used 1.5G.

BTW,even if the compilation need more mem than pyhsical mem,will swap do little help?

stativ commented on 2013-12-09 12:44

Are you sure you are not running out of space? The compilation requires about 3 GB of free space. This may be a problem especially if you are building in tmpfs, because you need some free RAM for the compilation itself, too.

mikulely commented on 2013-12-09 10:10

same error with billy123,and also used makepkg,the error messages are the same.

-DHAVE_CONFIG_H -I. -I. -I../../gcc-4.6.4/gcc -I../../gcc-4.6.4/gcc/. -I../../gcc-4.6.4/gcc/../include -I../../gcc-4.6.4/gcc/../libcpp/include -I../../gcc-4.6.4/gcc/../libdecnumber -I../../gcc-4.6.4/gcc/../libdecnumber/bid -I../libdecnumber ../../gcc-4.6.4/gcc/tree-vect-loop.c -o tree-vect-loop.o
/tmp/ccg3c3oY.s: Assembler messages:
/tmp/ccg3c3oY.s: Fatal error: can't write tree-vect-loop.o: 设备上没有空间
/tmp/ccg3c3oY.s: Fatal error: can't close tree-vect-loop.o: 设备上没有空间
Makefile:1089: recipe for target 'tree-vect-loop.o' failed
make[4]: *** [tree-vect-loop.o] Error 1
make[4]: Leaving directory '/tmp/yaourt-tmp-mike/aur-codeviz/src/codeviz-1.0.12/compilers/gcc-graph/objdir/gcc'
Makefile:5594: recipe for target 'all-stage3-gcc' failed
make[3]: *** [all-stage3-gcc] Error 2
make[3]: Leaving directory '/tmp/yaourt-tmp-mike/aur-codeviz/src/codeviz-1.0.12/compilers/gcc-graph/objdir'
Makefile:19865: recipe for target 'stage3-bubble' failed
make[2]: *** [stage3-bubble] Error 2
make[2]: Leaving directory '/tmp/yaourt-tmp-mike/aur-codeviz/src/codeviz-1.0.12/compilers/gcc-graph/objdir'
Makefile:19928: recipe for target 'bootstrap' failed
make[1]: *** [bootstrap] Error 2
make[1]: Leaving directory '/tmp/yaourt-tmp-mike/aur-codeviz/src/codeviz-1.0.12/compilers/gcc-graph/objdir'
Checking if this is CygWin
Note: This is untested, if building with Cygwin works, please email with
a report
Do not know how to fix this compile error up, exiting...
Makefile:10: recipe for target 'all' failed
make: *** [all] Error 255
==> 错误: 在 build() 中发生一个错误。
==> ERROR: Makepkg was unable to build codeviz.
==> Restart building codeviz ? [y/N]
==> --------------------------------

stativ commented on 2013-11-13 12:20

Well, this is weird. Have your tried building it using makepkg?

billy123 commented on 2013-11-09 01:06

I looked at available space after the error popped up after a very long compilation but I do have enough free space .

stativ commented on 2013-11-08 10:02

It's in the log:
"No space left on device"

You are running out of space, so you need to build on a device with more space or make some more space by removing something.

billy123 commented on 2013-11-07 20:16

Unable to compile. Gives the following error after an attempted compile . Using yaourt on Arch64. How can I get it to compile? Thanks.

duthils commented on 2011-08-09 12:34

Web page back online.

duthils commented on 2011-08-09 02:52

Actually, I could not download the tarball from there either as it points to the same location. I mailed the author.
I extracted the tarball from an OpenSUSE RPM package [1], but it's probably not suitable for this PKGBUILD.


duthils commented on 2011-08-09 02:22

The tarball is not available anymore on this website.
There's another one here :