Re: [sage-combinat-devel] sage combinat queue broken
Anne Schilling wrote: Anne Schilling wrote: Nicolas M. Thiery wrote: On Fri, May 14, 2010 at 04:15:16PM -0700, Anne Schilling wrote: I disabled several of your patches in the queue since they had import loops and hence one could not launch sage anymore ... trac_8881-functorial_constructions-nt.patch #+disabled ... trac_8890-free_module-cleanup-nt.patch #+disabled ... trac_7980-multiple-realizations-nt.patch #+disabled Now one cannot push anymore beyond trac_8933-subquotient_module_with_basis-fh.patch but at least sage works up to this point. Could you please fix your pushes (and be a bit more careful next time that everything still works before pushing, please?). I did try and it worked for me! Ah, I see, it's not an import loop, but a non-added file. Oops, sorry! Fixed. Thank you! Hi Nicolas, It seems that you broke the sage-combinat queue again since sage does not start after applying your latest patches. To be more precise, sage does not run any more after applying your patch trac_7980-multiple-realizations-nt.patch Best, Anne -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To post to this group, send email to sage-combinat-de...@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
Re: [sage-combinat-devel] sage combinat queue broken
On Sat, May 15, 2010 at 11:46:28PM -0700, Anne Schilling wrote: It seems that you broke the sage-combinat queue again since sage does not start after applying your latest patches. To be more precise, sage does not run any more after applying your patch trac_7980-multiple-realizations-nt.patch Argl, not twice in a row! I had run the full test with needs review, but this time forgot to try with all patches applied ... Sorry. This is fixed now. Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ -- You received this message because you are subscribed to the Google Groups sage-combinat-devel group. To post to this group, send email to sage-combinat-de...@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
[sage-devel] Re: graphs with symmetries?
Hi Robert, 2 weeks have passed :) Looking forward to hear what you have to say on this. Thanks, Dima On Apr 27, 5:14 am, Robert Miller r...@rlmiller.org wrote: I think Robert Miller is the one to ask though. I would love to answer.. After I defend my dissertation in two weeks! -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: [sage-combinat-devel] Freezing
Dear Bruce, dear graph fans, On Sat, May 15, 2010 at 02:46:14PM -0700, Bruce wrote: I am continuing a discussion in a new post. The issue is that if we take a class such as graphs the instances are mutable. It would be useful to have a version which was immutable and therefore hashable. For example, we could then use CombinatorialFreeModule to construct formal linear combinations. Nicolas has pointed out that: In any cases, with Sage 4.4.1, you can actually cheat around this, and pretend that your graph is immutable: sage: G = DiGraph(4) sage: hash(G) Traceback (most recent call last): ... TypeError: graphs are mutable, and thus not hashable sage: G._immutable = True sage: hash(G) -236023159 This is *dangerous*, so use with all due care. But maybe this can be sufficient as a workaround for you until a proper mutability management is implemented for graphs. Is the right way to deal with this (and other similar problems) to have a new class frozengraph but the types that the data is built up from is changed so that lists, sequences, etc. are converted to tuples and dictionaries are converted first to sets and then frozensets? See what's done e.g. with matrices: sage: m = matrix([[1,2],[1,2]]) sage: m.set_immutable? as well as the mutability section in: http://www.sagemath.org/doc/developer/coding_in_python.html (Florent: you may want to throw in this discussion a link to the clone feature) In any cases, this is a fairly technical issue (not in itself, but because it involves a large body of code), so the details of the design should be left to the people in charge of the graph library. Hence, the best way is to open a ticket (please ask for help for that if needed). I am also forwarding this discussion to sage-devel. Best, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: [sage-combinat-devel] Re: Grobner bases
On Fri, May 14, 2010 at 12:13:10PM -0700, Bruce wrote: I think I see what I need to do. Create a dummy class C which is hashable and immutable. Have a dictionary which has objects of C and planar graphs. Every time I create a planar graph, see if it is isomorphic to one in the dictionary. If not add it to the dictionary. Is this sensible? Given a Sage graph, you can ask for an isomorphic copy in canonical form by using G.canonical_label(). So an alternative would be to systematically put your graphs into canonical form whenever you construct / change them. About immutability: it ought to be possible to create immutable/hashable graphs in Sage. Alas this is not yet the case, and this has annoyed us in many occasions. Please open a ticket (if there is not one already). And, ops, I just realized that I inadvertently let a hack of mine slip into the graphviz #7004 patch, and Vincent did not catch it! Promised, that was not intentional! In any cases, with Sage 4.4.1, you can actually cheat around this, and pretend that your graph is immutable: sage: G = DiGraph(4) sage: hash(G) Traceback (most recent call last): ... TypeError: graphs are mutable, and thus not hashable sage: G._immutable = True sage: hash(G) -236023159 This is *dangerous*, so use with all due care. But maybe this can be sufficient as a workaround for you until a proper mutability management is implemented for graphs. Cheers, Nicolas -- Nicolas M. Thiéry Isil nthi...@users.sf.net http://Nicolas.Thiery.name/ -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: sage vs. others by nist
On 05/15/10 09:04 PM, William Stein wrote: Hi, It would be useful to have a page like this excellent page: http://www.scipy.org/NumPy_for_Matlab_Users William That is very impressive. dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
On 05/16/10 07:01 AM, Paul Leopardi wrote: Hi all, I am trying to build Sage 4.4.1 from sourece, using gcc 4.4.1 on SUSE 11.2. So far I have had two failures. I can work around the first, but have no clue about the second. Best, Paul 1. Problem with libreadline Symptom: [...]/local/lib/libreadline.so.6: undefined symbol: PC Workaround: Try to use native librealine. leopa...@linfinit:~/src/sage/sage-4.4.1 ls -l local/lib/libread* lrwxrwxrwx 1 leopardi users 24 2010-05-16 12:37 local/lib/libreadline.a - /usr/lib64/libreadline.a lrwxrwxrwx 1 leopardi users 16 2010-05-16 12:33 local/lib/libreadline.so - libreadline.so.6 lrwxrwxrwx 1 leopardi users 18 2010-05-16 12:35 local/lib/libreadline.so.6 - libreadline.so.6.0 lrwxrwxrwx 1 leopardi users 25 2010-05-16 12:36 local/lib/libreadline.so.6.0 - /lib64/libreadline.so.6.0 There is something strange about readline on OpenSUSE. There some code which does something different on OpenSUSE to other platforms. Perhaps that is not working correctly. It looks a bit of a hack if I'm honest. I don't have time to look at it now, but if you find the readline-$version.spkg, you will find there is something in there which checks a header file and makes a decision based on the header file. It may be that the test does not work on OpenSUSE 11.2. 2. Problem with symmetrica Symptom: /bin/bash: symbol lookup error: [...]/spkg/build/symmetrica-2.0.p5/src/nb.c:4087: undefined reference to `cos' Workaround: ??? Perhaps it needs the maths library linked, -lm, as that is where 'cos' will be. Though that seems a strange thing to be missing. Extracts from install.log: 1. Problem with libreadline readline.c:1112: warning: ‘reset_default_bindings’ defined but not used This, and the tons of other warnings worries me. search.c: In function ‘_rl_nsearch_init’: search.c:213: warning: too many arguments for format How the hell do the developers let that get by? What the where they thinking to ignore such a warning? complete.c: In function ‘fnwidth’: complete.c:643: warning: implicit declaration of function ‘wcwidth’ That probably needs #include wchar.h added to a source file. ../search.c: In function ‘_rl_nsearch_init’: ../search.c:213: warning: too many arguments for format IMHO, it would be better if compilers would throw this as an error. /bin/bash: symbol lookup error: /home/leopardi/src/sage/sage-4.4.1/local/lib/libreadline.so.6: undefined symbol: PC Successfully installed readline-6.0.p1 So readline installs, despite the fact the code looks as though it could do with a major cleanup to me. It is clearly is the cause of many later problems. sage: An error occurred while installing sqlite-3.6.22 sqlite is a well tested bit of code. The developers take testing very seriously - see http://www.sqlite.org/testing.html sage: An error occurred while installing symmetrica-2.0.p5 I would look over the readline.spkg and see if there are any clues there. I think you will find some SUSE specific code there, which may just not work. dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
Hi, these are two (if not three) very different kinds of problems. 1. The readline story on OpenSuse 11.1, 11.2, ArchLinux with Sage Looking at what was done for OpenSuse 11.1 64bit: http://trac.sagemath.org/sage_trac/ticket/4946 and/or for ArchLinux http://trac.sagemath.org/sage_trac/ticket/7610 one should be able to sort out this issue, which seems to come up every now and then. Thanks for reporting! As soon as someone can confirm this (do we have OpenSuse 11.2 64bit on the Sage build/test farm?), fixing it probably isn't too difficult. 2. Symmetrica Having a look at an install log of a successful build of the Symmetrica spkg shows that some of the warnings are to be expected, some not. From the logs (gcc -v Using built-in specs. Target: x86_64- suse-linux ...) I assume that you are using a 64bit OS, but then the Symmetrica spkg log should display something like gcc -O1 -m64 -fPIC - g -DFAST -DALLTRUE ... and not gcc -O1 -fPIC -g -DFAST -DALLTRUE. One could try issuing manually export SAGE64=yes and then hopefully the make run of the Symmetrica spkg works OK. Cheers, Georg -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Sage on Gentoo - Random SIGABRT failures on exit
Hello,
porting Sage to Gentoo progresses well, we now have a split version
where all all dependencies of Sage are installed with portage.
Unfortunately, we experience serious problems on amd64 when exiting
Sage. When doing so, there is a slight chance of getting a SIGABRT
error, which is always looking like this one:
sage -t -force_lib devel/sage/doc/en/constructions/rings.rst
*** glibc detected *** /usr/bin/python2.6: corrupted double-linked
list: 0x04afc6e0 ***
=== Backtrace: =
/lib/libc.so.6[0x7f8fa7a7f808]
/lib/libc.so.6[0x7f8fa7a7fb00]
/lib/libc.so.6[0x7f8fa7a81078]
/lib/libc.so.6(cfree+0x6c)[0x7f8fa7a8424c]
/lib/libc.so.6[0x7f8fa7a40ea5]
/lib/libc.so.6[0x7f8fa7a40ef5]
/usr/lib/libpython2.6.so.1.0[0x7f8fa80bc981]
/usr/lib/libpython2.6.so.1.0[0x7f8fa80bb1e5]
/usr/lib/libpython2.6.so.1.0(PyErr_PrintEx+0x23)[0x7f8fa80bb20a]
/usr/lib/libpython2.6.so.1.0(PyErr_Print+0xe)[0x7f8fa80baf41]
/usr/lib/libpython2.6.so.1.0(PyRun_SimpleFileExFlags+0x248)
[0x7f8fa80baa9d]
/usr/lib/libpython2.6.so.1.0(PyRun_AnyFileExFlags+0x79)
[0x7f8fa80ba335]
/usr/lib/libpython2.6.so.1.0(Py_Main+0xad9)[0x7f8fa80cbafa]
/usr/bin/python2.6(main+0x1b)[0x400847]
/lib/libc.so.6(__libc_start_main+0xe6)[0x7f8fa7a2aa26]
/usr/bin/python2.6[0x400769]
followed by a memory dump which is aborted and the error message: The
doctested process was killed by signal 6
The problem is also that these failures seem to be completely random -
running the failing tests manually again does not show this error
(with a high probability).
I already tried to debug this error by starting Sage with -gdb and
typed several times 2+2 and maxima('2+2'). Again, this worked in
most cases but failed in some. After triggering this error I was able
to find out that PyRun_SimpleFileExFlags (see backtrace above,
declared in Python/pythonrun.c:892) invokes PyRun_FileExFlags which
returns NULL - PyRun_SimpleFileExFlags then tries to print out an
error with PyErr_Print (see backtrace) which leads to SIGABRT.
I have struggled with this error a long time and now I am running out
of ideas ... So these are my questions:
- Is this type of error known ? Has it already been fixed in Sage (I
know that the recent gcc-4.5 error look alike, but we are still using
gcc-4.3.4) ?
- If not, are there any ways to find out more about this error ?
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
Sorry for replying to myself, but I just found this in the current readline spkg's install script: ... if [ -f /etc/SuSE-release ]; then if [ `grep 11.1 /etc/SuSE-release /dev/null; echo $?` -eq 0 ]; then echo OpenSUSE 11.1 detected if [ -d /usr/include/readline/ ]; then echo The development version of libreadline is installed - copying if [ `uname -p` = x86_64 ]; then cp /lib64/libreadline.so.* $SAGE_LOCAL/lib else cp /lib/libreadline.so.* $SAGE_LOCAL/lib fi cp -r /usr/include/readline $SAGE_LOCAL/include exit 0 ... This is both good and bad news. The good thing is, that to enhance this quick'n'dirty trick is trivial --- just copy and paste the above with 11.2 instead of 11.1. The bad news is, that this wouldn't work on OpenSuse 11.3, or 12.0 (so a real fix will require more care); and that specifically Sage on (64bit) OpenSuse 11.2 probably never ever has worked, and might require some more attention than the above two problems. I just created trac ticket #8978 for all that. Cheers, Georg -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
Thanks for the help. I tried again but with export SAGE64=yes before running make. The only difference is that the calls to gcc now include the option -m64. The warning and error messages are the same. Best, Paul --- install.2.log 2010-05-16 15:38:19.0 +1000 +++ install.log 2010-05-16 23:34:28.0 +1000 @@ -1,110348 +1,4 @@ make[1]: Entering directory `/home/leopardi/src/Sage/sage-4.4.1/spkg' -sage-spkg sqlite-3.6.22 21 [...] -Finished installing singular-3-1-0-4-20100214.spkg sage-spkg symmetrica-2.0.p5 21 Warning: Attempted to overwrite SAGE_ROOT environment variable symmetrica-2.0.p5 @@ -110576,76 +232,76 @@ gcc version 4.4.1 [gcc-4_4-branch revision 150839] (SUSE Linux) make[2]: Entering directory `/home/leopardi/src/Sage/sage-4.4.1/spkg/build/symmetrica-2.0.p5/src' -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE bar.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE bi.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE boe.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE bruch.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE classical.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE de.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE di.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE ff.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE galois.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE ga.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE gra.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE hash.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE hiccup.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE io.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE ko.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE list.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE lo.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE ma.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mee.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mem.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mes.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mhe.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mhh.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mhm.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mhp.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mhs.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mmm.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mms.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mod_dg_sbd.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE bar.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE bi.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE boe.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE bruch.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE classical.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE de.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE di.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE ff.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE galois.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE ga.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE gra.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE hash.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE hiccup.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE io.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE ko.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE list.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE lo.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE ma.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mee.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mem.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mes.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mhe.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mhh.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mhm.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mhp.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mhs.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mmm.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mms.c +gcc -c -O1 -m64 -fPIC -g -DFAST -DALLTRUE mod_dg_sbd.c mod_dg_sbd.c: In function ‘embedding_mod_into_ord’: mod_dg_sbd.c:624: warning: passing argument 4 of ‘qsort’ from incompatible pointer type /usr/include/stdlib.h:710: note: expected ‘__compar_fn_t’ but argument is of type ‘INT (*)()’ -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mo.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mpp.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mps.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mse.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE msh.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE msm.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE mss.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE muir.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE na.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE nb.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE nc.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE nu.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE part.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE pee.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE peh.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE pem.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE perm.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE pes.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE phe.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE phh.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE phm.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE phs.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE plet.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE pme.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE pmh.c -gcc -c -O1 -fPIC -g -DFAST -DALLTRUE poly.c -gcc -c -O1 -fPIC -g
[sage-devel] Trac login fails
Hi! Since a couple of hours I try to login to Trac. I can see the tickets, but when trying to login, the server does not answer. Best regards, Simon -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Trac login fails
Hello, It may just be that some time passed since, but it works here ! Nathann -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Trac login fails
On 16 Mai, 15:59, Nathann Cohen nathann.co...@gmail.com wrote: It may just be that some time passed since, but it works here ! No, it is still the same. I load a ticket without problems, but when I then click the login button, it loads forever, and no login screen pops up. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Trac login fails
I just logged into trac ok. John On 16 May 2010 15:12, Simon King simon.k...@nuigalway.ie wrote: On 16 Mai, 15:59, Nathann Cohen nathann.co...@gmail.com wrote: It may just be that some time passed since, but it works here ! No, it is still the same. I load a ticket without problems, but when I then click the login button, it loads forever, and no login screen pops up. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
On 16 Mai, 14:37, Georg S. Weber georgswe...@googlemail.com wrote: 2. Symmetrica Having a look at an install log of a successful build of the Symmetrica spkg shows that some of the warnings are to be expected, some not. From the logs (gcc -v Using built-in specs. Target: x86_64- suse-linux ...) I assume that you are using a 64bit OS, but then the Symmetrica spkg log should display something like gcc -O1 -m64 -fPIC - g -DFAST -DALLTRUE ... and not gcc -O1 -fPIC -g -DFAST -DALLTRUE. Since gcc was built for x86_64, the (implicit) default *is* -m64, i.e. you don't have to specify it. -Leif -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Better visibility of discussion groups
On May 16, 1:37 am, William Stein wst...@gmail.com wrote: It's about time http://sagemath.org got totally reworked for improved usability and simplicity. A design idea from last year is here: (you need safari or firefox, doesn't work in ie) http://boxen.math.washington.edu/home/schilly/www3/ The main difference is that the menu is on the left and each sub-point is always visible. That saves clicks and you always see a thematically structured map of all pages. I'm happy to hear about some feedback or ideas how to make it better - then I can re-implement it so that also IE is happy. Technically, layout is oriented on the left and there are fewer graphics. That speeds up the page even further, download and rendering! And our website should have a couple randomly chosen [quotes] and displayed in a sidebar. I've started that a while ago here: http://sagemath.org/inc/quotes.shtml as a replacement for the random links at the bottom. (It's just one quote, but there is room for 10) discussion lists Personally, when maintaining the website, my main problem is that they get created but nobody tells me about them. I just don't automatically think about adding them to the page if i read about them some time later. download page Well, there is no javascript involved at all and nothing is guessed by javascript - it's done via ssi on the server. If it is ok to use javascript, I can create an intelligent select dialog for the download process, just like on other pages. It's just that when I started to create the page the requirement was that all essential functions should work w/o javascript. So, if it is ok to create a dialog in js i'll do it. As a fallback for js-disabled browsers I can add a link to the mirrors. And btw, the download link at the top menu was pointing to the detected operating system, but then i got mails that this is confusing because there are users who use windows but want to download linux binaries. So, there is no simple solution and all such simplifications need a visible fallback to the general case. H -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Trac login fails
On 16 Mai, 16:16, John Cremona john.crem...@gmail.com wrote: I just logged into trac ok. Yes, meanwhile it works for me as well. Cheers, Simon -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Ctrl + C and Cython
Hello everybody !!! I have been working on a short patch to find an induced subgraph (#8922). It is bruteforce, and is written in Cython to be a bit more efficient. While it seems to deal very well with the few real instances I gave it, I also tried it on home-made instances on which it was bound to work for... a long time :-) Well, it worked, for a long time, and there was no way for me to stop it in the middle of its computations, as the function being written in Cython, the shortcut Ctrl + C does not work Is there any trick in this case ? :-) Thanks ! Nathann -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Sage on Gentoo - Random SIGABRT failures on exit
On Sun, May 16, 2010 at 05:55:10AM -0700, cschwan wrote: Hello, porting Sage to Gentoo progresses well, we now have a split version where all all dependencies of Sage are installed with portage. Unfortunately, we experience serious problems on amd64 when exiting Sage. When doing so, there is a slight chance of getting a SIGABRT error, which is always looking like this one: sage -t -force_lib devel/sage/doc/en/constructions/rings.rst *** glibc detected *** /usr/bin/python2.6: corrupted double-linked list: 0x04afc6e0 *** snip followed by a memory dump which is aborted and the error message: The doctested process was killed by signal 6 snip I have struggled with this error a long time and now I am running out of ideas ... So these are my questions: - Is this type of error known ? Has it already been fixed in Sage (I know that the recent gcc-4.5 error look alike, but we are still using gcc-4.3.4) ? - If not, are there any ways to find out more about this error ? Did you try running it through valgrind? For memory errors like this that might give some more clues. 'sage -t' has a -valgrind option similar to -gdb that does this for you. -Willem Jan -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Help needed with TestSuite
Hello, If I add a new file into Sage without TestSuite(...).run(), then sage -coverage shows an ERROR for this file. Does this mean that a patch without such a test has no chances to be merged? I really hope this is not the case yet... I think that TestSuite is an awesome idea and it did help me to fix some potential bugs. However when I derive from existing classes that have no TestSuite testing, it seems that my class is blamed for all the errors and inconsistencies of these existing classes. Of course, they also should be fixed, but it may not be very clear how. In particular, can anyone give me a hint what should I do with the following (my class has the same error): P2 = ProjectiveSpace(2, QQ) e = P2(1,1,1) e._test_category() Traceback (most recent call last): ... File element.pyx, line 472, in sage.structure.element.Element._test_category (sage/structure/ element.c:3676) File /home/novoselt/sage/local/lib/python/unittest.py, line 325, in failUnless if not expr: raise self.failureException, msg AssertionError I have also discovered that even this fails (in Sage 4.4): TestSuite(QQ[x]).run() Thank you! Andrey -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Help needed with TestSuite
I had noticed that, after bringing a coupld of files up to 100% coverage, it was annoying to get this Error message. There seems to be nothing about TestSuite in the developers guide, so it cannot (yet) be a requirement to implement it! After trying TestSuite? I found the page in the reference manual (under Miscellaneous, in the section Unit testing for Sage objects). But if this is intended to be a requirement, or even a desirable feature of every Sage class, there needs to be some better instruction on what to do. John On 16 May 2010 17:52, Andrey Novoseltsev novos...@gmail.com wrote: Hello, If I add a new file into Sage without TestSuite(...).run(), then sage -coverage shows an ERROR for this file. Does this mean that a patch without such a test has no chances to be merged? I really hope this is not the case yet... I think that TestSuite is an awesome idea and it did help me to fix some potential bugs. However when I derive from existing classes that have no TestSuite testing, it seems that my class is blamed for all the errors and inconsistencies of these existing classes. Of course, they also should be fixed, but it may not be very clear how. In particular, can anyone give me a hint what should I do with the following (my class has the same error): P2 = ProjectiveSpace(2, QQ) e = P2(1,1,1) e._test_category() Traceback (most recent call last): ... File element.pyx, line 472, in sage.structure.element.Element._test_category (sage/structure/ element.c:3676) File /home/novoselt/sage/local/lib/python/unittest.py, line 325, in failUnless if not expr: raise self.failureException, msg AssertionError I have also discovered that even this fails (in Sage 4.4): TestSuite(QQ[x]).run() Thank you! Andrey -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] graphs with symmetries?
On Mon, Apr 26, 2010 at 4:59 PM, Dima Pasechnik dimp...@gmail.com wrote: I work a lot with (large, say, 5000 vertices) (di)graphs having large automorphism groups (often vertex-transitive, etc). You should post up some examples somewhere, so I can get a sense of Sage's performance with these kinds of graphs. Such graphs are very efficiently represented in GAP (via GRAPE) package. (one needs to keep representatives of arc orbits, and few other things, to be able to check adjacency of vertices, say) These kinds of graphs often arise in e.g. coding theory. Is there anything like this in Sage? Everything you've described can be done in Sage, but I think that's not quite the question. There aren't any specialized data structures for keeping track of these things, just the usual digraph objects and permutation group objects. My primary use of Sage is an interface between GAP and cvxopt, so e.g. I can compute such graph invariants as Lovasz theta-function. The size of graphs makes it mandatory to use a compact representation, and collapsed adjacency matrices, that carry enough information about underlying algebra (e.g. graph eigenvalues). It would be helpful if you could explain these in a bit more detail. E.g. are these graphs highly sparse? I wonder if Sage should get its own graph with symmetries class (unless there is already one...) There isn't one. Right now even the automorphism group itself could be better, since the vertices and the points that get permuted aren't even the same. There is plenty of room for improvement... Dima -- Robert L. Miller http://www.rlmiller.org/ -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Help needed with TestSuite
Thank you, you made my day! Andrey On May 16, 11:15 am, John Cremona john.crem...@gmail.com wrote: I had noticed that, after bringing a coupld of files up to 100% coverage, it was annoying to get this Error message. There seems to be nothing about TestSuite in the developers guide, so it cannot (yet) be a requirement to implement it! After trying TestSuite? I found the page in the reference manual (under Miscellaneous, in the section Unit testing for Sage objects). But if this is intended to be a requirement, or even a desirable feature of every Sage class, there needs to be some better instruction on what to do. John On 16 May 2010 17:52, Andrey Novoseltsev novos...@gmail.com wrote: Hello, If I add a new file into Sage without TestSuite(...).run(), then sage -coverage shows an ERROR for this file. Does this mean that a patch without such a test has no chances to be merged? I really hope this is not the case yet... I think that TestSuite is an awesome idea and it did help me to fix some potential bugs. However when I derive from existing classes that have no TestSuite testing, it seems that my class is blamed for all the errors and inconsistencies of these existing classes. Of course, they also should be fixed, but it may not be very clear how. In particular, can anyone give me a hint what should I do with the following (my class has the same error): P2 = ProjectiveSpace(2, QQ) e = P2(1,1,1) e._test_category() Traceback (most recent call last): ... File element.pyx, line 472, in sage.structure.element.Element._test_category (sage/structure/ element.c:3676) File /home/novoselt/sage/local/lib/python/unittest.py, line 325, in failUnless if not expr: raise self.failureException, msg AssertionError I have also discovered that even this fails (in Sage 4.4): TestSuite(QQ[x]).run() Thank you! Andrey -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group athttp://groups.google.com/group/sage-devel URL:http://www.sagemath.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group athttp://groups.google.com/group/sage-devel URL:http://www.sagemath.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Ctrl + C and Cython
On Sun, May 16, 2010 at 9:44 AM, Nathann Cohen nathann.co...@gmail.com wrote: Hello everybody !!! I have been working on a short patch to find an induced subgraph (#8922). It is bruteforce, and is written in Cython to be a bit more efficient. While it seems to deal very well with the few real instances I gave it, I also tried it on home-made instances on which it was bound to work for... a long time :-) Well, it worked, for a long time, and there was no way for me to stop it in the middle of its computations, as the function being written in Cython, the shortcut Ctrl + C does not work Is there any trick in this case ? :-) Search the source for something like: include interrupt.pxi _sig_on ...do stuff in C, where interrupt will now work... _sig_off Thanks ! Nathann -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -- Robert L. Miller http://www.rlmiller.org/ -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Sage on Gentoo - Random SIGABRT failures on exit
I already tried valgrind but it did not work - how do I exactly use it ? When I run sage -valgrind -t -force_lib devel/sage/doc/en/reference/sage/ categories/examples/algebras_with_basis.rst I get: -- | Sage Version 4.4.1, Release Date: 2010-05-02 | | Type notebook() for the GUI, and license() for information.| -- /opt/sage/local/bin/sage-ipython Log file is /home/gnuke/.sage/valgrind/sage-memcheck.%p Using default flags: --leak-resolution=high --log-file=/home/gnuke/.sage/valgrind/sage- memcheck.%p --leak-check=full --num-callers=25 --suppressions=/opt/ sage/local/lib/valgrind/sage.supp but nothing happens. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Better visibility of discussion groups
On Sun, May 16, 2010 at 8:37 AM, Harald Schilly harald.schi...@gmail.com wrote: On May 16, 1:37 am, William Stein wst...@gmail.com wrote: It's about time http://sagemath.org got totally reworked for improved usability and simplicity. A design idea from last year is here: (you need safari or firefox, doesn't work in ie) http://boxen.math.washington.edu/home/schilly/www3/ The main difference is that the menu is on the left and each sub-point is always visible. That saves clicks and you always see a thematically structured map of all pages. I'm happy to hear about some feedback or ideas how to make it better - then I can re-implement it so that also IE is happy. Technically, layout is oriented on the left and there are fewer graphics. That speeds up the page even further, download and rendering! Having just tried the above, I'm not convinced that such a dramatic change is a good idea right now. For starters, most of the buttons on the left aren't even visible when I load the page. Also, personally it seems odd for the buttons to be on the left, not the right. And our website should have a couple randomly chosen [quotes] and displayed in a sidebar. I've started that a while ago here: http://sagemath.org/inc/quotes.shtml as a replacement for the random links at the bottom. (It's just one quote, but there is room for 10) That seems to be a google search that list pages that mention Sage. This should not be on the main page. What should be is some selection from http://sagemath.org/library-stories.html discussion lists Personally, when maintaining the website, my main problem is that they get created but nobody tells me about them. I just don't automatically think about adding them to the page if i read about them some time later. True. There is no solution to this problem, except increased communication, *and* a clear link that says Do you know about a Sage-related discussion group that should be listed here? If so, click here to report it. That link could just be a mailto:harald. download page Well, there is no javascript involved at all and nothing is guessed by javascript - it's done via ssi on the server. If it is ok to use javascript, I can create an intelligent select dialog for the download process, just like on other pages. It's just that when I started to create the page the requirement was that all essential functions should work w/o javascript. So, if it is ok to create a dialog in js i'll do it. As a fallback for js-disabled browsers I can add a link to the mirrors. I'm perfectly fine with you using Javascript to make the download process easier for end users. That no javascript thing was I think some weird obsession that Michael Abshoff had. The main thing we want to avoid is making it hard to setup mirror sites. Anyway, sagemath.org has javascript all over it already. And btw, the download link at the top menu was pointing to the detected operating system, but then i got mails that this is confusing because there are users who use windows but want to download linux binaries. So, there is no simple solution and all such simplifications need a visible fallback to the general case. There are solutions that appear simpler to end users.Almost any major software project's download solution is simpler that what we currently do. -- William H -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -- William Stein Professor of Mathematics University of Washington http://wstein.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
Well, one last try, before I give up. You should have a (temporary) directory /home/leopardi/src/Sage/sage-4.4.1/spkg/build/ symmetrica-2.0.p5/. In its subdirectory src/ there is a file makefile. Change its last line (line 12) from $(CC) $(CFLAGS) -lm test.c bar.o bi.o boe.o bruch.o classical.o de.o di.o ff.o galois.o ga.o gra.o hash.o hiccup.o io.o ko.o list.o lo.o ma.o mee.o mem.o mes.o mhe.o mhh.o mhm.o mhp.o mhs.o mmm.o mms.o mod_dg_sbd.o mo.o mpp.o mps.o mse.o msh.o msm.o mss.o muir.o na.o nb.o nc.o nu.o part.o pee.o peh.o pem.o perm.o pes.o phe.o phh.o phm.o phs.o plet.o pme.o pmh.o poly.o ppe.o pph.o ppm.o ppp.o pps.o pr.o pse.o psh.o psm.o pss.o rest.o rh.o sab.o sb.o sc.o sr.o ta.o teh.o tem.o tep.o tes.o the.o thm.o thp.o ths.o tme.o tmh.o tmp.o tms.o tpe.o tph.o tpm.o tps.o tse.o tsh.o tsm.o tsp.o vc.o zo.o zykelind.o zyk.o -o test to $(CC) $(CFLAGS) test.c bar.o bi.o boe.o bruch.o classical.o de.o di.o ff.o galois.o ga.o gra.o hash.o hiccup.o io.o ko.o list.o lo.o ma.o mee.o mem.o mes.o mhe.o mhh.o mhm.o mhp.o mhs.o mmm.o mms.o mod_dg_sbd.o mo.o mpp.o mps.o mse.o msh.o msm.o mss.o muir.o na.o nb.o nc.o nu.o part.o pee.o peh.o pem.o perm.o pes.o phe.o phh.o phm.o phs.o plet.o pme.o pmh.o poly.o ppe.o pph.o ppm.o ppp.o pps.o pr.o pse.o psh.o psm.o pss.o rest.o rh.o sab.o sb.o sc.o sr.o ta.o teh.o tem.o tep.o tes.o the.o thm.o thp.o ths.o tme.o tmh.o tmp.o tms.o tpe.o tph.o tpm.o tps.o tse.o tsh.o tsm.o tsp.o vc.o zo.o zykelind.o zyk.o -lm -o test i.e. just move the math library link option -lm somewhere *after* the object file nb.o, but before (I did it *right* before) the last -o test. (Reason: The Symmetrica code is perhaps ugly, but seems correct to me. As for the makefile: a library containing the definition of a function should appear after any source files, or object files, which use it. I would have assumed that all incarnations of gcc also accept the other way around, but maybe the one shipping with OpenSuse 11.2 doesn't like it.) Now from the first mentioned directory (the one containing src/), issue ./spkg-install. If that works, fine. If not, then you may also just delete the last two lines of the makefile mentioned (and then do ./spkg-install from the directory one above, as already mentioned) --- the binary test created by them is not used by Sage, so there. :-) Cheers, Georg -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Sage on Gentoo - Random SIGABRT failures on exit
On Sun, May 16, 2010 at 11:59:24AM -0700, cschwan wrote: I already tried valgrind but it did not work - how do I exactly use it ? When I run sage -valgrind -t -force_lib devel/sage/doc/en/reference/sage/ categories/examples/algebras_with_basis.rst I get: -- | Sage Version 4.4.1, Release Date: 2010-05-02 | | Type notebook() for the GUI, and license() for information.| -- /opt/sage/local/bin/sage-ipython Log file is /home/gnuke/.sage/valgrind/sage-memcheck.%p Using default flags: --leak-resolution=high --log-file=/home/gnuke/.sage/valgrind/sage- memcheck.%p --leak-check=full --num-callers=25 --suppressions=/opt/ sage/local/lib/valgrind/sage.supp but nothing happens. Ah, right. You need to put a valgrind suppressions file in /opt/sage/local/lib/valgrind/sage.supp. You can use the one that's part of the optional valgrind spkg available from http://sagemath.org/packages/optional/ . I've been using this one: http://www.math.leidenuniv.nl/~wpalenst/sage/sage.supp which suppresses some more false positives from python (but not all of them). I unfortunately don't remember the source of that file anymore; I've had it around for too long for various python-based projects. -Willem Jan -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Sage on Gentoo - Random SIGABRT failures on exit
2010/5/16 cschwan csch...@students.uni-mainz.de:
I already tried valgrind but it did not work - how do I exactly use
it ? When I run
sage -valgrind -t -force_lib devel/sage/doc/en/reference/sage/
categories/examples/algebras_with_basis.rst
I get:
--
| Sage Version 4.4.1, Release Date: 2010-05-02 |
| Type notebook() for the GUI, and license() for information. |
--
/opt/sage/local/bin/sage-ipython
Log file is /home/gnuke/.sage/valgrind/sage-memcheck.%p
Using default flags:
--leak-resolution=high --log-file=/home/gnuke/.sage/valgrind/sage-
memcheck.%p --leak-check=full --num-callers=25 --suppressions=/opt/
sage/local/lib/valgrind/sage.supp
but nothing happens.
The procedure I use in the Mandriva package is:
1. set environment variables from /usr/bin/sage
--%--
#!/bin/sh
export CUR=`pwd`
export DOT_SAGE=$HOME/.sage/
export DOT_SAGENB=$DOT_SAGE
mkdir -p $DOT_SAGE/{maxima,sympow,tmp}
export SAGE_TESTDIR=$DOT_SAGE/tmp
export SAGE_ROOT=/usr/share/sage
export SAGE_LOCAL=/usr/share/sage/local
export SAGE_DATA=/usr/share/sage/data
export SAGE_DEVEL=/usr/share/sage/devel
export SAGE_DOC=/usr/share/sage/devel/doc
export PATH=/usr/share/sage/local/bin:/usr/share/cdd/bin:$PATH
export SINGULARPATH=/usr/share/singular/LIB
export SINGULAR_BIN_DIR=/usr/share/singular/i386
export PYTHONPATH=/usr/share/sage/site-packages
export SAGE_CBLAS=cblas
export SAGE_FORTRAN=/usr/bin/gfortran
export SAGE_FORTRAN_LIB=`gfortran --print-file-name=libgfortran.so`
export SYMPOW_DIR=$DOT_SAGE/sympow
/usr/share/sage/local/bin/sage-sage $@
--%--
the above is generated for i586, so, just cutpaste it, but the last
line on a xterm
2. set ipython env
export IPYTHONDIR=$DOT_SAGE/ipython
export IPYTHONRC=ipythonrc
3. run valgrind
valgrind --db-attach=yes --freelist-vol=1 python
/usr/share/sage/local/bin/sage-ipython
This is a procedure I documented in a commit, but it should not
modify much for
gentoo. It works as sage -gdb or sage -valgrind, but I think I prefer things the
harder way, or where I have more control of what is going on...
On the above procedure, I would also cutpaste the doctest in sage prompt.
If valgrind reports too many memory errors, it may be harder, as you must say
'N' every time it asks if you want to attach gdb...
Paulo
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
Re: [sage-devel] Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
Thanks, Georg, I moved -lm to just before -o test in the makefile for symmetrica-2.0.p5, used tar zcf to creat a replacement spkg, and the make now continues past symmetrica-2.0.p5. The make is still running. I have the following environment variables defined: SAGE64=yes SAGE_CHECK=yes SAGE_ROOT= Best, Paul -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
In the makefile for symmetrica, the -lm has to go after all the .o files that need libm.a or libm.so. This is standard practice for GNU binutils and not a quirk of OpenSUSE, so I don't see why the build should have worked with any other Linux distribution (remember that I have exported SAGE_CHECK=yes ). In the GNU binutils doc under options: http://sourceware.org/binutils/docs-2.20/ld/Options.html#Options -l namespec --library=namespec Add the archive or object file specified by namespec to the list of files to link. This option may be used any number of times. If namespec is of the form :filename, ld will search the library path for a file called filename, otherwise it will search the library path for a file called libnamespec.a. On systems which support shared libraries, ld may also search for files other than libnamespec.a. Specifically, on ELF and SunOS systems, ld will search a directory for a library called libnamespec.so before searching for one called libnamespec.a. (By convention, a .so extension indicates a shared library.) Note that this behavior does not apply to :filename, which always specifies a file called filename. The linker will search an archive only once, at the location where it is specified on the command line. If the archive defines a symbol which was undefined in some object which appeared before the archive on the command line, the linker will include the appropriate file(s) from the archive. However, an undefined symbol in an object appearing later on the command line will not cause the linker to search the archive again. See the -( option for a way to force the linker to search archives multiple times. You may list the same archive multiple times on the command line. This type of archive searching is standard for Unix linkers. However, if you are using ld on AIX, note that it is different from the behaviour of the AIX linker. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Sage 4.4.1 build failures with gcc 4.4.1 on SUSE 11.2
Hi Georg, On Sun, May 16, 2010 at 10:37 PM, Georg S. Weber georgswe...@googlemail.com wrote: SNIP (do we have OpenSuse 11.2 64bit on the Sage build/test farm?) The build farm of Linux virtual machines has openSUSE 11.1 in 32- and 64-bit versions. The Skynet cluster has 64-bit openSUSE 11.1 and 64-bit SUSE Linux Enterprise Server 10 SP1. -- Regards Minh Van Nguyen -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Coercion of inexact fields
I think Robert's said it fairly well. Which is good, since I'll have spotty internet for the next couple weeks, and my battery is about to run out. On 5/15/10, Robert Bradshaw rober...@math.washington.edu wrote: On May 14, 2010, at 11:13 AM, Simon King wrote: Hi Robert! On 14 Mai, 18:34, Robert Bradshaw rober...@math.washington.edu wrote: 1. Do you agree this is a bug? The p-adic fields are of capped precision, not set precision, but each element remembers its own actual precision, so this is why the coercion goes in that direction, and I don't think its a bug. What does capped or set precision mean? Is it like this? - The precision of the elements of RR is determined by RR, and so the precision must be non-increasing along a coercion. Yep, otherwise elements have spuriously high precision. - The precision of the elements of one p-adic ring can be different, but there is an upper bound for the precision. This upper bound must be non-decreasing under coercion. Yep, otherwise we loose information. If we're going to change this, it should be on its own ticket as it's quite a big change. I thought it is just changing one byte: '' to ''. :). There are many places I could just change '' to '' that would wreck havoc all over, the above would be a big semantic change. Anyway, if you say we should keep it then I need to do a change in a different place: The Completion construction functor allows merging, and the rule is that two Completion functors with respect to the same prime (resp. +Infinity, for the completion functor yielding RR) are merged so that the *smaller* precision results. By consequence, if you have two parent structures based on p-adic rings of different precision, then it could be that there is no coercion into their pushout. Solution: In the merge method, I can distinguish the case completion at +Infinity and completion at some prime, so that the smaller precision is chosen in the first case and the bigger precision in the second case. Yes, we'd have to special case this. On May 14, 2010, at 11:39 AM, Simon King wrote: Would the following be what you want? sage: R1.a = Zp(5,prec=20)[] sage: R2 = Qp(5,prec=40) sage: R2(1)+a (1 + O(5^20))*a + (1 + O(5^40)) This results when one changes the merge method (and makes fraction field functor and completion functor commute). Yep, that looks right to me. (Sometimes, though, I wonder if the generator of a inexact ring should be considered to have infinite precision, but that's totally separate.) - Robert -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
