Whoever reads this... On Jun 4, 9:02 am, Simon King <simon.k...@nuigalway.ie> wrote: > After printing the ":", the memory consumption increased dramatically > (according to "top", ecl has eaten it) and my machine died from > swapping. > > Still unable to build 4.4.2 from sources.
In my first two attempts, I interrupted the build process with Ctrl-c. The third time, I only killed ecl (from "top"). Afterwards, the build process continued -- and apparently it succeeded! I could even use maxima. But manually interrupting ecl is certainly not how building Sage is supposed to work, right? BTW, if the data of my machine are not stated in the install.log that I posted, here they are: > uname -a Linux gauss 2.6.25.18-0.2-default #1 SMP 2008-10-21 16:30:26 +0200 x86_64 x86_64 x86_64 GNU/Linux > cat /etc/issue Welcome to openSUSE 11.0 (X86-64) - Kernel \r (\l). > cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU 6700 @ 2.66GHz ... k...@gauss:~/SAGE/sage-4.4.2> cat /proc/meminfo MemTotal: 2059408 kB MemFree: 1412772 kB Buffers: 11732 kB Cached: 248108 kB ... > gcc --version gcc (SUSE Linux) 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] Copyright (C) 2008 Free Software Foundation, Inc. Cheers, Simon -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
