Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<80575AFA5F0DD31197CE00805F650D7602CD94@wilber.adroit.com>
From:	"Robinow, David" <drobinow AT dayton DOT adroit DOT com>
To:	"'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
Subject:	netinet/tcp.h
Date:	Fri, 1 Sep 2000 13:44:20 -0400
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2650.21)

------_=_NextPart_001_01C0143C.47724310
Content-Type: text/plain;
	charset="iso-8859-1"

 I've just compiled the lastest Python beta 1.6b1 under Cygwin 1.1.4
It builds out of the box except for 2 things:
 1) the ".exe" suffix problem which has existed for a while and requires
    patching two files. (Partial support for solving this exists and I've
    submitted a patch for finishing this up.)

 2) Modules/socketmodule.c  has a statement
    #include <netinet/tcp.h>

    This file does not exist in Cygwin.  However, if I do:
       touch /usr/include/netinet/tcp.h

    The build completes and the test_socket test completes successfully.
    (A few other tests fail. I'm still investigating those.)
    Apparently whatever "normal" unix systems tend to put in
    netinet/tcp.h is handled elsewhere in Cygwin.

    My question is:
      Would it be reasonable for Cygwin to include an empty copy of this
    file so that packages that assume it is necessary can compile
succesfully?


David Robinow
 

------_=_NextPart_001_01C0143C.47724310--

- Raw text -