[sage-support] Re: sage-gap interface issue with _gap_

2007-08-02 Thread William Stein
On 8/2/07, David Joyner <[EMAIL PROTECTED]> wrote: > Hi: > > I'm not sure how to resolve this, but the problem is > that, for a permutation group G, the output of G._gap_() > and G._gap_init_() both depend on the size of the > generators. So? I don't understand from what you write below why this

[sage-support] sage-gap interface issue with _gap_

2007-08-02 Thread David Joyner
Hi: I'm not sure how to resolve this, but the problem is that, for a permutation group G, the output of G._gap_() and G._gap_init_() both depend on the size of the generators. Correct: sage: G = PermutationGroup([[(1,2,3),(4,5)],[(3,4)]]) sage: G._gap_init_() 'Group([((1,2,3)(4,5)), ((3,4))])'

[sage-support] Re: Finding the order of points on elliptic curves

2007-08-02 Thread William Stein
On 8/2/07, biozan <[EMAIL PROTECTED]> wrote: > > Hi, > > I'm just wondering if there is a command in sage to determine the > order of a point on an elliptic curve or do I have to define such a > function? I've looked through all the tutorials, cookbook, programming > guide etc, but I can't seem to

[sage-support] Finding the order of points on elliptic curves

2007-08-02 Thread biozan
Hi, I'm just wondering if there is a command in sage to determine the order of a point on an elliptic curve or do I have to define such a function? I've looked through all the tutorials, cookbook, programming guide etc, but I can't seem to find any. Thank you. Regards, Mandy --~--~-~

[sage-support] Re: Can´t compile sage-2.7.2

2007-08-02 Thread legout
Hi William, i´ll do so soon. I could build sage with gcc-4.0. But there´s a problem with my libblas.so. If i try to import cvxopt, i´ve got the following error: sage: import numpy sage: from cvxopt.base import spmatrix ---

[sage-support] Re: Can´t compile sage-2.7.2

2007-08-02 Thread William Stein
On 8/1/07, legout <[EMAIL PROTECTED]> wrote: > thanks for your answer. I already thought about the gcc-problem. And > yes, i´m using gcc 4.2.1. > I´ve just hoped, that this problem was fixed from 2.7 to 2.7.2 ;) Unfortunately not. It's really a linbox problem, and the linbox developers haven't b