On Tuesday, 18 June 2013 15:33:33 UTC+2, Volker Braun wrote: > > This is 32-bit Windows 7 with 4GB ram. > > On Tuesday, June 18, 2013 1:43:37 AM UTC-7, Dima Pasechnik wrote: >> >> what is the Windows version you are using? Is it a 32-bit? I've had a lot >> of trouble with this one, and much less with a 64-bit (I'm not talking >> about about 32 vs 64-bit Cygwin). >> It probably has to do with the amount of space one has to allocate for >> all the dlls. >> > > Possibly, the 64-bit OS will provide a fake 32-bit addressing space to > cygwin which ought to be more contiguous since there is no need to map much > of the OS stuff into it. > > Maybe everybody who tried can chime in and say which windows version and > bitwidth they used, and how good or bad their cygwin experience was. In my > case it was pretty much unusable, for example I haven't managed to get a > complete make ptestlong run without dying in forks. > > I found a 32-bit Windows 7 on a VMWare pretty much impossible to deal with, due to forking issues. (I even tried cutting down on the number of Cygwin packages insatlled) A 64-bit Windows 7 on a VMWare is, on the other hand, reasonably OK, full build of Sage 5.9, including docs, went quite OK.
One might look at the Cygwin's Python, they hacked it quite a bit. Maybe getting these patches into Sage's Python on Cygwin might improve things. A last resort is to "go Apache" and implement a custom module loader :) Dima -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
