Don't know where to send this type of thing, so I'll put it here and hope the right person sees it.
(Using cygwin32 on windows 8.1. Using 32 bit instead of 64 bit because I need Macaulay2, which only seems to be available for 32 bit.)
Building went fine up until numpy, which failed because the "cygwin-lapack_lite-setup.py.diff" patch seems to be made for an older version of numpy than the one included. Using a modified .diff based on the new version seemed to fix everything.
Then ipython failed with error
1 [main] python2.7 516 child_info_fork::abort: address space needed by 'array.dll' (0x2C0000) is already occupied error: [Errno 11]
Resource temporarily unavailable
Sounded like the type of thing rebasing would fix, but retrying after running sage-rebaseall.sh didn't solve it after about 5 attempts. Anyone have any ideas? (I'm a linux noob, so please treat me as such)
The Cygwin64Port page seems to suggest I might have better luck with 5.13, so I'm trying that as I speak.
EDIT: 5.13 failed with a similar error, this time while installing mercurial. Again rebasing doesn't fix it.
I believe I'm doing rebasing right. I quit cygwin then run "dash -c '/usr/bin/rebaseall" from a command prompt with admin privileges.
Just found the precompiled cygwin binaries at http://boxen.math.washington.edu/home/jpflori/dist/ , I grabbed the one for 5.13 and ran it. During startup it sometimes gives a fork error
1 [main] python2.7 4968 child_info_fork::abort: address space needed by 'utils.dll' (0x510000) is already occupied
but that doesn't seem to ruin things, and it still takes me to the prompt. I can calculate 3*3 (correctly) and I can open the notebook in Firefox, so that's good.
I'm running make test now to see how that goes. Will update.
EDIT 2: The test died with a fork error, the occasional fork error on sage startup somehow became constant, rebasing did nothing as always, usual, and the notebook stopped working (page loaded blank, fork and python errors in the terminal). Deleted everything and re-extracted, and the notebook works again, but still with intermittent fork errors.
Assuming it maintains its current level of not-completely-brokenness, I'll probably keep it but go back to the VM when I need something more stable.
It would be amazing if this could somehow be the/an officially supported way to use sage on windows, though. Virtual machines are so big and clunky.
