On Oct 9, 2013, at 13:24 , Jeroen Demeyer wrote:
> Sage 5.12 was released on 07 October 2013. It is available in
> source and binary form from:
>
> * http://www.sagemath.org/download.html
Built w/o problems on two Mac OS X systems. On both (10.6.8 (Dual 6-core
Xeons) and 10.8.5 (Quad Core i7
Thanks!
Hopefully youll find what the real problem was.
On Thursday, October 10, 2013 8:00:52 PM UTC+2, Keith Clawson wrote:
>
> Trac is back up. Something causes Trac to use nearly 100% CPU and memory
> after running for a few weeks, and eventually it becomes impossible to ssh
> into the VM run
Trac is back up. Something causes Trac to use nearly 100% CPU and memory
after running for a few weeks, and eventually it becomes impossible to ssh
into the VM running it. For the time being I'll put a monitor on Trac's
memory use and try to restart it before it gets to the point of locking up.
On Thursday, October 10, 2013 2:21:43 AM UTC-7, Jean-Pierre Flori wrote:
>
>
>
> On Thursday, October 10, 2013 11:19:01 AM UTC+2, Jean-Pierre Flori wrote:
>>
>> I guess http://trac.sagemath.org/ticket/15080 takes care of this?
>>>
>>>
>>> Yes, that works! I did "sage -i " and that solved
the prob
Another thing to try might have been "export SAGE_BINARY_BUILD='yes'". I've
had to use this setting on some OS X machines before.
John
On Thursday, October 10, 2013 7:23:56 AM UTC-7, Andrew Mathas wrote:
>
> Excellent! Thank you Jean-Pierre, this worked (or at least the compile is
> now in
Excellent! Thank you Jean-Pierre, this worked (or at least the compile is
now in full swing again).
Andrew
...
real 14.882user 12.442sys 1.752pcpu 95.38
Successfully installed pil-1.1.6.p4
Deleting temporary build directory
/usr/local/src/sage/sage-5.12/spkg/build/pil-1.1.6.p4
Finis
On Thursday, October 10, 2013 4:15:30 PM UTC+2, Jean-Pierre Flori wrote:
> I think I used to have the same problem on exotic archs where I did not
> have libjpeg installed.
>
Or at least the devel files.
So if you can install the equivalent of libjpeg-devel on your distrib, PIL
should compile
On Thursday, October 10, 2013 4:13:36 PM UTC+2, Andrew Mathas wrote:
>
> I'm having trouble compiling 5.12. Sage build to the extend that I get an
> executable which runs, but the compile fails to compile pil-1.1.6.p4 and
> exits with the error from the end of the log file is below. It's a bi
I'm having trouble compiling 5.12. Sage build to the extend that I get an
executable which runs, but the compile fails to compile pil-1.1.6.p4 and
exits with the error from the end of the log file is below. It's a bit funny in
that pil-1.1.6.p4 installed fine with 5.11.
I tried testing the e
I'm having trouble compiling 5.12. Sage build to the extend that I get an
executable which runs, but the compile fails to compile pil-1.1.6.p4 and
exits with the error from the end of the log file is below. I tried
testing the executable with 'make ptestlong' but it bombs straight away
becaus
In C (and therefore Cython), if you do
def foo():
cdef int my_array[SIZE]
then my_array lives on the stack. Which is relatively small compared to the
heap (the whole available ram). In your case, you are trying to allocate on
the order of about 10 MB, namely 147^3 * sizeof(int) bytes. The s
+1 :-/
And I also noticed that Feedly had not been refreshing sage-devel's rss
feed for weeks T_T
Nathann
On Thursday, October 10, 2013 11:57:46 AM UTC+2, Jean-Pierre Flori wrote:
>
> Same here...
> It was down at some point this morning, then came back to life and is down
> again now.
>
> On
Same here...
It was down at some point this morning, then came back to life and is down
again now.
On Thursday, October 10, 2013 11:50:15 AM UTC+2, Jeroen Demeyer wrote:
>
> Trac is not responding at all, I get 504 Gateway Time-out.
>
--
You received this message because you are subscribed to
Trac is not responding at all, I get 504 Gateway Time-out.
--
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
On Thursday, October 10, 2013 11:19:01 AM UTC+2, Jean-Pierre Flori wrote:
>
> I guess http://trac.sagemath.org/ticket/15080 takes care of this?
>>
>>
>> (Or at least is worth a try)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe
I guess http://trac.sagemath.org/ticket/15080 takes care of this?
On Thursday, October 10, 2013 2:45:24 AM UTC+2, Nils Bruin wrote:
>
> Some further info that may be helpful:
>
> $ ldd /usr/local/sage/sage-git/local/lib/python2.7/lib-dynload/_curses.so
> linux-vdso.so.1 => (0x7fff5a884000
Hi Sébastien,
Even in pure C you can not declare too large static arrays (it also
results in SEGFAULT). Dynamical allocation (with malloc or calloc) is
more flexible for huge chunks of memory.
My comment is just empirical...
Vincent
2013/10/10, Sébastien Labbé :
> Hi sage-devel,
>
> It took me
Hi sage-devel,
It took me a while yesterday to figure out from where I was obtaining a
Segmentation Fault in some cython code. I was using SIZE=200 thinking it
was ok, but no, it is too large!
I am sharing this so that nobody else loses time on the same problem.
Sébastien
r"""
Segmentation Fa
18 matches
Mail list logo
