`make build` finishes without an error but Sage crashes.
The attached file is Sage_crash_report.txt
2016年12月16日金曜日 11時04分41秒 UTC+9 Dima Pasechnik:
>
> does at least
>
> make build
>
> finish without an error?
> If yes, then the problem is in building the Sage docs.
>
> On Friday, December 16, 2016
does at least
make build
finish without an error?
If yes, then the problem is in building the Sage docs.
On Friday, December 16, 2016 at 1:41:59 AM UTC, Sho Takemori wrote:
>
> Thank you for the information. But I sill don't understand why this error
> occurs.
>
> I build Sage in the Docker con
Thank you for the information. But I sill don't understand why this error
occurs.
I build Sage in the Docker container using the Sage repo as follows.
git checkout a83e25136481efb99d9cb8c00dde3065c0d04894
make
Then I got the following error message
(if I use the commit f26b322f76034b8122603cbc4
A patch is up for review now at https://trac.sagemath.org/ticket/22063
On 15 December 2016 at 17:02, John Cremona wrote:
> Without going so far as to use interval arithmetic (which leads to at
> least one annoying problem: the RealIntervalField in Sage has no
> is_square() methods which is enoug
Without going so far as to use interval arithmetic (which leads to at
least one annoying problem: the RealIntervalField in Sage has no
is_square() methods which is enough to make it hard to work with as
far as creating points on elliptic curves is concerned) I came up with
a better solution.
I wil
On 15 December 2016 at 14:52, wrote:
> @John : Good point. The change in precision, at least seems to fix the
> previous problems (at least in the specific examples).
> I suppose, this is the precision that is used to bound the coefficients of
> the linear form of elliptic logarithms (?)
> If thi
Le jeudi 15 décembre 2016 13:42:57 UTC+1, Sho Takemori a écrit :
>
> Dear all,
>
> I am trying to build Sage 7.5.beta6 using Docker and binary-pkg (
> https://github.com/sagemath/binary-pkg) but I failed.
>
> I cloned binary-pkg in the host and ran the following commands. Here I
> used this Dock
@John : Good point. The change in precision, at least seems to fix the
previous problems (at least in the specific examples).
I suppose, this is the precision that is used to bound the coefficients of
the linear form of elliptic logarithms (?)
If this is the case, and I remember right, this prec
On Thu, Dec 15, 2016 at 4:51 AM, Dima Pasechnik wrote:
>
>
> On Thursday, December 15, 2016 at 12:23:15 PM UTC, John Cremona wrote:
>>
>> I just confirmed that if I change RealField(100) to RealField(200) in
>> one place (line 6975 of ell_rational_field.py) then both the points
>> Costas missed ar
On Thursday, December 15, 2016 at 12:23:15 PM UTC, John Cremona wrote:
>
> I just confirmed that if I change RealField(100) to RealField(200) in
> one place (line 6975 of ell_rational_field.py) then both the points
> Costas missed are found, so I was right that this is a stupid problem
> of pr
Dear all,
I am trying to build Sage 7.5.beta6 using Docker and binary-pkg
(https://github.com/sagemath/binary-pkg) but I failed.
I cloned binary-pkg in the host and ran the following commands. Here I used
this Docker file
(https://gist.github.com/stakemori/2008d4f3480c4c2334ac7133c4f7f0f7).
d
I just confirmed that if I change RealField(100) to RealField(200) in
one place (line 6975 of ell_rational_field.py) then both the points
Costas missed are found, so I was right that this is a stupid problem
of precision rather than something more complicated.
I can easily make a patch to make thi
On 14 December 2016 at 21:34, wrote:
> Thank you both for the answers,
>
> I found another problematic example
>
> sage:E1=EllipticCurve([0,0,0,37,18]);E1;S=E1.integral_points();S;
> Elliptic Curve defined by y^2 = x^3 + 37*x + 18
> over Rational Field
> [(2 : 10 : 1), (126 : 1416 : 1)]
>
>
>
> a
13 matches
Mail list logo