4

While Compiling graph-tool the gcc-compiler consumes more than 7 Gb of memory and after consuming more and more nothing happens anymore and I am forced to stop the compilation. I tried to embed a compiler suffix:

CFLAGS="$CFLAGS --param ggc-min-expand=0 --param ggc-min-heapsize=8192"

but I wasnt able to bring it into the ./configure procedure. Anyone knows of this issue? (It shouldn't make a difference but my OS is Archlinux-64)

Edit (1): I was able to add now the CFLAGS to configure, but it continues to consume an infinite number of memory. My Gcc Version is 4.8.2!

Edit (2): New Version of graph-tool (2.2.28) solved my problem because they fixed this memory issue!!

EdChum
  • 376,765
  • 198
  • 813
  • 562
varantir
  • 6,624
  • 6
  • 36
  • 57
  • You can tell `configure` to call the C compiler with specific options by setting the `CFLAGS` environment variable like this: `./configure CFLAGS="-foo bar --baz"` –  Nov 24 '13 at 10:06
  • 1
    which version of gcc are you using? – friol Nov 24 '13 at 10:07
  • Did you try to force the virtual memory usage, with something like: ulimit -v vmemsize – friol Nov 24 '13 at 11:55
  • friol: Yes I did, but He just tells me then that not enough memory is available for compiling! – varantir Nov 24 '13 at 18:44
  • Just to note, because graph-tool uses lots of metaprograming (template classes), it does a lot during compile time, and is fast on runtime. I'm just confirming that the amount of memory you are observing that the gcc is taking, is normal, and it's what it is on all the systems. That's why they have binaries for many distros, cause if you want to compile it for yourself, you need that amount of memory. – adrin Jan 12 '14 at 22:03
  • Are you doing any parallel building (`make -j`)? – Vinícius Gobbo A. de Oliveira Jan 13 '14 at 14:03

1 Answers1

1

7 GB is too much... You should need around 4 GB with GCC 4.8. Could it be you are compiling in parallel (with make -j)?

Tiago Peixoto
  • 5,149
  • 2
  • 28
  • 28