On 2013-01-11 11:46, Jeroen Demeyer wrote:
> Hello sage-devel,
>
> It looks like the libGAP patch at #13588 has the unfortunate consequence
> that even more virtual memory will be required to build the Sage
> documentation, about 2.7GB on 64-bit systems.
My initial guess was much too low, it seems
On Jan 13, 2:33 pm, Charles Bouillaguet
wrote:
> Well, I would prefer this thing to print "0.0", just as a gentle reminder
> that the result may not be accurate…
Well, the zero polynomial really is something different from the
constant 0.0. Printing 0 reminds you that really no term is present
he
On Sun, 13 Jan 2013 16:38:27 Vepxistqaosani wrote:
> Hello again!
>
> After my build failed with an input/output error while reading libsingcf.a,
> I thought I'd try to build 'singular' -- the module in which the error
> occurred.
>
> That worked -- a further indication that my disk must be somew
Hello again!
After my build failed with an input/output error while reading libsingcf.a,
I thought I'd try to build 'singular' -- the module in which the error
occurred.
That worked -- a further indication that my disk must be somewhat wonky --
but where do I go from here? The Makefile in spkg
> That's good to know! So doing computations in sage with numerical
> polynomials does not give you an upper bound on the degree of the
> resulting polynomial, contrary to what one would get from a naive
> implementation:
>
> sage: R.=CDF[]
> sage: f=10^30*x
> sage: g=3*x
> sage: (g+f)-f
> 0
Well
On Sunday, 13 January 2013 04:59:19 UTC-5, Volker Braun wrote:
> The symbol table seems to be ok but clearly something is wrong in
> liblinboxsage.so. The actual error might be further up in the log. It could
> also be a transient r/w error, try rebuilding from scratch and see if it
> happens a
I think something with my installation is broken, I removed the patch
and still get the same errors.
I try to track down the reasons for this.
bg,
Johannes
On 13.01.2013 19:49, Johannes wrote:
> yea, I have and I never had problems with it. It's a big surprise for
> me, that so much tests failed,
yea, I have and I never had problems with it. It's a big surprise for
me, that so much tests failed, even because I never recognized any problems.
bg,
Johannes
On 13.01.2013 12:44, Volker Braun wrote:
> On Sunday, January 13, 2013 11:27:09 AM UTC, Johhannes wrote:
>
> I run 'sage -tp 10 -lon
On Jan 13, 10:01 am, Marco Streng wrote:
> Polynomials in Sage have a well-defined degree, and that means that
> the leading coefficient cannot be (numerically) zero, the degree of
> 0.0 is ambiguous unless we decide that 0.0 is just 0, in which case we
> may as well print it as such.
That's good
I don't think it is a bug, rather it is a question about what polynomials are.
CDF['x'](0) is the zero polynomial, with no coefficients, which really
is equal to 0, not just a numerical 0.0.
Polynomials in Sage have a well-defined degree, and that means that
the leading coefficient cannot be (num
On Sunday, January 13, 2013 11:27:09 AM UTC, Johhannes wrote:
> I run 'sage -tp 10 -long src/sage/src' (is there a better way to do a
> test all?)
>
Yes, "make ptest" / "make ptestlong"
and a get a bunch of errors. Most of them coming from undefined
> variables in the tests
Do you have LaTe
Hi,
I run 'sage -tp 10 -long src/sage/src' (is there a better way to do a
test all?)
and a get a bunch of errors. Most of them coming from undefined
variables in the tests. I don't think that all these test are broken
(400+), because some of the errors look like the following one:
> File
> "/usr/
The symbol table seems to be ok but clearly something is wrong in
liblinboxsage.so. The actual error might be further up in the log. It could
also be a transient r/w error, try rebuilding from scratch and see if it
happens again.
On Saturday, January 12, 2013 11:17:26 PM UTC, Vepxistqaosani w
On 2013-01-12 23:37, Vepxistqaosani wrote:
> Hi!
>
> I'm attempting to install Sage 5.5 on a Sony Vaio VGNFW590f3b running an
> Intel Core 2 Duo T6600 / 2.2 GHz ( Dual-Core ) at 64 bits. The OS is
> LinuxMint 14.
>
> The install dies with an input/output error, as shown below.
I would guess it
14 matches
Mail list logo
