[sage-devel] Re: Sage 2.8.15 vs. gcc 4.3.0 20071130 (experimental)

2007-12-27 Thread remo
> This is a triviality. mwrank_elliptic curves need to be initialized > with 5 integers, period. Currently Sage just tried to coerce the 5 > things to integers, whcih some stupid results (e.g. 1.2 gets rounded > to 1 with meaningless results). This is really bad behaviour. If mwrank only except

[sage-devel] Re: sage 2.8.15 compilation error with gcc 4.1.2 on Slackware Linux 12.0

2007-12-14 Thread John A. Murdie
Thank you, Michael; I made the change to the copy of 2.8.15 I'd downloaded here, and that indeed fixes the problem. John A. Murdie --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [

[sage-devel] Re: sage 2.8.15 compilation error with gcc 4.1.2 on Slackware Linux 12.0

2007-12-14 Thread mabshoff
On Dec 13, 6:20 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > On Dec 13, 6:05 pm, "John A. Murdie" <[EMAIL PROTECTED]> wrote: > > Hello John, > Hello John, I got some feedback from Hans Schöneman of the Singular team. His proposed solution is to change line 127 in Singular/cntrlc.cc fr

[sage-devel] Re: sage 2.8.15 compilation error with gcc 4.1.2 on Slackware Linux 12.0

