[sage-devel] Re: VirtualBox testers needed
On May 30, 10:04 am, Jeroen Demeyer wrote: > All of you who had trouble with building Sage from source inside a > VirtualBox: > > please test new source tarball > athttp://boxen.math.washington.edu/home/release/sage-5.0.1.rc0/sage-5.0... Built and all tests passed using 'make ptestlong'. This is on Ubuntu 12.04 (64 bit) running in vmplayer 4.03 on Windows 7. Cheers, Adam -- 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: how do I build sage-5.0 on virtualbox?
On May 21, 4:02 pm, Jeroen Demeyer wrote: > On 2012-05-21 23:21, Adam Webb wrote: > > > > > > > > > > >> William (or anyone else having this problem), can you test the SPKG > >> Jeroen has put up on #12970 ? Just unpack a sage source tarball, and > >> replace mpir-2.4.0.p3.spkg > >> withhttp://boxen.math.washington.edu/home/jdemeyer/spkg/mpir-2.4.0.p5.spkg. > > >> I'd test it myself but I don't have access to my VM for the next month > >> or so. > > >> -Keshav > > >> > >> Join us in #sagemath on irc.freenode.net ! > > > I tried the spkg and everything built without problems. A 'make - > > ptestlong' also passed. > > This is using Ubuntu 12.04 (64 bit) on vmplayer in Windows 7. > > Please > 1) Mention your CPU model > 2) Send the MPIR build log My cpu is an Intel Core i7-2600. BTW I am using VMware Player 4.0.3. For what it is worth, cpuinfo shows the following flags: flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology tsc_reliable nonstop_tsc aperfmperf pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 popcnt hypervisor lahf_lm ida arat epb xsaveopt pln pts dts Log file is at http://sage.math.washington.edu/home/awebb/mpir-2.4.0.p5.log. Cheers, Adam -- 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: how do I build sage-5.0 on virtualbox?
> > William (or anyone else having this problem), can you test the SPKG > Jeroen has put up on #12970 ? Just unpack a sage source tarball, and > replace mpir-2.4.0.p3.spkg > withhttp://boxen.math.washington.edu/home/jdemeyer/spkg/mpir-2.4.0.p5.spkg. > > I'd test it myself but I don't have access to my VM for the next month > or so. > > -Keshav > > > Join us in #sagemath on irc.freenode.net ! I tried the spkg and everything built without problems. A 'make - ptestlong' also passed. This is using Ubuntu 12.04 (64 bit) on vmplayer in Windows 7. Cheers, Adam -- 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: how do I build sage-5.0 on virtualbox?
> > The restriction is not due to the physical CPU at all. The physical > CPU's architecture is equal to the architecture that MPIR detects. > That is not the problem. The problem is that Virtualbox does not > support certain instructions inside the VM. And that means that all > VMs made by people using Virtualbox will probably have this problem. > The conditions for this problem to occur are: 1) the physical CPU > supports some instruction x; and 2) Virtualbox does not support > running instruction x inside VMs; and 3) MPIR gets built with > instruction x somewhere in its binary (or fails during the build due > to instruction x being run somewhere in the build process), because it > knew that the *physical* CPU supported that instruction, while it did > not know that the *virtual* CPU does *not* support that instruction. > > At least, that's how I understand the situation. > > -Keshav > > > Join us in #sagemath on irc.freenode.net !- Hide quoted text - > > - Show quoted text - Just to add my 2 cents. I am using vmplayer which I believe is simliar overall if not in implementation detail. However it supports a somewhat different set of CPU instructions. Fortunately, the solution posted here for virtual box, using march=native, works equally well for vmplayer. Adam -- 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: Ubuntu 11.10 testers needed
On Jan 7, 5:39 am, John Cremona wrote: > (24 hours later) > > Successfully built 4.8.alpha6 > withhttp://sage.math.washington.edu/home/palmieri/SPKG/readline-6.2.p3.spkg > put into spkg/standard before starting to build. All long tests pass > and there is no warning about readline, and history etc all works > normally. > > John > I did a similar build on a virtual machine (given half the resources on a Gateway PC, i7, 8 GB Ram, Windows 7 Home Premium)). I had had problems with readline previously with this setup so I used the new spkg. Atlas reported errors as it always does but continued anyway. I used make -j4 for the build and the test. using 'make ptestlong' resulted in: All tests passed! Total time for all tests: 1639.2 seconds Adam -- 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: DirichletGroup(1)[0] values?
On Sep 6, 6:46 am, Matthew Alderson wrote: > Hello, > > I'm using Sage 4.6.2 on my local machine and when I use the command > > DirichletGroup(1)[0].values() > > it gives me the correct values (namely [1]). However, in Sage 4.7.1, it > seems to return [0], which is > false since everything is coprime to 1. > > Thank you, > > Matt I also get [0] in 4.7.1. This is built from source on Ubuntu 11.04 running in a virtual machine (32 bit and 64 bit versions). Adam -- 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: Vote on making GNU patch a standard package
On Jul 2, 8:01 am, David Kirkby wrote: > On 1 July 2010 20:25, Mike Hansen wrote: > > > > > On Thu, Jul 1, 2010 at 12:05 PM, David Kirkby > > wrote: > >> I don't understand your proposal. Would it need the patch command > >> added to Sage? I don't understand your method, so can't comment > >> really. > > > William's proposal is to > > > 1) Standardize the filenames of patches so that the only file which > > patches ./src/foo/bar/xyz.py is ./patches/foo/bar/xyz.py.patch > > > 2) Only the .patch file is checked into the repository. > > > 3) When doing "sage -spkg" to create an spkg, it goes through all of > > the patches under ./patches/ and uses the patch command to make the > > patched file which is copied over. In the above example, the "sage > > -spkg" script would automatically make ./patches/foo/bar/xyz.py from > > ./src/foo/bar/xyz.py and ./patches/foo/bar/xyz.py.patch. Thus, only > > patch needs to be installed on the machine which creates the original > > spkg. > > Many patches are currently applied conditionally - usually dependent > on the operating system of the system to which the Sage source will be > installed. One I can think of is applied only on the newer sun4v > systems like 't2' but not on older SPARC systems. But whether it gets > applied or not also depends on an environment variable. > > Whilst applying patch as a result of an environment variable is not > common, applying them by operating system is very common. > > I don't see how that situation could be handled by this method unless > we distribute a source for OS X, another for Linux, another for > Solaris ... etc etc. > > Dave I felt that the important part of the proposal was the use of patches. I don't know if there will really be a lot of space saved but I think that is less important. The advantage of patches as I see it is that it is a well known and used method of making changes to source code. Having the original source and applying patches is the logical thing to do. The question seems to be when to apply the patches. Can the patches be applied when the spkgs are made? Are there patches which are applied conditionally at install time? My personal preference is to patch as late as possible. When I get the spkg I want the original source and not a patched version. Then I still have the option of adding/removing/changing patches as needed for my system. If I understand the proposal. 1. the diffs are made and included in the patches directory (details of naming aside) 2. when sage -pkg is used the patched files are created 2b. conditional patches for specific systems and OS's could also made (do we expect a lot of these?) 3. When the package is installed the patched files are copied over as they are now The bigger changes would be in the sage -pkg mechanism. The spkg- install would also have to have conditions to copy the correct patches for a specific system or OS but that is already the case. The question then is if it is a burden to carry around the patches for different systems. However, isn't this already the case? Adam -- 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: Vote on making GNU patch a standard package
[Yes] Include GNU patch as a standard package in Sage Sounds good to me. Adam -- 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: Test your Python build
> > I would not rule out any unexpected side-effects of some old patch > > though. It is probably a good idea to review the patches to remove > > anything that is no longer needed. > > > Adam > > Hi Adam. > > I noticed there was a patch to disutils in Sage, but removing it did not allow > it to build on my system. I would be interested if it does on yours. You > should > find it easily in spkg-install - just comment it out. > > I do wonder if there should be a different method of applying patches in Sage > to > .spkg files. One option is that a checksum is computed of the file being > overwritten, and the patch will only apply if the checksum is the same. That > way, if the upstream source gets updated, the patch can't be applied without > someone manually doing things with it. > > Dave Removing the patch did not allow python to build on either of my systems. Adam -- 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: Test your Python build
On Jun 24, 11:42 pm, "Dr. David Kirkby" wrote: > On 06/24/10 08:45 PM, Fran ois Bissey wrote: > > > > >> On 06/24/10 04:14 PM, Adam Webb wrote: > >>> test_distutils passes if I use a plain python 2.6.5 tarball. This is > >>> consistent with the problem being in Sage or at least in the > >>> environment used for building packages. > > >>> Adam > > >> That's interesting! > > >> So far everyone seems to see this. > > >> * You on Scientific Linux > >> * Me on OpenSolaris > >> * Me on Solaris 10 > >> * Alex Ghitza on what I think is probably archlinux though I'm not sure. > >> * Francois on Gentoo. > > > Just to be clear I was pointing that the test is skipped because it > > is known to fail in the "system" package. The snippet I sent is part > > of what is in every gentoo system regardless of whether they use > > sage or not. > > I was pointing out that some python tests are known to fail at the linux > > distro level. > > > Francois > > I wonder if the problem is fixed in Python 2.6.5, since the test passes for > Adam > with 2.6.5. > > The problem with Python in Sage is there are so many patches, that is makes it > difficult to update. Many patches are copied over Python files - I don't know > how carefully these changed files have been updated as python has been > updated, > but some are years old. The chances someone has screwed up during that time is > quite high. > > 'hg log' shows 68 entries. > > Dave Hi, I did a another test and test_distutils also passes for a plain 2.6.4. In fact, I don't think I have ever seen this one fail. Since my system Python is only 2.4 I have usually have to compile a newer one. Normally, I get failures on modules due to missing devel packages. Naturally failures may vary between distributions. Missing modules may or may not have an impact on Sage. I would not rule out any unexpected side-effects of some old patch though. It is probably a good idea to review the patches to remove anything that is no longer needed. Adam -- 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: Test your Python build
On Jun 24, 11:42 pm, "Dr. David Kirkby" wrote: > On 06/24/10 08:45 PM, Fran ois Bissey wrote: > > > > >> On 06/24/10 04:14 PM, Adam Webb wrote: > >>> test_distutils passes if I use a plain python 2.6.5 tarball. This is > >>> consistent with the problem being in Sage or at least in the > >>> environment used for building packages. > > >>> Adam > > >> That's interesting! > > >> So far everyone seems to see this. > > >> * You on Scientific Linux > >> * Me on OpenSolaris > >> * Me on Solaris 10 > >> * Alex Ghitza on what I think is probably archlinux though I'm not sure. > >> * Francois on Gentoo. > > > Just to be clear I was pointing that the test is skipped because it > > is known to fail in the "system" package. The snippet I sent is part > > of what is in every gentoo system regardless of whether they use > > sage or not. > > I was pointing out that some python tests are known to fail at the linux > > distro level. > > > Francois > > I wonder if the problem is fixed in Python 2.6.5, since the test passes for > Adam > with 2.6.5. > > The problem with Python in Sage is there are so many patches, that is makes it > difficult to update. Many patches are copied over Python files - I don't know > how carefully these changed files have been updated as python has been > updated, > but some are years old. The chances someone has screwed up during that time is > quite high. > > 'hg log' shows 68 entries. > > Dave Hi, I did a another test and test_distutils also passes for a plain 2.6.4. In fact, I don't think I have ever seen this one fail. Since my system Python is only 2.4 I have usually have to compile a newer one. Normally, I get failures on modules due to missing devel packages. Naturally failures may vary between distributions. Missing modules may or may not have an impact on Sage. I would not rule out any unexpected side-effects of some old patch though. It is probably a good idea to review the patches to remove anything that is no longer needed. Adam -- 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: Test your Python build
Hi, I get two test errors on Scientific Linux 5.1 (32 bit). test_grp and test_distutils test_grp is a normal problem on this system. test test_grp failed -- Traceback (most recent call last): File "/home/math/sage/spkg/build/python-2.6.4.p9/src/Lib/test/ test_grp.py", line 32, in test_values e2 = grp.getgrgid(e.gr_gid) KeyError: 'getgrgid(): gid not found: -2' This is known problem that getgrgid() does not handle negative numbers. http://bugs.python.org/issue1465646 test_distutils passes if I use a plain python 2.6.5 tarball. This is consistent with the problem being in Sage or at least in the environment used for building packages. Adam -- 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: axiom.py
A ticket should probably be opened for both axiom.py and fricas.py (or one for each). The parsing of the output is very simplistic and buggy. I would guess that some simple code was done to get the interface started but has not been developed further. Adam -- 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: Ubuntu 10.4 LTS JMOL applet source is not properly provided
On Jun 13, 5:09 pm, Cedric Sodhi wrote: > Can at least someone confirm that it SHOULD run well in 10.4 LTS and Firefox? > It's a pretty big problem not to have any 3d plots at all! > Hi, I didn't want to just say "works for me" but I guess since you asked: I am running Ubuntu 10.04 x86_64, Firefox 3.6.3, Sage 4.4.3, openjdk/ icedtea 6. I have no problems with jmol either in the notebook or from the command line. I should mention that I compiled Sage from source. However, I also downloaded and ran the binary and it also worked. I am not sure if this helps you much. The only thing extra that I can think of is that I have installed ubuntu-restricted-extras which pulled in icedtea6-plugins and openoffice.org-base which pulled in some additional java stuff. Cheers, Adam -- 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.3.4 released
Hi, On a positive note. I was able to build Sage 4.3.4 and run long tests (all passed) on: 1. x86 - Scientific Linux 5.1 2. AMD64 - Ubuntu 10.4 (beta 1) Adam -- 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 unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
[sage-devel] Re: FriCAS in Sage
On Mar 21, 11:58 am, Ralf Hemmecke wrote: > Does somebody know whether (and how) I can convince Sage to work with an > existing FriCAS (compiled with sbcl) instead of compiling+installing the > fricas.spkg? > > Ralf Hi, Since the interface to fricas is pexpect I would not have expected any problems. I have not tried it with fricas but I have used a global install of axiom (compiled with gcl) without any errors. I only had to make sure that it was in my path for it to work. Adam -- 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 unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
[sage-devel] Re: proposal: standard command-line options in Sage
On Mar 19, 5:05 am, John H Palmieri wrote: > Sage uses non-standard command-line options (e.g., -notebook rather > than --notebook). I propose that we switch to standard ones. Here are > two reasons: > > 1. They're standard, and standards are good. People used to Unix-type > systems will expect our options to work this way. I think if we > decide to continue not using the standard format, we should have a > good reason. > > 2. If we use standard command-line options, we can use an existing > command-line parser, like Python's optparse, instead of having our own > home-grown version (in SAGE_ROOT/local/bin/sage-sage). A standard > Python library package is likely to be more robust than something home- > grown. For example, we can solve trac ticket #21 (and the related > ticket #180) this way. For another example, note that "sage -merge" > works but "sage --merge" doesn't; this sort of thing can be fixed on a > case-by-case basis, but it's harder to even introduce such > inconsistencies with optparse. > I think it is a great idea. > > - what is "sage -darcs" supposed to do? I don't know what "darcs" is, > and I don't see any packages which seem relevant. > I assume this refers to the distributed source code management. (http://darcs.net/) Perhaps someone was thinking of it as an alternative to mercurial. It does have an interesting theory of patches. > - what about "sage -axiom"? What package installs axiom? Fricas? > This is leftover from when fricas used to use the name axiom as a synonym. This is no longer the case. If axiom is installed globally it will be used. There is no spkg for it but there are optional tests that assume the presence of axiom. Adam > For any of these, we have several choices: (1) delete them, (2) keep > them, (3) keep them but don't document them (don't list them when you > type "sage --advanced"), (4) ?? > > -- > John -- 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 unsubscribe from this group, send email to sage-devel+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
[sage-devel] Re: proposal to remove dsage from sage
> If you care, please vote. > > [ ] Yes, I don't use DSage (don't even know what it is...), and > think it should be removed from Sage. > > [ ] No, I think DSage should stay as is. I love using DSage! > > [ ] Sort of -- delete Dsage for now, but if a maintainer/developer > comes along and fixes it so it actually works, then DSage gets back > into Sage for free. I vote: [x] Yes, I don't use DSage (don't even know what it is...), and think it should be removed from Sage. However, I admit that I have no idea of what it does. ;-) Adam -- 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: licenses for sage-enhanced books to be eventually included in Sage
> > I never really thought about this distinction--I wish there was > something like CC-by-sa-src as well. Source doesn't make as much sense > for a photo, but for something like a LaTeX document or a vector > graphic it is very valuable--almost an essential part of the "share > alike" idea. That's a strong argument for the GFDL. Even then, most > stuff doesn't fall into the 100+ pages category, and the GFDL is a lot > harder (for me) to be sure I understand (The CC, even the legalese > version, is much more readable.), and the GFDL requirements to contain > the full license is more draconian. Interesting question--now that > wikipedia is CC-by-sa, can I take the full text, make some > improvements, and satisfy the license by selling PDFs only? Would > certainly seem to violate the spirit of the license. > > BTW, I don't think there's any conflict issues with the GPL of any > code involved--they don't link to each other. > > - Robert Actually, there is a company that does just that! They take wikipedia articles and make books.[1] There was a discussion related to a new Lisp book [2]. They are selling books on Amazon. I love the one that is supposed to be about Georgia (Eastern Europe) that has a picture of Atlanta, Georgia, USA on the cover [3]. Quality. ;-) Cheers, Adam [1] http://www.alphascript-publishing.com/index.php?&act=nav&nav=10048 [2] http://groups.google.com/group/comp.lang.lisp/browse_thread/thread/784e2ad8f734fb8b/cda6809c45c123a7?#cda6809c45c123a7 [3] http://www.amazon.com/History-Georgia-country-Democratic-Tao-Klarjeti/dp/6130007442/ref=cm_cr-mr-title -- 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: multiple versions of optional packages
Just for information, here are some other multiple packages. I would guess that the newer versions of glpk and pexpect in experimental are tests. Others seem to be older versions that were left behind after promotion of the package. standard vs optional boehm_gc-7.1.p2 boehm_gc-7.1.p0 standard vs experimental gd-2.0.35.p2gd-2.0.34 libpng-1.2.35 libpng-1.2.24.p1 pexpect-2.0.p4 pexpect-2.1 optional vs experimental glpk-4.38.p4glpk-4.9 pyopenssl-0.8 pyopenssl-0.6 pyx-0.10pyx-0.8.1 Cheers, Adam -- 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
