On Sep 25, 4:50 pm, Minh Nguyen <nguyenmi...@gmail.com> wrote:
> Hi folks,
>
> There are some updated packages that would be really cool to get into
> Sage 4.1.2. These include:
>
> * #6969 boehm_gc-7.1.p2.spkg
> * #6971 ecl-9.8.4-20090913cvs.p1.spkg
> * #7006 mpir-1.2.p6.spkg
> * #6919 flint-1.5.0.p0.spkg
> * #6990 python-2.6.2.p2.spkg
> * #6951 singular-3-1-0-4-20090818.p0.spkg
> * #6758 libgcrypt-1.4.3.p2.spkg
> * #6681 cliquer-1.2.p0.spkg
In an attempt to save time, I attempted to build using all of these at
once (instead of doing one at a time), along with the new fortran spkg
(#6981) and the new r spkg (#6972). On OS X 10.5, both 32-bit and 64-
bit, building was successful. After applying the appropriate patches
-- the ones from 6883, 6919, 6972 -- 64-bit: all tests passed. After
applying these patches to the 32-bit build, same failures as Minh
reported in another thread ("Sage 4.1.2.alpha2 doctest failures on OS
X 10.5.8").
In other words, the packages seem to all look good. I have not
examined each one to see if the spkg-install files make sense, for
instance, but from the point of view of building and (apparently)
functioning on OS X 10.5, they work.
I don't have the energy to comment on each ticket individually, so
take this as my portion of a positive review for each ticket: on Mac
OS X 10.5, they build properly and seem to work.
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
-~----------~----~----~----~------~----~------~--~---