2007-12-13 Thread mabshoff
On Dec 13, 6:05 pm, "John A. Murdie" <[EMAIL PROTECTED]> wrote: Hello John, > Has anyone seen this problem yet? (I'll investigate it myself also.) > Slackware Linux 12.0, gcc 4.1.12 - versions of other things and/or > other configuration details on request. Nope, I have never seen that one be

[sage-devel] Re: SAGE-2.8.15!

2007-12-05 Thread John Cremona
I have fixed the smallest of the mwrank/g0n issues in trac # 1403; patch attached to the trac. This could be applied to either qrank/getcurve.cc in the new cremona package, or to getcurve.cc in the old mwrank package. On to the next one! John On 05/12/2007, mabshoff <[EMAIL PROTECTED]> wrote:

[sage-devel] Re: Sage 2.8.15 vs. gcc 4.3.0 20071130 (experimental)

2007-12-05 Thread mabshoff
On Dec 5, 8:58 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: Hello John, > Actually there are two different errors we are hunting here --- when > you sent me two backtraces about 12 hours ago there was one for each. The one without symbols was mwrank from mwrank.spkg, the second one with [som

[sage-devel] Re: Sage 2.8.15 vs. gcc 4.3.0 20071130 (experimental)

2007-12-05 Thread John Cremona
Actually there are two different errors we are hunting here --- when you sent me two backtraces about 12 hours ago there was one for each. One is the apparent referenceing of uninitialized memory, somwhere around line 900 of qcurves/sieve_search.cc (I'm being imprecise since I have been adding do

[sage-devel] Re: Sage 2.8.15 vs. gcc 4.3.0 20071130 (experimental)

2007-12-05 Thread mabshoff
Ok, I compiled NTL as well as mwrank with "-O0 -g" and the problem persists. But at least I got a better backtrace from gdb: (gdb) bt #0 0x003105830015 in raise () from /lib64/libc.so.6 #1 0x003105831980 in abort () from /lib64/libc.so.6 #2 0x2b09f1db in ghalt (c=0x2b1609a8

[sage-devel] Re: Sage 2.8.15 vs. gcc 4.3.0 20071130 (experimental)

2007-12-05 Thread mabshoff
On Dec 5, 7:46 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: > > > mwrank compiles with gcc 4.2, so that has never been a problem. I am > > > not sure who fixed it, but the changes should have certainly flown > > If you mean, who fixed my source to compile ok under 4.2 then that was me. Ok, I w

[sage-devel] Re: Sage 2.8.15 vs. gcc 4.3.0 20071130 (experimental)

2007-12-05 Thread Robert Bradshaw
On Dec 5, 2007, at 10:46 AM, John Cremona wrote: >>> #1058 the mwrank interface barfs on bad input > > This is a triviality. mwrank_elliptic curves need to be initialized > with 5 integers, period. Currently Sage just tried to coerce the 5 > things to integers, whcih some stupid results (e.g.

[sage-devel] Re: Sage 2.8.15 vs. gcc 4.3.0 20071130 (experimental)

2007-12-05 Thread John Cremona
> > > > mwrank compiles with gcc 4.2, so that has never been a problem. I am > > not sure who fixed it, but the changes should have certainly flown If you mean, who fixed my source to compile ok under 4.2 then that was me. > > back into your tree. With the removal of mwrank.spkg that issue will

[sage-devel] Re: SAGE-2.8.15!

2007-12-05 Thread mabshoff
On Dec 5, 7:20 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > On Dec 5, 2007 10:15 AM, John Cremona <[EMAIL PROTECTED]> wrote: > > > > > > > On 05/12/2007, William Stein <[EMAIL PROTECTED]> wrote: > > > > On Dec 5, 2007 7:51 AM, John Cremona <[EMAIL PROTECTED]> wrote: > > > > > I'm sure that c

[sage-devel] Re: Sage 2.8.15 vs. gcc 4.3.0 20071130 (experimental)

2007-12-05 Thread William Stein
On Dec 5, 2007 10:21 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > On Dec 5, 4:55 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: > > Since it seems that most of the problems everyone now has are caused > > by the mwrank.spkg -> cremona.spkg switchover, and given that 99.9% of > > the extra functi

[sage-devel] Re: Sage 2.8.15 vs. gcc 4.3.0 20071130 (experimental)

2007-12-05 Thread mabshoff
On Dec 5, 4:55 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: > Since it seems that most of the problems everyone now has are caused > by the mwrank.spkg -> cremona.spkg switchover, and given that 99.9% of > the extra functionality has not yet been wrapped into Sage and is > hence unavailable fro

[sage-devel] Re: SAGE-2.8.15!

2007-12-05 Thread William Stein
On Dec 5, 2007 10:15 AM, John Cremona <[EMAIL PROTECTED]> wrote: > > > On 05/12/2007, William Stein <[EMAIL PROTECTED]> wrote: > > > > On Dec 5, 2007 7:51 AM, John Cremona <[EMAIL PROTECTED]> wrote: > > > > > > I'm sure that can be done, and in fact I have suggested it myself. > > > The cremona.sp

[sage-devel] Re: SAGE-2.8.15!

2007-12-05 Thread John Cremona
On 05/12/2007, William Stein <[EMAIL PROTECTED]> wrote: > > On Dec 5, 2007 7:51 AM, John Cremona <[EMAIL PROTECTED]> wrote: > > > > I'm sure that can be done, and in fact I have suggested it myself. > > The cremona.spkg contains everything that mwrank.spkg did. So whoever > > put mwrank into Sage

[sage-devel] Re: SAGE-2.8.15!

2007-12-05 Thread William Stein
On Dec 5, 2007 7:51 AM, John Cremona <[EMAIL PROTECTED]> wrote: > > I'm sure that can be done, and in fact I have suggested it myself. > The cremona.spkg contains everything that mwrank.spkg did. So whoever > put mwrank into Sage That would be me when I visited you for a day in Nottingham > 2 y

[sage-devel] Re: Sage 2.8.15 vs. gcc 4.3.0 20071130 (experimental)

2007-12-05 Thread John Cremona
Since it seems that most of the problems everyone now has are caused by the mwrank.spkg -> cremona.spkg switchover, and given that 99.9% of the extra functionality has not yet been wrapped into Sage and is hence unavailable from Sage anyway, why don't we just chuck out the cremona.spkg into an opt

[sage-devel] Re: SAGE-2.8.15!

2007-12-05 Thread John Cremona
I'm sure that can be done, and in fact I have suggested it myself. The cremona.spkg contains everything that mwrank.spkg did. So whoever put mwrank into Sage could make some small changes and get mwrank to do the same. The executables files (e.g. the mwrank stand-alone program) should still be b

[sage-devel] Re: Sage 2.8.15 vs. gcc 4.3.0 20071130 (experimental)

2007-12-05 Thread mabshoff
On Dec 5, 12:53 pm, Ismail Dönmez <[EMAIL PROTECTED]> wrote: > Wednesday 05 December 2007 13:48:19 mabshoff yazmıştı: > > > I just love it when I wake up and somebody has come up with a cleaner > > patch than I did. Do you mind if I forward this to gmp-bugs in your > > Name? > > The patch is fro

[sage-devel] Re: Sage 2.8.15 vs. gcc 4.3.0 20071130 (experimental)

2007-12-05 Thread Ismail Dönmez
Wednesday 05 December 2007 13:53:15 Ismail Dönmez yazmıştı: > GMP 4.2.2 which is GPLv3 This should say LGPLv3 of course. -- Never learn by your mistakes, if you do you may never dare to try again. --~--~-~--~~~---~--~~ To post to this group, send email to sage-

[sage-devel] Re: Sage 2.8.15 vs. gcc 4.3.0 20071130 (experimental)

2007-12-05 Thread Ismail Dönmez
Wednesday 05 December 2007 13:48:19 mabshoff yazmıştı: > I just love it when I wake up and somebody has come up with a cleaner > patch than I did. Do you mind if I forward this to gmp-bugs in your > Name? The patch is from OpenSuse and should be already fixed in GMP 4.2.2 which is GPLv3 now so c

[sage-devel] Re: Sage 2.8.15 vs. gcc 4.3.0 20071130 (experimental)

2007-12-05 Thread mabshoff
On Dec 5, 7:39 am, Ismail Dönmez <[EMAIL PROTECTED]> wrote: > Wednesday 05 December 2007 06:07:03 mabshoff yazmıştı: > > > gmp: > [...] > > * uncomment std::FILE -> causes trouble - need clean fix > Hello Ismail > See attached patch. > I just love it when I wake up and somebody has come up w

[sage-devel] Re: Sage 2.8.15 vs. gcc 4.3.0 20071130 (experimental)

2007-12-05 Thread mabshoff
On Dec 5, 6:34 am, "Justin C. Walker" <[EMAIL PROTECTED]> wrote: > Hi, all, > > On Dec 4, 2007, at 20:07 , mabshoff wrote: > > [snip] > > > Those are all cause by mwrank. The issue seems to be the same issue as > > Justin Walker reported in the 2.8.15 thread in sage-support. > > Interestingly no

[sage-devel] Re: SAGE-2.8.15!

2007-12-05 Thread mabshoff
On Dec 5, 10:17 am, "John Cremona" <[EMAIL PROTECTED]> wrote: > I can explain Robert's error. > > When I adapted the code so as to compile with gcc4,2, one function > whose signature changed is initprimes() since gcc4,2 complained about > char* parameters. This was changed in the (new) cremona*

[sage-devel] Re: SAGE-2.8.15!

2007-12-05 Thread John Cremona
I can explain Robert's error. When I adapted the code so as to compile with gcc4,2, one function whose signature changed is initprimes() since gcc4,2 complained about char* parameters. This was changed in the (new) cremona* package, but has not been changed in the (old) mwrank* package, which sh

[sage-devel] Re: Sage 2.8.15 vs. gcc 4.3.0 20071130 (experimental)

2007-12-04 Thread Ismail Dönmez
Wednesday 05 December 2007 06:07:03 mabshoff yazmıştı: > gmp: [...] >  * uncomment std::FILE -> causes trouble - need clean fix See attached patch. Regards, ismail -- Never learn by your mistakes, if you do you may never dare to try again. --~--~-~--~~~---~--~~

[sage-devel] Re: Sage 2.8.15 vs. gcc 4.3.0 20071130 (experimental)

2007-12-04 Thread Justin C. Walker
Hi, all, On Dec 4, 2007, at 20:07 , mabshoff wrote: [snip] > Those are all cause by mwrank. The issue seems to be the same issue as > Justin Walker reported in the 2.8.15 thread in sage-support. > Interestingly nobody ever reported it and I now finally have a > testcase that also produces the is

[sage-devel] Re: SAGE-2.8.15!

2007-12-04 Thread Robert Miller
Probably too late, but maybe this will help. On thing I did that may have caused this is change branches on one terminal while doing a maketest in another window. I haven't moved sage root since install, so I don't know how relevant #1358 is. 1. Tried to install cremona, ran into the same probl

[sage-devel] Re: SAGE-2.8.15!

2007-12-04 Thread mabshoff
On Dec 4, 8:30 pm, Robert Miller <[EMAIL PROTECTED]> wrote: > I don't know if this is specific to my current install, but I thought > it could be useful to someone. Also, I'm not noticing any problems > resulting from this. During upgrade from 2.8.14 on Intel OS X 10.5.1: > > g++ -fPIC -shared -

[sage-devel] Re: SAGE-2.8.15!

2007-12-04 Thread mabshoff
On Dec 4, 8:30 pm, Robert Miller <[EMAIL PROTECTED]> wrote: > I don't know if this is specific to my current install, but I thought > it could be useful to someone. Also, I'm not noticing any problems > resulting from this. During upgrade from 2.8.14 on Intel OS X 10.5.1: I did fix some issue w

[sage-devel] Re: SAGE-2.8.15!

2007-12-04 Thread Robert Miller
I don't know if this is specific to my current install, but I thought it could be useful to someone. Also, I'm not noticing any problems resulting from this. During upgrade from 2.8.14 on Intel OS X 10.5.1: g++ -fPIC -shared -o libntl.so FFT.o FacVec.o GF2.o GF2E.o GF2EX.o GF2EXFactoring.o GF2X.o

[sage-devel] Re: SAGE-2.8.15.rc1 released!

2007-12-03 Thread mabshoff
On Dec 4, 1:24 am, "Pablo De Napoli" <[EMAIL PROTECTED]> wrote: > please consider fixing bug #1282 > > make flint.spkg depend on python > > http://sagetrac.org/sage_trac/ticket/1282 > > which is maked for 2.8.15 milestone > > Pablo > > On Dec 3, 2007 9:16 PM, Jaap Spies <[EMAIL PROTECTED]> wrote

[sage-devel] Re: SAGE-2.8.15.rc1 released!

2007-12-03 Thread mabshoff
On Dec 4, 1:16 am, Jaap Spies <[EMAIL PROTECTED]> wrote: > mabshoff wrote: > > > http://sage.math.washington.edu/home/mabshoff/sage-2.9.15.rc1.tar > > :) > > But on Fedora 8 32 bits: > > -- > The following tests failed: > >

[sage-devel] Re: SAGE-2.8.15.rc1 released!

2007-12-03 Thread mabshoff
On Dec 4, 1:24 am, "Pablo De Napoli" <[EMAIL PROTECTED]> wrote: > please consider fixing bug #1282 > > make flint.spkg depend on python > > http://sagetrac.org/sage_trac/ticket/1282 > > which is maked for 2.8.15 milestone > > Pablo That went into 2.8.15 - could you check $SAGE_ROOT/spkg/deps, b

[sage-devel] Re: SAGE-2.8.15.rc1 released!

2007-12-03 Thread Pablo De Napoli
please consider fixing bug #1282 make flint.spkg depend on python http://sagetrac.org/sage_trac/ticket/1282 which is maked for 2.8.15 milestone Pablo On Dec 3, 2007 9:16 PM, Jaap Spies <[EMAIL PROTECTED]> wrote: > > mabshoff wrote: > > > > > http://sage.math.washington.edu/home/mabshoff/sage

[sage-devel] Re: SAGE-2.8.15.rc1 released!

2007-12-03 Thread Jaap Spies
mabshoff wrote: > > http://sage.math.washington.edu/home/mabshoff/sage-2.9.15.rc1.tar > :) But on Fedora 8 32 bits: -- The following tests failed: sage -t devel/sage-main/sage/functions/transcendental.py

[sage-devel] Re: SAGE-2.8.15.rc1 released!

2007-12-03 Thread William Stein
On Dec 3, 2007 12:30 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > This is a misconception. mwrank will disappear as a standalone spkg, > > but it still exists as a standalone binary in cremona-*.spkg, and will > > continue > > to in the future. In fact, currently in sage we build mwrank twice. >

[sage-devel] Re: SAGE-2.8.15.rc1 released!

2007-12-03 Thread mabshoff
On Dec 3, 9:14 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > On Dec 3, 2007 12:10 PM, mabshoff > > <[EMAIL PROTECTED]> wrote: > I forgot to mention that I renamed the tarball so that we won't get any bug reports for 2.9.15.rc1 in the future ;) See http://sage.math.washington.edu/home/mabsho

[sage-devel] Re: SAGE-2.8.15.rc1 released!

2007-12-03 Thread William Stein
On Dec 3, 2007 12:10 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > > ToDo: > > * investigate Justin's mwrank crashes on 10.5 - this might happen > >on teardown of the heap. Since mwrank as a stand alone binary > >will disappear shortly this problem might solve itself ;) This is a misconcep

[sage-devel] Re: SAGE-2.8.15.rc1 released!

2007-12-03 Thread mabshoff
On Dec 3, 9:06 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > Hello folks, > > this is likely to be indentical to 2.8.15 assuming nothing turns up > last minute. We closed 80 tickets this release cycle, see > > http://www.sagetrac.org/sage_trac/query?status=closed&milestone=sage-... > > S

[sage-devel] Re: Sage-2.8.15.rc0 release

2007-12-02 Thread Justin C. Walker
And another thing: On Dec 2, 2007, at 22:50 , Justin C. Walker wrote: > On Dec 2, 2007, at 21:47 , William Stein wrote: [snip] >> Then you get those errors you listed? (I fixed the permissions on >> the file you posted so everybody can read them -- the errors look >> very scary!) > > Have you v

[sage-devel] Re: Sage-2.8.15.rc0 release

2007-12-02 Thread Justin C. Walker
A question: On Dec 2, 2007, at 21:47 , William Stein wrote: > On Dec 2, 2007 9:42 PM, Justin C. Walker <[EMAIL PROTECTED]> wrote: [snip] > Just for clarification, do you mean that if you type this on a > frech rc0 build: > > bsd:sage-2.8.15.rc0 was$ ./sage -t devel/doc/tut/tut.tex > sage -t de

[sage-devel] Re: Sage-2.8.15.rc0 release

2007-12-02 Thread Justin C. Walker
On Dec 2, 2007, at 21:47 , William Stein wrote: > On Dec 2, 2007 9:42 PM, Justin C. Walker <[EMAIL PROTECTED]> wrote: >> On Dec 2, 2007, at 18:22 , mabshoff wrote: [snip] >> Still showing 'mwrank' blowing chunks during the testing on 10.5.1 (a >> Core Duo). This happens early on, I think during

[sage-devel] Re: Sage-2.8.15.rc0 release

2007-12-02 Thread William Stein
On Dec 2, 2007 9:42 PM, Justin C. Walker <[EMAIL PROTECTED]> wrote: > > > On Dec 2, 2007, at 18:22 , mabshoff wrote: > > > > > Hello folks, > > > > So far we closed roughly 72 tickets, see > > > > http://www.sagetrac.org/sage_trac/query? > > status=closed&milestone=sage-2.8.15 > > > > Still no ATL

[sage-devel] Re: Sage-2.8.15.rc0 release

2007-12-02 Thread Justin C. Walker
On Dec 2, 2007, at 18:22 , mabshoff wrote: > > Hello folks, > > So far we closed roughly 72 tickets, see > > http://www.sagetrac.org/sage_trac/query? > status=closed&milestone=sage-2.8.15 > > Still no ATLAS, but we merged pretty much every mergable patch and had > to > back out the occasional p

[sage-devel] Re: Sage 2.8.15.alpha2 released!

2007-12-02 Thread mabshoff
On Dec 3, 2:17 am, "Justin C. Walker" <[EMAIL PROTECTED]> wrote: > On Dec 2, 2007, at 24:27 , mabshoff wrote: > > > > > A quick remark upfront: This Bug Day rocked! We got a lot > > accomplished > > and pretty much merged every mergable patch. Thanks to everybody who > > participated! We closed

[sage-devel] Re: Sage 2.8.15.alpha2 released!

2007-12-02 Thread Justin C. Walker
On Dec 2, 2007, at 24:27 , mabshoff wrote: > > A quick remark upfront: This Bug Day rocked! We got a lot > accomplished > and pretty much merged every mergable patch. Thanks to everybody who > participated! We closed roughly 60 tickets, see > > http://www.sagetrac.org/sage_trac/query? > status=

[sage-devel] Re: Sage 2.8.15.alpha2 released!

2007-12-02 Thread William Stein
On Dec 2, 2007 10:13 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > On Dec 2, 7:07 pm, Jaap Spies <[EMAIL PROTECTED]> wrote: > > mabshoff wrote: > > > > > http://sage.math.washington.edu/home/mabshoff/sage-2.8.15.alpha2.tar > > > [167 MB] > > > > On Fedora 8 32 bits I got this in test.log: > > >

[sage-devel] Re: Sage 2.8.15.alpha2 released!

2007-12-02 Thread mabshoff
On Dec 2, 7:07 pm, Jaap Spies <[EMAIL PROTECTED]> wrote: > mabshoff wrote: > > > http://sage.math.washington.edu/home/mabshoff/sage-2.8.15.alpha2.tar > > [167 MB] > > On Fedora 8 32 bits I got this in test.log: > > File "maxima.py", line 711: > sage: _= len(maxima.trait_names(verbose=False

[sage-devel] Re: Sage 2.8.15.alpha2 released!

2007-12-02 Thread Jaap Spies
mabshoff wrote: > > http://sage.math.washington.edu/home/mabshoff/sage-2.8.15.alpha2.tar > [167 MB] > On Fedora 8 32 bits I got this in test.log: File "maxima.py", line 711: sage: _= len(maxima.trait_names(verbose=False))# random output Expected nothing Got: Done! **

[sage-devel] Re: Sage 2.8.15.alpha2 released!

2007-12-02 Thread Jaap Spies
mabshoff wrote: > > > > This is now #1372. Please try the patch I attached there and report > back if it fixes the issue for you. > With patch: Exiting SAGE (CPU time 0m0.02s, Wall time 0m18.24s). [EMAIL PROTECTED] sage-2.8.15.alpha2]$ ./sage -t devel/sage-main/sage/lfunctions/dokchitser.p

[sage-devel] Re: Sage 2.8.15.alpha2 released!

2007-12-02 Thread mabshoff
On Dec 2, 4:31 pm, Jaap Spies <[EMAIL PROTECTED]> wrote: > mabshoff wrote: > > As it turned out Alpha 2 is loads of fixes and all the prep-work for > > the ATLAS merge, but ATLAS itself didn't make it yet. The tarball is > > at > > > http://sage.math.washington.edu/home/mabshoff/sage-2.8.15.alp

[sage-devel] Re: Sage 2.8.15.alpha2 released!

2007-12-02 Thread Jaap Spies
mabshoff wrote: > As it turned out Alpha 2 is loads of fixes and all the prep-work for > the ATLAS merge, but ATLAS itself didn't make it yet. The tarball is > at > > http://sage.math.washington.edu/home/mabshoff/sage-2.8.15.alpha2.tar > [167 MB] On Fedora 7: -

[sage-devel] Re: Sage 2.8.15.alpha2 released!

2007-12-02 Thread Burcin Erocal
On Sun, 2 Dec 2007 00:27:18 -0800 (PST) mabshoff <[EMAIL PROTECTED]> wrote: > Depending on the strategy we can do two things: > > * release 2.8.15 late Sunday, maybe merge in ATLAS if it works, then > do a >2.8.16 release with the updated Singular, FLINT 1.0 and PolyBoRi > toward >the