Changes between Version 131 and Version 132 of CygwinPort

Timestamp:

12/02/11 21:59:45 (18 months ago)

Author:

dimpase

Comment:

--

CygwinPort

@@ -32 +32 @@
 === Rebasing ===
 At any point in the build process (or after), one can get  forking problems, related to the fact that Windows can relocate a dynamic library that just called fork() to another place in memory, causing fork() failure (this is a "feature" of the current Cygwin fork() implementation on Win32). To decrease the probability of this happening, you may need to rebase all the Cygwin and Sage DLLs you have so far, i.e. allocate each its own space address to load in (otherwise they compete for the space). 
- * 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. (But ignore the part about editing the list of Sage dlls, this is no longer necessary since #12096.)
- * 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`.
+ * See [https://groups.google.com/d/msg/sage-windows/ygK1kJm9p9w/XKyuJfiMlgYJ these build notes of William's] for a fairly effective strategy to deal with this. (But ignore the parts (4) and (5)  about editing the list of Sage dlls, this is no longer necessary since #12096.)
+ * In order to use this, you will need to run the 'ash' shell (or 'dash' shell) from the Windows command line.  
+   * This will require closing all Cygwin applications, and 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.
    * You may also have problems with permissions (getting a message about "is not writable").  [http://code.google.com/p/cyg-apt/issues/detail?id=8 This cyg-apt thread] seems to have several solutions for this.