[FFmpeg-devel] [PATCH] Fix connect return EWOULDBLOCK not EINPROGRESS under mingw

Michael Niedermayer michaelni
Fri Jun 29 03:04:29 CEST 2007


On Fri, Jun 29, 2007 at 01:21:34AM +0200, Alex Beregszaszi wrote:
> Hi,
> > > A connect in windows doesn't return EINPROGRESS as is customary for a non
> > > blocking socket, it returns EWOULDBLOCK. By redefining WSAEWOULDBLOCK to
> > > WSAEINPROGRESS tcp.c works just fine. 
> > > 
> > > EINPROGRESS in windows has some very odd meaning, and wouldn't make sense to
> > > check for anyway, so think this patch is fine.
> > 
> > do we have a win32 maintainer?
> > if there are any volunteers, id be very happy to loose the implicit
> > ffmpeg-win32 maintainer role
> We have an other fix for this in the tree.
> And how many times do we need to discuss this win32 maintainership?

there are exactly 3 threads (including your 
"We have an other fix for this in the tree" from above) with mingw and
[PATCH] in the subject to which you replied ever
there are none with cygwin in the subject
search for mingw and [PATCH] there are many pages

that is NOT maintaining windows support nor mingw support

and even if you would maintain it you just maintain mingw, we either way
still need a maintainer for cygwin


Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Concerning the gods, I have no means of knowing whether they exist or not
or of what sort they may be, because of the obscurity of the subject, and
the brevity of human life -- Protagoras
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20070629/29342e16/attachment.pgp>

More information about the ffmpeg-devel mailing list