I had success compiling all of Sage (except maybe some strange gdb segfault at the end of the doc building process) on real and virtual 32 bit Windows.
I may have been just lucky, but I'll give it another shot for 5.10 and if I succeed you can just give a shot to the bdist I'll produce. I don't think we should reinvent Cygwin here. On Tuesday, June 18, 2013 9:59:00 PM UTC+2, Dima Pasechnik wrote: > > On 2013-06-18, Volker Braun <vbrau...@gmail.com <javascript:>> wrote: > > ------=_Part_3815_15192245.1371584473247 > > Content-Type: text/plain; charset=ISO-8859-1 > > > > If there were a way to avoid the memory addressing conflicts with fork > then > > it would be implemented in Cygwin. A quick web search shows many people > > having trouble with Apache on Cygwin, e.g. > sure, Apache on Cygwin is a trouble. But Apache runs on > Windows without Cygwin, yet is has its dynamic modules just fine. > > Cygwin cannot follow this path, as they want to be able to create real > Windows dlls, not something that needs a custom loader. > > > > > > > http://superuser.com/questions/597293/apache-package-in-cygwin-does-not-seem-to-work-error-logs-are-also-empty > > > > > > > On Tuesday, June 18, 2013 12:24:12 PM UTC-7, Dima Pasechnik wrote: > >> > >> Apache has its own implementation of loading of dynamic modules. So > they > >> don't have to rely on the mercy of Windows... > >> > >> > > > > -- 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.
