Mike, I recall reporting some weirdness on Windows 7, originating from the randomized addressing issue. (that's what rebase and rebaseall Cygwin utilities are/were fighting). At that time Cygwin still had Python 2.5.
Is it correct that since then it has fixed itself, as Cygwin folks found a way to fix these problems? Dima On Apr 16, 12:20 pm, Mike Hansen <mhan...@gmail.com> wrote: > Hello, > > Sorry about the delay in response. > > On Thu, Apr 14, 2011 at 11:29 AM, Alexandre Blondin Massé > > <alexandre.blondin.ma...@gmail.com> wrote: > > 1. What remains to be done? > > All of the current known build issues are listed > athttp://trac.sagemath.org/sage_trac/wiki/CygwinPortunder the "Build > Tickets" section. They all currently have fixes, but some work needs > to be done in updating spkgs for some of them. With those fixes, I > got all the spkgs in Sage 4.7.alpha3 to build on Cygwin. > > Currently Sage 4.7.alpha3 does not start up due to a segfault caused > by either the new PARI added in 4.6 or the new interrupt handling > code. I have a clean backtrace for this, but I haven't delved into it > yet. > > There are some tickets on there for doctest failures that need to be > looked into, but a number of them are trivial. > > > 2. Who is working actively/partially actively on the project? > > I think I am the only one who is spending some time on it every now and then. > > > 3. What human ressource is needed? What profile should people working > > on it have? > > It seems like most the issues left are with C code so someone who is > very familiar building Unix C code would be best. > > --Mike -- 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
