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
On Wednesday, August 13, 2014 4:57:15 PM UTC+1, Jeroen Demeyer wrote:
>
> Ideally, you should have 2 GB of RAM available to build Sage.
>
2GB per process if you build with multiple processes (make -j N)
--
You received this message because you are subscribed to the Google Groups
"sage-support
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 y
Hello,
recently I get a MemoryError during build of the develop branch on
'ScientificLinux
6.5, 64 bit', in package
conway_polynomials when runnung ./spkg-install:
Traceback (most recent call last):
File "./spkg-install", line 21, in
create_db()
File "./spkg-install", line 11, in cre
On May 27, 2010, at 11:31 AM, Rolandb wrote:
Hi,
I'm running a routine which uses a large data set (13 million
elements). After a while the output is:
MemoryError
no mem for new parser
What to do? Thanks in advance for the swift reply!
Roland
What are you doing with this data? Do you have a
Hi,
I'm running a routine which uses a large data set (13 million
elements). After a while the output is:
MemoryError
no mem for new parser
What to do? Thanks in advance for the swift reply!
Roland
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this g
