On 19 November 2016 at 13:27, Jeroen Demeyer wrote:
> On 2016-11-19 13:16, 'Bill Hart' via sage-release wrote:
>
>> I vaguely remember Bill Allombert saying something about changing Pari
>> so that it just adds more stack when needed, rather than requiring a
>> huge block
On 2016-11-19 13:16, 'Bill Hart' via sage-release wrote:
I vaguely remember Bill Allombert saying something about changing Pari
so that it just adds more stack when needed, rather than requiring a
huge block allocated up front.
It's true that PARI uses a small stack by default and that it
On 19 November 2016 at 12:16, 'Bill Hart' via sage-release
wrote:
> I vaguely remember Bill Allombert saying something about changing Pari so
> that it just adds more stack when needed, rather than requiring a huge block
> allocated up front. Or are we talking about
On 2016-11-19 10:27, John Cremona wrote:
It seems strange to me that pari would need to allocate an
enormous amount of memory as Sage starts up.
Maybe strange, but it is a feature because of the way the PARI stack works.
--
You received this message because you are subscribed to the Google
On 19 November 2016 at 08:18, Jeroen Demeyer wrote:
> On 2016-11-18 20:58, John Cremona wrote:
>>
>>*** Warning: not enough memory, new stack 69618196480
>>
>> -- what's that about (the last line)?
>
>
> It means that PARI failed to allocate the requested amount of
On 2016-11-18 20:58, John Cremona wrote:
*** Warning: not enough memory, new stack 69618196480
-- what's that about (the last line)?
It means that PARI failed to allocate the requested amount of memory.
--
You received this message because you are subscribed to the Google Groups
On 2016-11-18 10:06, John Cremona wrote:
Build failure on ubuntu, based on a successful build of the previous
beta and following "git pull trac develop":
Error building Sage.
The following package(s) may have failed to build (not necessarily
during this run of 'make all'):
* package: python
Well I just did a make distclean and am rebuilding, so I don't know
how old that log file is -- but the build failure report did point to
that file. I have been inventing or resurrecting old packages, I just
pulled the updated develop branch and typed make.
On 18 November 2016 at 17:05, Samuel
Build failure on ubuntu, based on a successful build of the previous
beta and following "git pull trac develop":
Error building Sage.
The following package(s) may have failed to build (not necessarily
during this run of 'make all'):
* package: python
log file:
On Nov 17, 2016, at 16:16 , Francois Bissey wrote:
>
>> On 18/11/2016, at 12:59, Justin C. Walker wrote:
>>
>> sage -t --long --warn-long 70.6 src/sage/interfaces/singular.py
>
> We know about that one at #21865 it can even affect linux boxes.
> Singular 4.1.0 should have the
> On 18/11/2016, at 12:59, Justin C. Walker wrote:
>
> sage -t --long --warn-long 70.6 src/sage/interfaces/singular.py
We know about that one at #21865 it can even affect linux boxes.
Singular 4.1.0 should have the fix we need.
François
--
You received this message because
> On Nov 17, 2016, at 11:14 , Volker Braun wrote:
>
> As always, you can get the latest beta version from the "develop" git branch.
> Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
Built from the tarball on macOS
As always, you can get the latest beta version from the "develop" git
branch. Alternatively, the self-contained source tarball is at
http://www.sagemath.org/download-latest.html
0c6824f Updated SageMath version to 7.5.beta3
36ba665 Trac #21877: Remove two deprecated function from Hasse diagram
13 matches
Mail list logo