Changes between Version 104 and Version 105 of CygwinPort


Ignore:
Timestamp:
07/01/11 16:33:02 (11 years ago)
Author:
kcrisman
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CygwinPort

    v104 v105  
    3636 
    3737=== Win 7 only ===
    38  * #11245: on Win7 tar does not unpack cddlib and networkx spkg's right. See the ticket for a workaround.
     38 * #11245: on Win7 tar does not unpack cddlib and networkx spkg's right.
    3939 * #11550: Singular does not build (see also the older #10235, which may or may not still be valid)
    4040 * Issue with Python 2.6.4 building.  Relevant comments:
    41    * Comment 0 - Original report, from March 2010, at [http://groups.google.com/group/sage-windows/browse_thread/thread/88499b995a22ecc1]
     41   * Comment 0 - Original report, from March 2010, at [http://groups.google.com/group/sage-windows/browse_thread/thread/88499b995a22ecc1] - but note the fix should be `__CYGWIN__`, not `CYGWIN`
    4242   * Comment 1 - I had no problems with that thus far in Vista Premium 32-bit - Alec Mihailovs
    4343   * Comment 2 - Alec - Win7 has a newer codebase, so this is not really a proof that we need not worry --- I think we really need to. Dmitrii
    4444   * Comment 3 (from somebody) "obsolete, as Cygwin now has Python 2.6.5 as the standard" - true, but apparently still a problem for us
    4545   * Comment 4 - Python spkg builds fine on XP - kcrisman
    46    * Comment 5 - Tried this fix on Win7 after it failed on the first extension, but it failed in the next extension after that.  Rebasing everything in $SAGE_ROOT seemed to fix that, however, so this remains an open issue.
     46   * Comment 5 - Rebasing everything in $SAGE_ROOT seemed to fix it on Windows 7.
    4747   * Comment 6 - Sometimes sage-gdb does not work.  install.log reports that Python failed to find necessary bits to build
    4848     * `_bsddb` and `bsddb185`