Minh Nguyen wrote: > Hi folks, > > This is the first release of the Sage 4.1.1 release cycle. William and > I are co-chairing this release cycle. The source tarball and the > sage.math only binary are available at > > http://sage.math.washington.edu/home/mvngu/release/sage-4.1.1.alpha0.tar > http://sage.math.washington.edu/home/mvngu/release/sage-4.1.1.alpha0-sage.math.washington.edu-x86_64-Linux.tar.gz > > You can also upgrade using this path: > > http://sage.math.washington.edu/home/mvngu/release/sage-4.1.1.alpha0/ > > The lowest ticket number winner is #111, which was closed due to the > work of Alex Ghitza and David Loeffler. > > This alpha 0 release includes 5 tickets relating to new SPKG's: > > #6380 [ntl-5.4.2.p9.spkg] > #6443 [zn_poly-0.9.p1.spkg] > #6445 [pari-2.3.3.p1.spkg] > #6451 [flint-1.3.0.p2.spkg] > #6493 [numpy-1.3.0.p1.spkg] > > All of these tickets, except for #6493, deal with building the > corresponding SPKG's on Solaris on the machine t2. This Solaris build > support is due to the remarkable work of David Kirkby. If you want to > help out with building SPKG's on Solaris/t2, the following tickets > need review: > > #6453 > #6558
#6558 "Be more selective in patching ATLAS on Solaris" http://sagetrac.org/sage_trac/ticket/6558 should be very easy to review, as the change is very small. #6453 "MPFR test failures on Solaris 10 update 4 on host 't2'" http://sagetrac.org/sage_trac/ticket/6453 Is somewhat more complex to review. It basically applies a very simple patch, in a flexible way - whether the patch is applied or not depends on the type of Solaris machine and if the user has set an environment variable to over-ride the default behavior. Ticket #6563 "Singular fails to install header files, since it fails to find install-sh" http://sagetrac.org/sage_trac/ticket/6563 Is an easy one to review, but perhaps a bit controversial. It applies a quick fix (add a copy of install-sh) to the 15 or so copies of the same name in the singular distribution. It however add that copy in the top level directory (where spkg-install exists). It can not possibly break anything else, and it allows singular to build. There are undoubtedly other ways to get around this problem, but none are quite as simple. The real solution is to fix a bug in autoconf or fix the singular build systems - whatever one happens to be at fault. I'm personally a bit reluctant to spend much time on finding a better solution, when there are other parts of Sage which have more serious problems on Solaris. Dave --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
