Re: IP_MULTICAST_IF et. all / Winsock[2] value conflict

2005-09-30 Thread Corinna Vinschen
On Sep 30 10:07, Brian Ford wrote: > On Fri, 30 Sep 2005, Corinna Vinschen wrote: > > 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 accordi

Re: IP_MULTICAST_IF et. all / Winsock[2] value conflict

2005-09-30 Thread Brian Ford
On Fri, 30 Sep 2005, Corinna Vinschen wrote: > 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 b

Re: IP_MULTICAST_IF et. all / Winsock[2] value conflict

2005-09-30 Thread Corinna Vinschen
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

Re: IP_MULTICAST_IF et. all / Winsock[2] value conflict

2005-09-29 Thread Brian Ford
On Thu, 29 Sep 2005, Corinna Vinschen wrote: > On Sep 29 11:27, Brian Ford wrote: > > I'm having a problem with IP_MULTICAST_IF not working on Cygwin. While > > investigating, I came across this MS KB article that might describe my > > problem: > > > > http://support.microsoft.com/default.aspx?sc

Re: IP_MULTICAST_IF et. all / Winsock[2] value conflict

2005-09-29 Thread Corinna Vinschen
On Sep 29 11:27, Brian Ford wrote: > I'm having a problem with IP_MULTICAST_IF not working on Cygwin. While > investigating, I came across this MS KB article that might describe my > problem: > > http://support.microsoft.com/default.aspx?scid=kb;en-us;257460 > > IP_MULTICAST_IF can have two valu