[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
I tried to sage -upgrade my 2.8.9 this evening on an Ubuntu x686, and I got: Building sage/matrix/misc.c because it depends on sage/matrix/ misc.pyx. touch sage/matrix/misc.pyx; cython --embed-positions --incref-local- binop -I/home/kostadm/sage/devel/sage-main -o sage/matrix/misc.c sage/ matrix/misc.pyx Error converting Pyrex file to C: ... 0, 0, 0) cdef mpz_t* L_row cdef mod_int* A_row for i from 0 = i A._nrows: L_row = L._matrix[i] A_row = A._matrix[i] ^ /home/kostadm/sage/devel/sage-main/sage/matrix/misc.pyx:54:25: Cannot assign type 'sage.matrix.matrix_modn_dense.mod_int *' to 'sage.matrix.misc.mod_int *' sage: Error running cython. sage: There was an error installing modified sage library code. JV --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
I just downloaded a new tarball from sage.math. JV --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
On Nov 8, 2007 3:12 PM, Kate [EMAIL PROTECTED] wrote: I am confused about why you forwarded my build report to sage-devel. According to the About this group I forwarded your email because I know for a fact that several of the people likely to fix the problems you reported only subscribe to sage-devel but not to sage-support. Simple as that. -- William sage-support: This email list is to report possible bugs in SAGE or to post a support-related issue. sage-devel: This email list is for discussion of SAGE development issues. I was trying to build from source - and failed - so that seems to me to be more of support issue, rather than a development issue. If you want, in the future I will send my build problems to sage- devel. But if this is really what you want, I recommend that you change the wording for About this group to more accurately reflect what you want. Kate On Nov 7, 2:08 pm, William Stein [EMAIL PROTECTED] wrote: This should really be sent to sage-devel, so I'm forwarding it there. -- Forwarded message -- From: William Stein [EMAIL PROTECTED] Date: Nov 7, 2007 11:07 AM Subject: Re: [sage-support] sage-2.8.12 build report To: [EMAIL PROTECTED] On Nov 7, 2007 11:02 AM, Kate Minola [EMAIL PROTECTED] wrote: I go away for a while, and now SAGE does not build on any of my machines of interest: Compiling from source using gcc-4.2.2, I get *** x86-Linux, ia64-Linux *** While compiling cvxopt-0.8.2.p4, I get gcc -pthread -shared build/temp.linux-i686-2.5/C/base.o build/temp.linux-i686-2.5/C/dense.o build/temp.linux-i686-2.5/C/sparse.o -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib/gcc-lib/i686-pc-linux-gnu/4.0.3 -lm -llapack -lblas -lf95 -o build/lib.linux-i686-2.5/cvxopt/base.so /usr/local/binutils-2.17/x86-Linux-gcc-4.1.1/bin/ld: cannot find -lf95 That's because you're using gfortran. Evidently Josh's fix for cvxopt not fully working fails for people using gfortran. I'll open a trac ticket: http://trac.sagemath.org/sage_trac/ticket/1125 *** x86_64-Linux *** While compiling libfplll-2.1-20071024, I get g++ -shared -nostdlib /usr/lib/../lib64/crti.o /usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/crtbeginS.o .libs/fplll.o -Wl,--rpath -Wl,/usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64 -Wl,--rpath -Wl,/usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64 -lmpfr -lgmp -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2 -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/home/kate/sage/sage-2.8.12-x86_64-Linux/local/lib -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/../../.. /usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64/libstdc++.so -lm -lc -lgcc_s /usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/crtendS.o /usr/lib/../lib64/crtn.o -Wl,-soname -Wl,libfplll.so.0 -o .libs/libfplll.so.0.0.0 /usr/bin/ld: /usr/lib/../lib64/libmpfr.a(exceptions.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/lib/../lib64/libmpfr.a: could not read symbols: Bad value Why is Sage trying to use libmpfr.a out of /usr/lib? Should it not be using the version in [sage]/local/lib? I agree. Note that libfpll is a brand new package in Sage (it does very fast LLL reduction, so is quite important), but it hasn't been as widely tested as other components of Sage. This is now trac #1126: http://trac.sagemath.org/sage_trac/ticket/1126 I've made both trac tickets blockers. We'll fix them at Sage Days next week. William -- William Stein Associate Professor of Mathematics University of Washingtonhttp://wstein.org -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
Michael, I have tried http://sage.math.washington.edu/home/mabshoff/libfplll-2.1-20071024.p0.spkg and can report that it builds on my x86_64-Linux box. The build is now stuck at the cvxopt-0.8.2.p4 spot (same error) that I reported for x86-Linux and ia64-Linux. Kate On Nov 7, 6:16 pm, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Nov 7, 8:08 pm, William Stein [EMAIL PROTECTED] wrote: This should really be sent to sage-devel, so I'm forwarding it there. -- Forwarded message -- From: William Stein [EMAIL PROTECTED] Date: Nov 7, 2007 11:07 AM Subject: Re: [sage-support] sage-2.8.12 build report To: [EMAIL PROTECTED] On Nov 7, 2007 11:02 AM, Kate Minola [EMAIL PROTECTED] wrote: I go away for a while, and now SAGE does not build on any of my machines of interest: Compiling from source using gcc-4.2.2, I get *** x86-Linux, ia64-Linux *** While compiling cvxopt-0.8.2.p4, I get gcc -pthread -shared build/temp.linux-i686-2.5/C/base.o build/temp.linux-i686-2.5/C/dense.o build/temp.linux-i686-2.5/C/sparse.o -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib/gcc-lib/i686-pc-linux-gnu/4.0.3 -lm -llapack -lblas -lf95 -o build/lib.linux-i686-2.5/cvxopt/base.so /usr/local/binutils-2.17/x86-Linux-gcc-4.1.1/bin/ld: cannot find -lf95 That's because you're using gfortran. Evidently Josh's fix for cvxopt not fully working fails for people using gfortran. I'll open a trac ticket: http://trac.sagemath.org/sage_trac/ticket/1125 *** x86_64-Linux *** While compiling libfplll-2.1-20071024, I get g++ -shared -nostdlib /usr/lib/../lib64/crti.o /usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/crtbeginS.o .libs/fplll.o -Wl,--rpath -Wl,/usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64 -Wl,--rpath -Wl,/usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64 -lmpfr -lgmp -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2 -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/home/kate/sage/sage-2.8.12-x86_64-Linux/local/lib -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/../../.. /usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64/libstdc++.so -lm -lc -lgcc_s /usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/crtendS.o /usr/lib/../lib64/crtn.o -Wl,-soname -Wl,libfplll.so.0 -o .libs/libfplll.so.0.0.0 /usr/bin/ld: /usr/lib/../lib64/libmpfr.a(exceptions.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/lib/../lib64/libmpfr.a: could not read symbols: Bad value Why is Sage trying to use libmpfr.a out of /usr/lib? Should it not be using the version in [sage]/local/lib? I agree. Note that libfpll is a brand new package in Sage (it does very fast LLL reduction, so is quite important), but it hasn't been as widely tested as other components of Sage. This is now trac #1126: Kate, could you try http://sage.math.washington.edu/home/mabshoff/libfplll-2.1-20071024.p... and report back it that solves the issue? Cheers, Michael http://trac.sagemath.org/sage_trac/ticket/1126 I've made both trac tickets blockers. We'll fix them at Sage Days next week. William -- William Stein Associate Professor of Mathematics University of Washingtonhttp://wstein.org --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
William, I am confused about why you forwarded my build report to sage-devel. According to the About this group sage-support: This email list is to report possible bugs in SAGE or to post a support-related issue. sage-devel: This email list is for discussion of SAGE development issues. I was trying to build from source - and failed - so that seems to me to be more of support issue, rather than a development issue. If you want, in the future I will send my build problems to sage- devel. But if this is really what you want, I recommend that you change the wording for About this group to more accurately reflect what you want. Kate On Nov 7, 2:08 pm, William Stein [EMAIL PROTECTED] wrote: This should really be sent to sage-devel, so I'm forwarding it there. -- Forwarded message -- From: William Stein [EMAIL PROTECTED] Date: Nov 7, 2007 11:07 AM Subject: Re: [sage-support] sage-2.8.12 build report To: [EMAIL PROTECTED] On Nov 7, 2007 11:02 AM, Kate Minola [EMAIL PROTECTED] wrote: I go away for a while, and now SAGE does not build on any of my machines of interest: Compiling from source using gcc-4.2.2, I get *** x86-Linux, ia64-Linux *** While compiling cvxopt-0.8.2.p4, I get gcc -pthread -shared build/temp.linux-i686-2.5/C/base.o build/temp.linux-i686-2.5/C/dense.o build/temp.linux-i686-2.5/C/sparse.o -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib/gcc-lib/i686-pc-linux-gnu/4.0.3 -lm -llapack -lblas -lf95 -o build/lib.linux-i686-2.5/cvxopt/base.so /usr/local/binutils-2.17/x86-Linux-gcc-4.1.1/bin/ld: cannot find -lf95 That's because you're using gfortran. Evidently Josh's fix for cvxopt not fully working fails for people using gfortran. I'll open a trac ticket: http://trac.sagemath.org/sage_trac/ticket/1125 *** x86_64-Linux *** While compiling libfplll-2.1-20071024, I get g++ -shared -nostdlib /usr/lib/../lib64/crti.o /usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/crtbeginS.o .libs/fplll.o -Wl,--rpath -Wl,/usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64 -Wl,--rpath -Wl,/usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64 -lmpfr -lgmp -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2 -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/home/kate/sage/sage-2.8.12-x86_64-Linux/local/lib -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/../../.. /usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64/libstdc++.so -lm -lc -lgcc_s /usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/crtendS.o /usr/lib/../lib64/crtn.o -Wl,-soname -Wl,libfplll.so.0 -o .libs/libfplll.so.0.0.0 /usr/bin/ld: /usr/lib/../lib64/libmpfr.a(exceptions.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/lib/../lib64/libmpfr.a: could not read symbols: Bad value Why is Sage trying to use libmpfr.a out of /usr/lib? Should it not be using the version in [sage]/local/lib? I agree. Note that libfpll is a brand new package in Sage (it does very fast LLL reduction, so is quite important), but it hasn't been as widely tested as other components of Sage. This is now trac #1126: http://trac.sagemath.org/sage_trac/ticket/1126 I've made both trac tickets blockers. We'll fix them at Sage Days next week. William -- William Stein Associate Professor of Mathematics University of Washingtonhttp://wstein.org --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
On Nov 8, 3:59 pm, Kate [EMAIL PROTECTED] wrote: Michael, Hello Kate, I have tried http://sage.math.washington.edu/home/mabshoff/libfplll-2.1-20071024.p... and can report that it builds on my x86_64-Linux box. Great. I will make sure the updated spkg goes into 2.9 or whatever the next release will be. The build is now stuck at the cvxopt-0.8.2.p4 spot (same error) that I reported for x86-Linux and ia64-Linux. Josh did update the cvxopt.spkg (see above in the thread). The latest is at http://sage.math.washington.edu/home/jkantor/spkgs/cvxopt-0.8.2.p5.spkg It should now handle gfortran and g95 without problems. Please report back if that solves your problem. Kate SNIP Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
On Nov 8, 9:50 pm, Kate [EMAIL PROTECTED] wrote: Michael, SNIP sage -t devel/sage-main/sage/numerical/test.py ** File test.py, line 4: : from cvxopt.base import * Exception raised: Traceback (most recent call last): File /home/kate/sage/sage-2.8.12-ia64-Linux/local/lib/python2.5/ doctest.py, line 1212, in __run compileflags, 1) in test.globs File doctest __main__.example_0[0], line 1, in module from cvxopt.base import *###line 4: : from cvxopt.base import * ImportError: /usr/lib/libblas.so.3: undefined symbol: e_wsfe ** Sorry to reply to myself so quickly: here we are pulling in the local blas and not the one we compiled with Sage. So that should be easily fixable. Note to self: Need more sleep. Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
On Nov 8, 9:50 pm, Kate [EMAIL PROTECTED] wrote: Michael, Kate, Much thanks for the link to Josh's update of cvxopt.spkg. No problem. With that fix, I now can compile on all the architectures I am currently interested in: x86-Linux, x86_64-Linux, and ia64-Linux. The next step is to run 'make check', which I have done. Sadly, only x86-Linux passes all the tests. *** x86_64-Linux *** sage -t devel/sage-main/sage/rings/real_rqdf.pyx ** File real_rqdf.pyx, line 12: sage: RQDF( 123.2) + RR (1.0) Expected: 124.2000 Got: NaN ** File real_rqdf.pyx, line 14: sage: RQDF( 12.2) + RDF (0.56) Expected: 12.76 Got: nan ** File real_rqdf.pyx, line 16: sage: RQDF( 12.2) + (9) Expected: 21.19928945726423989981412887573242187500 Got: NaN ** and then others with a similar message: Got NaN or Got nan mmmh, any chance some other package pulls in the libmpfr that caused trouble with libfplll? Could you gzip the build log and post it somewhere and send us a link? *** ia64-Linux *** The following tests failed: sage -t devel/sage-main/sage/lfunctions/lcalc.py sage -t devel/sage-main/sage/numerical/test.py sage -t devel/sage-main/sage/rings/polynomial/ polynomial_element.pyx sage -t devel/sage-main/sage/lfunctions/lcalc.py ** File lcalc.py, line 188: sage: E.Lseries().values_along_line(0.5, 3, 5) Expected: lcalc: 1.5 0 WARNING- we don't have enough Dirichlet coefficients. lcalc: Will use the maximum possible, though the output will not necessarily be accurate. lcalc: nan nan [(0, 0.209951303), (0.5, -2...e-16), (1., 0.133768433), (2., 0.552975867)] Got: lcalc: 1.5 0 WARNING- we don't have enough Dirichlet coefficients. lcalc: Will use the maximum possible, though the output will not necessarily be accurate. lcalc: nan nan [(0, 0.209951303), (0.5, -3.16949699e-16), (1., 0.133768433), (2., 0.552975867)] ** Mhh, not sure about this one yet. sage -t devel/sage-main/sage/numerical/test.py ** File test.py, line 4: : from cvxopt.base import * Exception raised: Traceback (most recent call last): File /home/kate/sage/sage-2.8.12-ia64-Linux/local/lib/python2.5/ doctest.py, line 1212, in __run compileflags, 1) in test.globs File doctest __main__.example_0[0], line 1, in module from cvxopt.base import *###line 4: : from cvxopt.base import * ImportError: /usr/lib/libblas.so.3: undefined symbol: e_wsfe ** Josh - any idea about this one? sage -t devel/sage-main/sage/rings/polynomial/ polynomial_element.pyx** File polynomial_element.pyx, line 2314: sage: f.roots(ring=CC) Expected: [(1.00, 1), (-0.500 + 0.866025403784438*I, 1), (-0.500 - 0.866025403784438*I, 1)] Got: [(1.00, 1), (-0.500 + 0.866025403784439*I, 1), (-0.500 - 0.866025403784439*I, 1)] ** File polynomial_element.pyx, line 2749: sage: (x^3 - 1).complex_roots() Expected: [1.00, -0.500 + 0.866025403784438*I, -0.500 - 0.866025403784438*I] Got: [1.00, -0.500 + 0.866025403784439*I, -0.500 - 0.866025403784439*I] ** Ok, these are only minor precision issues, that we can easily fix in the next release. Kate Any volunteers to open trac tickets for these? I have to leave for the airport in 5 hours and would like to catch some sleep. I am also working on another release candidate for ApCoCoA - G, work sucks. SNIP Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
Michael, Much thanks for the link to Josh's update of cvxopt.spkg. With that fix, I now can compile on all the architectures I am currently interested in: x86-Linux, x86_64-Linux, and ia64-Linux. The next step is to run 'make check', which I have done. Sadly, only x86-Linux passes all the tests. *** x86_64-Linux *** sage -t devel/sage-main/sage/rings/real_rqdf.pyx ** File real_rqdf.pyx, line 12: sage: RQDF( 123.2) + RR (1.0) Expected: 124.2000 Got: NaN ** File real_rqdf.pyx, line 14: sage: RQDF( 12.2) + RDF (0.56) Expected: 12.76 Got: nan ** File real_rqdf.pyx, line 16: sage: RQDF( 12.2) + (9) Expected: 21.19928945726423989981412887573242187500 Got: NaN ** and then others with a similar message: Got NaN or Got nan *** ia64-Linux *** The following tests failed: sage -t devel/sage-main/sage/lfunctions/lcalc.py sage -t devel/sage-main/sage/numerical/test.py sage -t devel/sage-main/sage/rings/polynomial/ polynomial_element.pyx sage -t devel/sage-main/sage/lfunctions/lcalc.py ** File lcalc.py, line 188: sage: E.Lseries().values_along_line(0.5, 3, 5) Expected: lcalc: 1.5 0 WARNING- we don't have enough Dirichlet coefficients. lcalc: Will use the maximum possible, though the output will not necessarily be accurate. lcalc: nan nan [(0, 0.209951303), (0.5, -2...e-16), (1., 0.133768433), (2., 0.552975867)] Got: lcalc: 1.5 0 WARNING- we don't have enough Dirichlet coefficients. lcalc: Will use the maximum possible, though the output will not necessarily be accurate. lcalc: nan nan [(0, 0.209951303), (0.5, -3.16949699e-16), (1., 0.133768433), (2., 0.552975867)] ** sage -t devel/sage-main/sage/numerical/test.py ** File test.py, line 4: : from cvxopt.base import * Exception raised: Traceback (most recent call last): File /home/kate/sage/sage-2.8.12-ia64-Linux/local/lib/python2.5/ doctest.py, line 1212, in __run compileflags, 1) in test.globs File doctest __main__.example_0[0], line 1, in module from cvxopt.base import *###line 4: : from cvxopt.base import * ImportError: /usr/lib/libblas.so.3: undefined symbol: e_wsfe ** sage -t devel/sage-main/sage/rings/polynomial/ polynomial_element.pyx** File polynomial_element.pyx, line 2314: sage: f.roots(ring=CC) Expected: [(1.00, 1), (-0.500 + 0.866025403784438*I, 1), (-0.500 - 0.866025403784438*I, 1)] Got: [(1.00, 1), (-0.500 + 0.866025403784439*I, 1), (-0.500 - 0.866025403784439*I, 1)] ** File polynomial_element.pyx, line 2749: sage: (x^3 - 1).complex_roots() Expected: [1.00, -0.500 + 0.866025403784438*I, -0.500 - 0.866025403784438*I] Got: [1.00, -0.500 + 0.866025403784439*I, -0.500 - 0.866025403784439*I] ** Kate On Nov 8, 10:04 am, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Nov 8, 3:59 pm, Kate [EMAIL PROTECTED] wrote: Michael, Hello Kate, I have tried http://sage.math.washington.edu/home/mabshoff/libfplll-2.1-20071024.p... and can report that it builds on my x86_64-Linux box. Great. I will make sure the updated spkg goes into 2.9 or whatever the next release will be. The build is now stuck at the cvxopt-0.8.2.p4 spot (same error) that I reported for x86-Linux and ia64-Linux. Josh did update the cvxopt.spkg (see above in the thread). The latest is at http://sage.math.washington.edu/home/jkantor/spkgs/cvxopt-0.8.2.p5.spkg It should now handle gfortran and g95 without problems. Please report back if that solves your problem. Kate SNIP Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
Yeah. the missing symbol is because its linking against libblas in / usr/lib, which was compiled with some other probably older fortran (why oh why can't all the fortrans get along). I'm curious about what people think is a good solution here. If they have a libblas in /usr/lib thats broken like this (it requires special additional libraries but we can't deduce that at compile time) then as far as I know, the only way to avoid linking against their blas is to change the name of our blas library i.e. libsage_blas and link against that. Or do something like set LD_LIBRARY_PATH=$SAGE_LOCAL (but thats not a good way to solve the problem). Thoughts? Josh On Nov 8, 1:11 pm, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Nov 8, 9:50 pm, Kate [EMAIL PROTECTED] wrote: Michael, SNIP sage -t devel/sage-main/sage/numerical/test.py ** File test.py, line 4: : from cvxopt.base import * Exception raised: Traceback (most recent call last): File /home/kate/sage/sage-2.8.12-ia64-Linux/local/lib/python2.5/ doctest.py, line 1212, in __run compileflags, 1) in test.globs File doctest __main__.example_0[0], line 1, in module from cvxopt.base import *###line 4: : from cvxopt.base import * ImportError: /usr/lib/libblas.so.3: undefined symbol: e_wsfe ** Sorry to reply to myself so quickly: here we are pulling in the local blas and not the one we compiled with Sage. So that should be easily fixable. Note to self: Need more sleep. Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
On Nov 9, 3:14 am, Joshua Kantor [EMAIL PROTECTED] wrote: Hi Josh, Yeah. the missing symbol is because its linking against libblas in / usr/lib, which was compiled with some other probably older fortran (why oh why can't all the fortrans get along). I'm curious about what people think is a good solution here. If they have a libblas in /usr/lib thats broken like this (it requires special additional libraries but we can't deduce that at compile time) We are guaranteed a BLAS in $SAGE_LOCAL/lib because we compile it ourselves. So just add -L $SAGE_LOCAL/lib to the flags at the right point and the problem is gone. then as far as I know, the only way to avoid linking against their blas is to change the name of our blas library i.e. libsage_blas and link against that. Or do something like set LD_LIBRARY_PATH=$SAGE_LOCAL (but thats not a good way to solve the problem). Nope, I agree that this is not a solution. And we do add $SAGE_LOCAL/ lib to LD_LIBRARY_PATH which causes the problem in the first place. Thoughts? :) Off to the airport Josh Michael On Nov 8, 1:11 pm, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Nov 8, 9:50 pm, Kate [EMAIL PROTECTED] wrote: Michael, SNIP sage -t devel/sage-main/sage/numerical/test.py ** File test.py, line 4: : from cvxopt.base import * Exception raised: Traceback (most recent call last): File /home/kate/sage/sage-2.8.12-ia64-Linux/local/lib/python2.5/ doctest.py, line 1212, in __run compileflags, 1) in test.globs File doctest __main__.example_0[0], line 1, in module from cvxopt.base import *###line 4: : from cvxopt.base import * ImportError: /usr/lib/libblas.so.3: undefined symbol: e_wsfe ** Sorry to reply to myself so quickly: here we are pulling in the local blas and not the one we compiled with Sage. So that should be easily fixable. Note to self: Need more sleep. Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
This is something which has confused me in the past. The issue is that there are two shared object libraries with the exact same name. If we compile with -L$SAGE_LOCAL/lib are we guaranteed that this will be searched before /usr/lib at runtime. Josh On Nov 8, 6:22 pm, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Nov 9, 3:14 am, Joshua Kantor [EMAIL PROTECTED] wrote: Hi Josh, Yeah. the missing symbol is because its linking against libblas in / usr/lib, which was compiled with some other probably older fortran (why oh why can't all the fortrans get along). I'm curious about what people think is a good solution here. If they have a libblas in /usr/lib thats broken like this (it requires special additional libraries but we can't deduce that at compile time) We are guaranteed a BLAS in $SAGE_LOCAL/lib because we compile it ourselves. So just add -L $SAGE_LOCAL/lib to the flags at the right point and the problem is gone. then as far as I know, the only way to avoid linking against their blas is to change the name of our blas library i.e. libsage_blas and link against that. Or do something like set LD_LIBRARY_PATH=$SAGE_LOCAL (but thats not a good way to solve the problem). Nope, I agree that this is not a solution. And we do add $SAGE_LOCAL/ lib to LD_LIBRARY_PATH which causes the problem in the first place. Thoughts? :) Off to the airport Josh Michael On Nov 8, 1:11 pm, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Nov 8, 9:50 pm, Kate [EMAIL PROTECTED] wrote: Michael, SNIP sage -t devel/sage-main/sage/numerical/test.py ** File test.py, line 4: : from cvxopt.base import * Exception raised: Traceback (most recent call last): File /home/kate/sage/sage-2.8.12-ia64-Linux/local/lib/python2.5/ doctest.py, line 1212, in __run compileflags, 1) in test.globs File doctest __main__.example_0[0], line 1, in module from cvxopt.base import *###line 4: : from cvxopt.base import * ImportError: /usr/lib/libblas.so.3: undefined symbol: e_wsfe ** Sorry to reply to myself so quickly: here we are pulling in the local blas and not the one we compiled with Sage. So that should be easily fixable. Note to self: Need more sleep. Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
On Nov 9, 2007 4:49 AM, Joshua Kantor [EMAIL PROTECTED] wrote: This is something which has confused me in the past. The issue is that there are two shared object libraries with the exact same name. If we compile with -L$SAGE_LOCAL/lib are we guaranteed that this will be searched before /usr/lib at runtime. In short, yes, since that path is in LD_LIBRARY_PATH when Sage runs. I think if the *shared* libraries have exactly the same name, then which will be used at runtime is determined by the library load path. In particular, LD_LIBRARY_PATH if set will be searched first, then the system standard library path. William --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
On Nov 7, 2007 12:52 PM, Joshua Kantor [EMAIL PROTECTED] wrote: Thats expected, since the fix I made was for g95 builds and it worked by linking in f95, which won't be around using gfortran. Should be easy to add a test for gfortran. I was going to test whether or not $SAGE_FORTRAN was set and use an appropriate setup.py depending on whether or not this is true. (if not assume g95, else assume gfortran) Watch out, since SAGE_FORTRAN need *not* be set. All that matters is that when the fortran spkg was installed the variable SAGE_FORTRAN was set. The important thing is the contents of local/bin/sage_fortran/. -- William --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
Thats expected, since the fix I made was for g95 builds and it worked by linking in f95, which won't be around using gfortran. Should be easy to add a test for gfortran. I was going to test whether or not $SAGE_FORTRAN was set and use an appropriate setup.py depending on whether or not this is true. (if not assume g95, else assume gfortran) Josh On Nov 7, 11:08 am, William Stein [EMAIL PROTECTED] wrote: This should really be sent to sage-devel, so I'm forwarding it there. -- Forwarded message -- From: William Stein [EMAIL PROTECTED] Date: Nov 7, 2007 11:07 AM Subject: Re: [sage-support] sage-2.8.12 build report To: [EMAIL PROTECTED] On Nov 7, 2007 11:02 AM, Kate Minola [EMAIL PROTECTED] wrote: I go away for a while, and now SAGE does not build on any of my machines of interest: Compiling from source using gcc-4.2.2, I get *** x86-Linux, ia64-Linux *** While compiling cvxopt-0.8.2.p4, I get gcc -pthread -shared build/temp.linux-i686-2.5/C/base.o build/temp.linux-i686-2.5/C/dense.o build/temp.linux-i686-2.5/C/sparse.o -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib/gcc-lib/i686-pc-linux-gnu/4.0.3 -lm -llapack -lblas -lf95 -o build/lib.linux-i686-2.5/cvxopt/base.so /usr/local/binutils-2.17/x86-Linux-gcc-4.1.1/bin/ld: cannot find -lf95 That's because you're using gfortran. Evidently Josh's fix for cvxopt not fully working fails for people using gfortran. I'll open a trac ticket: http://trac.sagemath.org/sage_trac/ticket/1125 *** x86_64-Linux *** While compiling libfplll-2.1-20071024, I get g++ -shared -nostdlib /usr/lib/../lib64/crti.o /usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/crtbeginS.o .libs/fplll.o -Wl,--rpath -Wl,/usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64 -Wl,--rpath -Wl,/usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64 -lmpfr -lgmp -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2 -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/home/kate/sage/sage-2.8.12-x86_64-Linux/local/lib -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/../../.. /usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64/libstdc++.so -lm -lc -lgcc_s /usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/crtendS.o /usr/lib/../lib64/crtn.o -Wl,-soname -Wl,libfplll.so.0 -o .libs/libfplll.so.0.0.0 /usr/bin/ld: /usr/lib/../lib64/libmpfr.a(exceptions.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/lib/../lib64/libmpfr.a: could not read symbols: Bad value Why is Sage trying to use libmpfr.a out of /usr/lib? Should it not be using the version in [sage]/local/lib? I agree. Note that libfpll is a brand new package in Sage (it does very fast LLL reduction, so is quite important), but it hasn't been as widely tested as other components of Sage. This is now trac #1126: http://trac.sagemath.org/sage_trac/ticket/1126 I've made both trac tickets blockers. We'll fix them at Sage Days next week. William -- William Stein Associate Professor of Mathematics University of Washingtonhttp://wstein.org --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
Ok, then I'll look at sage_fortran --version. On Nov 7, 1:00 pm, William Stein [EMAIL PROTECTED] wrote: On Nov 7, 2007 12:52 PM, Joshua Kantor [EMAIL PROTECTED] wrote: Thats expected, since the fix I made was for g95 builds and it worked by linking in f95, which won't be around using gfortran. Should be easy to add a test for gfortran. I was going to test whether or not $SAGE_FORTRAN was set and use an appropriate setup.py depending on whether or not this is true. (if not assume g95, else assume gfortran) Watch out, since SAGE_FORTRAN need *not* be set. All that matters is that when the fortran spkg was installed the variable SAGE_FORTRAN was set. The important thing is the contents of local/bin/sage_fortran/. -- William --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
On Nov 7, 8:08 pm, William Stein [EMAIL PROTECTED] wrote: This should really be sent to sage-devel, so I'm forwarding it there. -- Forwarded message -- From: William Stein [EMAIL PROTECTED] Date: Nov 7, 2007 11:07 AM Subject: Re: [sage-support] sage-2.8.12 build report To: [EMAIL PROTECTED] On Nov 7, 2007 11:02 AM, Kate Minola [EMAIL PROTECTED] wrote: I go away for a while, and now SAGE does not build on any of my machines of interest: Compiling from source using gcc-4.2.2, I get *** x86-Linux, ia64-Linux *** While compiling cvxopt-0.8.2.p4, I get gcc -pthread -shared build/temp.linux-i686-2.5/C/base.o build/temp.linux-i686-2.5/C/dense.o build/temp.linux-i686-2.5/C/sparse.o -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib/gcc-lib/i686-pc-linux-gnu/4.0.3 -lm -llapack -lblas -lf95 -o build/lib.linux-i686-2.5/cvxopt/base.so /usr/local/binutils-2.17/x86-Linux-gcc-4.1.1/bin/ld: cannot find -lf95 That's because you're using gfortran. Evidently Josh's fix for cvxopt not fully working fails for people using gfortran. I'll open a trac ticket: http://trac.sagemath.org/sage_trac/ticket/1125 *** x86_64-Linux *** While compiling libfplll-2.1-20071024, I get g++ -shared -nostdlib /usr/lib/../lib64/crti.o /usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/crtbeginS.o .libs/fplll.o -Wl,--rpath -Wl,/usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64 -Wl,--rpath -Wl,/usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64 -lmpfr -lgmp -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2 -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/home/kate/sage/sage-2.8.12-x86_64-Linux/local/lib -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/../../.. /usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64/libstdc++.so -lm -lc -lgcc_s /usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/crtendS.o /usr/lib/../lib64/crtn.o -Wl,-soname -Wl,libfplll.so.0 -o .libs/libfplll.so.0.0.0 /usr/bin/ld: /usr/lib/../lib64/libmpfr.a(exceptions.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/lib/../lib64/libmpfr.a: could not read symbols: Bad value Why is Sage trying to use libmpfr.a out of /usr/lib? Should it not be using the version in [sage]/local/lib? I agree. Note that libfpll is a brand new package in Sage (it does very fast LLL reduction, so is quite important), but it hasn't been as widely tested as other components of Sage. This is now trac #1126: Kate, could you try http://sage.math.washington.edu/home/mabshoff/libfplll-2.1-20071024.p0.spkg and report back it that solves the issue? Cheers, Michael http://trac.sagemath.org/sage_trac/ticket/1126 I've made both trac tickets blockers. We'll fix them at Sage Days next week. William -- William Stein Associate Professor of Mathematics University of Washingtonhttp://wstein.org --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
[sage-devel] Re: Fwd: [sage-support] sage-2.8.12 build report
About the cvxopt problem Now the package checks sage_fortran -v and uses a setup.py that links against f95 if you have g95 and a setup.py that links against gfortran otherwise. (this package is in my spkgs cvxopt-0.8.2.p5.spkg) I have tested it with both g95 and gfortran. Josh On Nov 7, 3:16 pm, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Nov 7, 8:08 pm, William Stein [EMAIL PROTECTED] wrote: This should really be sent to sage-devel, so I'm forwarding it there. -- Forwarded message -- From: William Stein [EMAIL PROTECTED] Date: Nov 7, 2007 11:07 AM Subject: Re: [sage-support] sage-2.8.12 build report To: [EMAIL PROTECTED] On Nov 7, 2007 11:02 AM, Kate Minola [EMAIL PROTECTED] wrote: I go away for a while, and now SAGE does not build on any of my machines of interest: Compiling from source using gcc-4.2.2, I get *** x86-Linux, ia64-Linux *** While compiling cvxopt-0.8.2.p4, I get gcc -pthread -shared build/temp.linux-i686-2.5/C/base.o build/temp.linux-i686-2.5/C/dense.o build/temp.linux-i686-2.5/C/sparse.o -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib -L/home/kate/sage/sage-2.8.12-x86-Linux/local/lib/gcc-lib/i686-pc-linux-gnu/4.0.3 -lm -llapack -lblas -lf95 -o build/lib.linux-i686-2.5/cvxopt/base.so /usr/local/binutils-2.17/x86-Linux-gcc-4.1.1/bin/ld: cannot find -lf95 That's because you're using gfortran. Evidently Josh's fix for cvxopt not fully working fails for people using gfortran. I'll open a trac ticket: http://trac.sagemath.org/sage_trac/ticket/1125 *** x86_64-Linux *** While compiling libfplll-2.1-20071024, I get g++ -shared -nostdlib /usr/lib/../lib64/crti.o /usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/crtbeginS.o .libs/fplll.o -Wl,--rpath -Wl,/usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64 -Wl,--rpath -Wl,/usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64 -lmpfr -lgmp -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2 -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/home/kate/sage/sage-2.8.12-x86_64-Linux/local/lib -L/usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/../../.. /usr/local/gcc-4.2.2/x86_64-Linux/lib/../lib64/libstdc++.so -lm -lc -lgcc_s /usr/local/gcc-4.2.2/x86_64-Linux/lib/gcc/x86_64-unknown-linux-gnu/4.2.2/crtendS.o /usr/lib/../lib64/crtn.o -Wl,-soname -Wl,libfplll.so.0 -o .libs/libfplll.so.0.0.0 /usr/bin/ld: /usr/lib/../lib64/libmpfr.a(exceptions.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/lib/../lib64/libmpfr.a: could not read symbols: Bad value Why is Sage trying to use libmpfr.a out of /usr/lib? Should it not be using the version in [sage]/local/lib? I agree. Note that libfpll is a brand new package in Sage (it does very fast LLL reduction, so is quite important), but it hasn't been as widely tested as other components of Sage. This is now trac #1126: Kate, could you try http://sage.math.washington.edu/home/mabshoff/libfplll-2.1-20071024.p... and report back it that solves the issue? Cheers, Michael http://trac.sagemath.org/sage_trac/ticket/1126 I've made both trac tickets blockers. We'll fix them at Sage Days next week. William -- William Stein Associate Professor of Mathematics University of Washingtonhttp://wstein.org --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~--~~~~--~~--~--~---
