[sage-devel] Re: Some polynomial timings

And why not giac? flint is a little faster for basic multivariate polynomial arithmetic on 1 thread, but giac is multithread and has more advanced fast functionnalities like gcd, factorization, Groebner basis or rational univariate representation. -- You received this message because you are

Re: [sage-devel] Trouble while compiling sage---- compiling ends during plot3d

Thank you. I got the same error even with 'make build' with the j1 flag. I will compile from a local virtual machine and try going the route you suggest. Miguel-Angel Manrique On Monday, September 4, 2017 at 2:07:25 PM UTC-7, Samuel Lelievre wrote: > > If you have access to another machine

Re: [sage-devel] Does anyone use SAGE64?

On 4 September 2017 at 18:34, Erik Bray wrote: > On Mon, Sep 4, 2017 at 6:08 PM, Jean-Pierre Flori > wrote: > +1 I think if this functionality is needed for Solaris (or any other > platform) it should be moved into configure.ac, and the explicit >

Re: [sage-devel] Trouble while compiling sage---- compiling ends during plot3d

If you have access to another machine with more RAM and the same OS, you could produce binaries on that machine and then install on the machine with less RAM from the binaries you created. To create binaries, use: https://github.com/sagemath/binary-pkg ​ -- You received this message because

Re: [sage-devel] Trouble while compiling sage---- compiling ends during plot3d

Unfortunately I cannot add more RAM to the server. One day I hope to have the server be in-house and to swim in many GB of RAM. > I will try these suggestions. Thanks again. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from

Re: [sage-devel] Trouble while compiling sage---- compiling ends during plot3d

I am trying to keep costs down. I would like to have more RAM, but it is not in the budget. -- 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

Re: [sage-devel] Trouble while compiling sage---- compiling ends during plot3d

you can try MAKE="make -j1" make to build the docs. This should make sure you do not build it in parallel. -- 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

Re: [sage-devel] Trouble while compiling sage---- compiling ends during plot3d

Sun 2017-09-03 20:27:44 UTC-5, Miguel-Angel Manrique: > 2048MB RAM total, 4 core 64bit processor; the server was running > webwork in the background, but no students have access yet. > > Building in parallel: no idea but I presume so. I didn't specify the > number of threads to use during

Re: [sage-devel] Re: doctests: non-sorted output

Given the transition to Python 3, I don't think we should directly compare the elements in a set (though perhaps an exception should be made if they all have the same parent). Comparing their string representations seems better. If we do sort the string representation of sets, we can reduce

Re: [sage-devel] Does anyone use SAGE64?

On Mon, Sep 4, 2017 at 6:08 PM, Jean-Pierre Flori wrote: > > > On Monday, September 4, 2017 at 6:06:35 PM UTC+2, Jean-Pierre Flori wrote: >> >> I would also say that passing -m64 is needed on Solaris even when the >> kernel is 64bits, and I think the situation is the same on

Re: [sage-devel] Does anyone use SAGE64?

On Monday, September 4, 2017 at 6:06:35 PM UTC+2, Jean-Pierre Flori wrote: > > I would also say that passing -m64 is needed on Solaris even when the > kernel is 64bits, and I think the situation is the same on linux running on > sparc. > On these platforms default versions of gcc produces 32

Re: [sage-devel] Does anyone use SAGE64?

I would also say that passing -m64 is needed on Solaris even when the kernel is 64bits, and I think the situation is the same on linux running on sparc. On these platforms default versions of gcc produces 32 bits stuff by default, unless you begin compiling your own gcc and convince it to do

[sage-devel] Re: Some polynomial timings

Anyway we should definitely get some multivariate polynomial arithmetic over Z based on flint and keep singular for groebner bases or things it is meant for. On Monday, September 4, 2017 at 7:13:59 AM UTC+2, parisse wrote: > > > > Le dimanche 3 septembre 2017 16:06:46 UTC+2, rjf a écrit : >> >>

[sage-devel] Re: Trouble while compiling sage---- compiling ends during plot3d

> it doesn't solve anything, but... do you need to make the doc? it's > online: http://doc.sagemath.org/ > the command `make start` can be helpful. > > Also "make build". Best, Travis -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To

Re: [sage-devel] Unable to compile 8.0.rc2 on mac

Reimer Behrends has helped me track down the explicit issue. We don't have a patch yet, but the bug (and solution) is described here [1]. Basically the M4 macro JMPENT in mpn/x86_64/x86_64-defs.mac needs to do more than just subtract the two addresses on Mac. However, I'm confused why this

Re: [sage-devel] Trouble while compiling sage---- compiling ends during plot3d

There is the message "Killed" which can normally only happen if something external kills Sage. A common case is the Linux OOM (out-of-memory) killer which kills processes when the system runs out of memory. Second, the docbuilder is known to use huge amounts of memory. -- You received this