Oops, I was pretty sure there was no ulimit, but I was wrong.
After that the build succeeded, sorry about that.
However, when trying to start sage, it constantly got 'Killed'.
Luckily, I succeeded using the '--nodotsage' option.
Q1: Why does that make such a difference?
Q2: Could sage detect the issue and give a warning ('Killed' was not a good
hint what to look at...)
Jack
Am Mittwoch, 13. August 2014 17:57:15 UTC+2 schrieb Jeroen Demeyer:
>
> On 2014-08-13 17:53, Jakob Kroeker wrote:
> > Any idea what to look at or how to investigate?
> Obviously, look into your memory usage :-)
>
> How much RAM/swap do you have, how much is actually available
> (considering other processes), do you have any limits (see ulimit -a) on
> the allowed memory, are you using too many jobs (make -j1000)...?
>
> Ideally, you should have 2 GB of RAM available to build Sage.
>
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.
