On Monday, 20 April 2015 12:10:21 UTC-6, Volker Braun wrote: > > Which build step / which setup.py? Logs? >
I believe it was building Sage itself and getting stuck at rings. Can't provide a log now, will try to run it again overnight and post a log tomorrow. > > On Monday, April 20, 2015 at 12:33:24 PM UTC-4, Andrey Novoseltsev wrote: >> >> Hello, >> >> Up to Sage-6.5 I was able to build it on my old laptop with 2GB RAM. It >> has swap as well, but I don't think it was used much, the wall time was >> just a bit bigger than user+system, about 8-9 hours. >> >> With Sage-6.6 it gets stuck while processing rings directory: swap is not >> full yet, but it seems that necessary stuff does not fit RAM anymore - >> heavy disk usage, low CPU temperature, not much progress after more than a >> day, top was showing "python setup.py" if I recall correctly consuming >> 1.5GB RAM and over 2.5GB virtual memory. This consistent over several >> attempts with "make distclean", with nothing running apart from MATE >> session and a terminal window. >> >> I realize that supporting builds on such computers may not be a high >> priority, if at all, but perhaps it is a manifestation of some bug. >> >> Besides, while 2GB total RAM seems small nowadays, 2GB/core is quite >> common, especially with VMs. (In fact, all physical and virtual machines >> that I use frequently happen to have exactly this number, ranging from >> 2GB/1 core to 32GB/16 cores.) >> >> Thank you, >> Andrey >> > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
