> Other people in this thread suggested that
>
> sage -f ecl
> sage -f maxima
>
> should fix it. (I think you ought to be able to just do 'sage -f maxima',
> actually.)
>
Thank you! That worked.
Anne
--
You received this message because you are subscribed to the Google Groups
"sage-rel
You need to recompile Sage. The docbuilder relies on being able to import
Sage, but you seem to have some messed upl maxima/ecl. If in doubt: make
distclean && make
On Monday, June 2, 2014 9:32:42 PM UTC+1, Anne Schilling wrote:
>
> Hi!
>
> I get the following error even after make doc-clean:
>
On Monday, June 2, 2014 1:32:42 PM UTC-7, Anne Schilling wrote:
>
> Hi!
>
> I get the following error even after make doc-clean:
>
> [graphs ] reading sources... [ 78%] sage/graphs/line_graph
> [calculus ] Exception occurred:
> [calculus ] File "ecl.pyx", line 337, in sage.libs.ecl.ecl_safe_eva
Hi!
I get the following error even after make doc-clean:
[graphs ] reading sources... [ 78%] sage/graphs/line_graph
[calculus ] Exception occurred:
[calculus ] File "ecl.pyx", line 337, in sage.libs.ecl.ecl_safe_eval
(sage/libs/ecl.c:4352)
[calculus ] RuntimeError: ECL says: Module error: Don'
I have no idea about Un*x programming, has this to do with
http://trac.sagemath.org/ticket/13311 ?
Until something is done running patchbot in clouds is near useless.
On Thu, May 29, 2014 at 3:40 PM, Volker Braun wrote:
> I think the best option is to fix the sigalarm delivery to be 100% reliab
I think the best option is to fix the sigalarm delivery to be 100% reliable
On Thursday, May 29, 2014 2:34:13 PM UTC+1, Ralf Stephan wrote:
>
> On Thu, May 29, 2014 at 12:28 PM, Volker Braun
>
> > wrote:
>
>> The reason is alarm() not working reliably. The failing test is from:
>>
>> 5159542 T
On Thu, May 29, 2014 at 12:28 PM, Volker Braun wrote:
> The reason is alarm() not working reliably. The failing test is from:
>
> 5159542 Trac #16162: Cantor-Zassenhaus may enter infinite loop over
> GF(2**k) and cannot be interrupted
>
> but thats just the symptom not the cause.
>
So, should on
The reason is alarm() not working reliably. The failing test is from:
5159542 Trac #16162: Cantor-Zassenhaus may enter infinite loop over
GF(2**k) and cannot be interrupted
but thats just the symptom not the cause.
On Thursday, May 29, 2014 9:02:42 AM UTC+1, Ralf Stephan wrote:
>
> In some doc
In some doctest runs, doctests are getting stuck in testing
polynomial_element.pyx
http://patchbot.sagemath.org/log/15914/Ubuntu/14.04/x86_64/3.13.0-24-generic/compute5dc2/2014-05-29%2007:41:00%20+
http://patchbot.sagemath.org/log/16261/Ubuntu/14.04/x86_64/3.13.0-24-generic/compute5dc2/2014-
New beta is out now, get it while its hot ;)
As usual, checkout the "develop" branch on our git server or download the
whole source tarball:
http://boxen.math.washington.edu/home/release/sage-6.3.beta2.tar.gz
Mini-changelog:
a3c4cf3 Updated Sage version to 6.3.beta2
c727462 Trac #16389: displa
10 matches
Mail list logo