On 25 August 2014 16:28, Dima Pasechnik <[email protected]> wrote: > > apparently it's better, but it's only supported on certain more > expensive versions of Windows 7 and Windows Server 2008. > > to quote: > > Supported Operating Systems: Windows Server 2008 R2; Windows 7 Enterprise; > Windows 7 Enterprise 64-bit edition; Windows 7 Ultimate; Windows 7 Ultimate > 64-bit edition;
Ah bummer... I wonder if the version check is strict or if it can be worked around somehow. Seems like at some point Debian had an Interix port: http://www.debian-interix.net/ (As a side question, what versions of Windows are commonly found on desktops/laptops these days? Are people switching over to Windows 8?) There's quite a bit of material on how to write a replacement of fork() using the Windows API. See, e.g., http://stackoverflow.com/questions/985281/what-is-the-closest-thing-windows-has-to-fork/985525#985525 http://doxygen.scilab.org/5.3/d0/d8f/forkWindows_8c_source.html#l00216 And it seems MinGW has the prototype for fork(), although not the implementation: http://stackoverflow.com/questions/9612315/why-does-my-compiler-not-accept-fork-despite-my-inclusion-of-unistd-h Even if the implementation is not 100% conforming, it would probably be adequate for some purposes. Is the lack of fork() the biggest showstopper or just one of many roadblocks? I would imagine a lot of external components included in sage are not written with platform independence in mind (but IMO this would rather be an argument to work with upstream to rectify the issue instead of working around it). -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
