Well, we haven't managed to separate sagenb from sage yet. Maybe he wants
something more lightweight.
-Keshav
Join us in #sagemath on irc.freenode.net !
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsu
On Sunday, January 1, 2012 8:52:24 AM UTC-8, daveloeffler wrote:
>
>
> Here's *yet another* SAGE_CHECK issue. The sagetex package doesn't
> work:
>
[snip]
> Output written on example.dvi (7 pages, 23380 bytes).
> Transcript written on example.log.
> Traceback (most recent call last):
>
well, the guy there says that his goal to make a web interface for maxima;
IMHO, sagenb is already here, so why yet another one?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For mo
You might be interested in this topic
https://groups.google.com/forum/#!topic/comp.lang.lisp/k6x-IuBBBQc
These are the sources
https://github.com/filonenko-mikhail/maxima
Apparently the Mikhail's aim is similar to Sage's: running one or more
copies of Maxima in some other and greater progra
On Sunday, January 1, 2012 7:18:20 AM UTC-8, daveloeffler wrote:
>
> I get an error when doing a parallel build with SAGE_CHECK set. See
> below for the relevant part of the output. The problem seems to be
> that the M4RIE test suite requires NTL and Givaro to have already been
> built, but th
On 1 January 2012 16:52, daveloeffler wrote:
>
>
> Here's *yet another* SAGE_CHECK issue. The sagetex package doesn't
> work:
>
> sagetex-2.3.1.p1
> Machine:
> Linux selmer 2.6.28-13-generic #45-Ubuntu SMP Tue Jun 30 22:12:12 UTC
> 2009 x86_64 GNU/Linux
David, We should check whether this machine
On Jan 1, 4:38 pm, Volker Braun wrote:
> I'm only surprised that you get this far; I thought pretty much all builds
> with SAGE_CHECK='yes' die while testing Python because some optional
> modules don't get compiled.
Yes, well, test_distutils fails for me and always has done. I'm just
puzzled t
I'm only surprised that you get this far; I thought pretty much all builds
with SAGE_CHECK='yes' die while testing Python because some optional
modules don't get compiled.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sa
Here's another strange thing: with the new Python 2.7.2 spkg, if
SAGE_CHECK is set, the whole Python test suite gets run *twice over*!
Is this deliberate?
Here is the tail end of the first test run and the beginning of the
second:
test_zipimport_support
test_zlib
343 tests OK.
1 test failed:
I get an error when doing a parallel build with SAGE_CHECK set. See
below for the relevant part of the output. The problem seems to be
that the M4RIE test suite requires NTL and Givaro to have already been
built, but that Sage's build scripts don't know about these
dependencies. Installing the Giva
I had to take hawk down for an extended period of time, as I needed to run some
CPU intensive Windows software, and I currently have no better machine than hawk.
I've upgraded hawk to 24 GB of RAM too - which actually not supported by Sun in
this workstation, but seems to work OK.
I'm looking
11 matches
Mail list logo
