Changes between Version 130 and Version 131 of CygwinPort


Ignore:
Timestamp:
12/03/11 05:48:51 (10 years ago)
Author:
dimpase
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CygwinPort

    v130 v131  
    2525   * not needed but very useful are ssh and scp
    2626   * similarly and nano or vim or something to edit files with
     27 * Make sure you uninstall the applications interfering with Cygwin, see [http://cygwin.com/faq/faq.using.html#faq.using.bloda BLODA] (Big List Of Dodgy Apps), including:
     28   * antivirus programs
     29   * antispyware programs
     30   * etc etc etc
    2731
    2832=== Rebasing ===
    29 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.
    30  * 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.
     33At 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).
     34 * 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.)
    3135 * In order to implement this, you may need to use the 'ash' shell from the Windows command line. 
    3236   * This may require doing `C:\cygwin\bin\ash.exe` or something similar instead of just `ash`.