You might also check your available disk space : a Sage tree us huge. On Debian, it is a bit more than 8 GB, IIRC ; on Cygwin cygwin's du says it is 9.3 GB, whereas Windows explorer says it is 8.33 GB (using 8.72 GB on disk).
Similarly, check the number of available inodes. HTH, -- Emmanuel Charpentier Le dimanche 21 janvier 2018 11:15:03 UTC+1, Dima Pasechnik a écrit : > > > > On Sunday, January 21, 2018 at 8:58:41 AM UTC, aishen wrote: >> >> Hi, >> >> I used to compiled sage till version 7.0, but now it crashes and halt pc >> at about the compilation of doc (but I think with the last 8.2 beta 3 it >> was before because sage doesn't run). I have an AMD 8core and 16 Go RAM >> ssd 250 Go) ubuntu 17.10 (and 18.04). I guess I haven't enaugh RAM now ? >> > > certainly 16 Gb is more than enough to build Sage. > I guess that you might be trying to do a parallel build, and this somehow > does not work > (I saw systems grinding to a halt if you do something like make -j8 on a > 4-core system). > I suggest that after the building stops you re-run make as follows: > > make -j1 > > This should restart from the place where it stopped, and uses only one > core. > > > > Anyhow, you might also try > > make build > > (this does not build documentation, so the questionable step would be > avoided) > > > >> >> Would it be possible to have a binary somewhere so that it could be >> tested ? >> >> Regards >> >> Henri >> >> >> -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
