Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 30 Sep 2005 10:17:01 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: IP_MULTICAST_IF et. all / Winsock[2] value conflict
Message-ID: <20050930081701.GB27423@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <Pine DOT CYG DOT 4 DOT 58 DOT 0509291103421 DOT 2244 AT PC1163-8460-XP DOT flightsafety DOT com> <20050929165053 DOT GU12256 AT calimero DOT vinschen DOT de> <Pine DOT CYG DOT 4 DOT 58 DOT 0509291152490 DOT 2244 AT PC1163-8460-XP DOT flightsafety DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.CYG.4.58.0509291152490.2244@PC1163-8460-XP.flightsafety.com>
User-Agent: Mutt/1.4.2i

On Sep 29 12:04, Brian Ford wrote:
> On Thu, 29 Sep 2005, Corinna Vinschen wrote:
> > There's no easy fix right now.  We have to drop all traces of Winsock1
> > in Cygwin and change the headers accordingly.
> 
> Can't we just translate these based on a flag indicating what version we
> dynamically loaded?

Yes, in theory we can.  But that's hell.  The definitions in socket.h
wouldn't be static values anymore, they would have to be translated
into function calls to retrieve the right value at runtime.  That's
bound to break building applications which rely on getting constant
values.

Really, dropping Winsock1 entirely is the way to go.  Winsock2 is
available since Win98 and even for Win95, there's a Winsock2 available
for free on some Microsoft web page (should be in the Cygwin mailing
list archives somewhere).

So that's the next step to do in the networking code and, Brian,
while we're at it, some team work wouldn't hurt here.  I recall
that you have a copyright assignment in place.
http://cygwin.com/acronyms/#PTC
http://cygwin.com/acronyms/#SHTDI


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/