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:	<39DC4BE8.2C087502@cygnus.com>
Date:	Thu, 05 Oct 2000 11:37:44 +0200
From:	Corinna Vinschen <vinschen AT cygnus DOT com>
X-Mailer:	Mozilla 4.75 [en] (X11; U; Linux 2.2.14-SMP i686)
X-Accept-Language:	de, en
MIME-Version:	1.0
To:	"Laurence F. Wood" <LaurenceWood AT sunyatasystems DOT com>
CC:	cygwin AT sources DOT redhat DOT com
Subject:	Re: compiling python under cygwin
References:	<FPECIFPIDJMHKKOODOHICEKCCAAA DOT LaurenceWood AT sunyatasystems DOT com>

"Laurence F. Wood" wrote:
> 
> I have had problems porting a large system because of the winsock.h include.
> For one thing, I was having a problem with WIN32/_WIN32 being suddenly
> defined (by something that winsock.h includes) in conditional code.  It took
> me a while to track down what was going on.

Yup, the WIN32 define sometimes results in, erm, *interesting* problems
while porting.

However, the winsock include in tcp.h is fixed in the winsup cvs.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                        mailto:cygwin AT sources DOT redhat DOT com
Red Hat, Inc.
mailto:vinschen AT cygnus DOT com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -