Hi Andrey
I can confirm that sage-6.6 was built successfully on an 8 year old pentium
with 2GB of RAM and about 10 GB of swap, I was looking from time to time at
the swap use during the ~15 hours built, I think almost 3GB was the top.
This was done with Debian Jessie, which I have to say, is th
On Monday, April 20, 2015 at 3:27:45 AM UTC+2, François wrote:
>
> On 04/20/15 09:23, ggrafendorfer wrote:
> > Sagetex e.g., is one reason:
> >
> > http://www.sagemath.org/doc/installation/sagetex.html
>
> I have to agree with other that setting SAGE_ROOT is
s.
If I type
sage-6.6$ make ptestlong
then I expect that the test is done with the "new" sage-6.6, which can be
found in the same directory as the makefile, no matter if SAGE_ROOT is set
(to whatever) or not.
Otherwise missunderstandings are inevitable.
Georg
>
> > On 1
Sagetex e.g., is one reason:
http://www.sagemath.org/doc/installation/sagetex.html
Georg
On Sunday, April 19, 2015 at 6:43:27 PM UTC+2, John Cremona wrote:
>
> Do you have a reason for having SAGE_ROOT set at all? I don't.
>
> John
>
> On 19 April 2015 at 17:33,
Hi
When I build a new version of sage in a separate directory, and then, while
beeing in that directory, execute
./sage
then the current "old" version of sage, which can be found in SAGE_ROOT is
executed.
E.g., this looks as follows:
.../data/sage-6.6$ pwd
/mnt/data/sage-6.6
.../data/sage-6.6
Hi,
sage 5.0 beta11, on Fedora 15, AMD Phenom II X4:
sage: f(x) = sin(x)^2/x^2
sage: f.integral(x, -infinity, infinity)
x |--> pi
sage: f.integral(x, -infinity, infinity).n()
3.14159265358979
sage: f.integral(x, -5, 0).n() + f.integral(x, 0, 5).n()
3.1415769097886317
everthing fine so fa
Hi,
built successful and almost all test passed (ptestlong) on AMD Phenom
X4 II, Fedora 13
one test failed, this is related to
http://trac.sagemath.org/sage_trac/ticket/9847
Georg
On Sep 7, 12:09 pm, Jeroen Demeyer wrote:
> Hello sage-devel,
>
> As far as we know, there are no more remaini
Hi,
sage-4.3.5 on Phenom II X4, fedora 11,
the same happens since sage-4.3.1 (which I reported on sage-support
before), I know there is a workaround by changing the pari package,
but I'm trying to spread sage on my university (ETH Zürich), we all
use the same OS where the same error occurs, so th
Thank you Mike,
that was probably the fastest answer ever!!
however, I'm sorry for the post, I should have looked if it was
reported before,
Georg
On Mar 22, 9:32 pm, Mike Hansen wrote:
> This ishttp://trac.sagemath.org/sage_trac/ticket/8567. You can fix
> the problem by replacing the gd sp
> Of course only David can speak for his own motives, but do you really
> think David is quitting because of me creating a sage-solaris mailing
> list?
William,
As far as I can judge the situation, its not what you doing, but the
way you are doing it what makes him quit (if he does so),
it would
Hi Minh,
> I still maintain the version of pari-2.3.3.p8.spkg at ticket #7979.
> You can download it from
I know, I already did it and expect it to work,
I'm just wondering, so far I had the impression that built errors (and
this is obviously one) are real blockers for new releases, that is, I
w
Hi all,
I recently reported a build error with sage-4.3.1 on fedora 11:
http://groups.google.com/group/sage-support/browse_thread/thread/c895b6b12eb1d41/a1d5de9ee6b20a1b?lnk=gst&q=fedora+11#a1d5de9ee6b20a1b
the workaround proposed by Minh did work, namely replacing the package
pari-2.3.3.p7.spkg
> "There should be one-- and preferably only one --obvious way to do it."
> ...
>
> and confusing because tab completion always pulls up both commands, and
> the instant question is, "there must be some difference between these;
> which one is right for me?"
You are perfectly right, this is just
Hi All,
concerning general benchmarks, here is a site where are plenty of
languages compared to each other (time, memory usage, source code
size):
http://shootout.alioth.debian.org/gp4/index.php
if you click on one language, you can easily choose the other one to
compare with, etc...,
Georg
14 matches
Mail list logo
