[Python-Dev] Re: Q: Testing Python 2.1.2 on cygwin

[Jason Tishler]

Anthony,

The problems with fork() and _curses that you reported are already known.
In fact, the _curses build problem is already solved.  Please read
the Python README or the latest Cygwin Python 2.2 README which is
available at:

    http://www.tishler.net/jason/software/python/python-2.2.README.txt

On Fri, Jan 11, 2002 at 09:32:19PM -0500, Tim Peters wrote:
> [Anthony Baxter]
> > Paul Everitt tested on cygwin, and make test got:
> 
> There's a long section about known Cygwin problems in the main README file,
> mostly written by Cygwin developers.  Make sure Paul followed the special
> Cygwin build instructions before worrying too much;

The fork() problem can be worked around by building the _socket module
statically:

    http://sources.redhat.com/ml/cygwin/2001-12/msg00542.html

> the failure of curses to build won't go away regardless (see README).

This problem has been solved in the latest Cygwin ncurses release:

    http://sources.redhat.com/ml/cygwin/2002-01/msg00473.html
    http://sources.redhat.com/ml/cygwin/2002-01/msg00529.html

Note that you will have to explicitly ask Cygwin's setup.exe to install
this ncurses version because it is still marked as test.

FYI, a pre-built Python 2.2 is part of the standard Cygwin distribution:

    http://cygwin.com/ml/cygwin-announce/2002/msg00001.html

BTW, if you are trying to build other Python versions (e.g., 2.1.2), you
may find the Cygwin specific patch (i.e., CYGWIN-PATCHES/python.patch)
in the Python source tarballs on the Cygwin mirrors useful to review.

Jason