Changes between Version 101 and Version 102 of CygwinPort

Timestamp:

06/30/11 06:59:44 (23 months ago)

Author:

kcrisman

Comment:

--

CygwinPort

@@ -5 +5 @@
  * Although below it compares Windows 7 and Windows XP, it is conceivable that the Cygwin version also sometimes has something to do with the problems listed
 
-== Cygwin Prerequisites ==
+== Cygwin Notes ==
 
+=== Prerequisites ===
 These Cygwin packages need to be installed in order for the Sage build to complete.  Eventually, these should be added to prereq, but that would be for when Cygwin is actually supported.
 
@@ -21 +22 @@
    * similarly and nano or vim or something to edit files with
 
-At any point in the build process (or after), changes in Windows (such as antivirus upgrades) can lead to forking problems, and you may need to rebase.  See [http://groups.google.com/group/sage-windows/browse_thread/thread/ca02b59099bda7dc these build notes of William's] for a fairly effective strategy to deal with this.
+=== Rebasing ===
+At any point in the build process (or after), changes in Windows (such as antivirus upgrades) can lead to forking problems, and you may need to rebase.  
+ * See [http://groups.google.com/group/sage-windows/browse_thread/thread/ca02b59099bda7dc these build notes of William's] for a fairly effective strategy to deal with this.
+ * In order to implement this, you may need to use the 'ash' shell from the Windows command line.  
+   * This may require doing `C:\cygwin\bin\ash.exe` or something similar instead of just `ash`.
+   * For ash to actually find any commands, you may need to follow the tips at [http://thehacklist.blogspot.com/2009/04/cygwin-ls-command-not-found.html this blog post] for setting the `CYGWIN_HOME` variable and prepending the Cygwin binary directory (usually `C:\cygwin\bin`) to the `Path` variable.
 
+=== Porting! ===
 Also, don't forget to {{{export SAGE_PORT=yes}}} before starting.