From: Corinna Vinschen <cygwin@cygwin.com>
To: cygwin <cygwin@cygwin.com>
Subject: Re: 1.3.2: Cygwin && UDP && O_NONBLOCK
Date: Thu, 16 Aug 2001 05:59:00 -0000 [thread overview]
Message-ID: <20010816145913.Q17709@cygbert.vinschen.de> (raw)
In-Reply-To: <030401c1264e$3ae5d550$93b849d5@uu.net>
On Thu, Aug 16, 2001 at 02:23:14PM +0200, Roderick Groesbeek wrote:
> From: "Corinna Vinschen" <cygwin@cygwin.com>
> To: <cygwin@cygwin.com>
> Sent: Wednesday, August 15, 2001 9:50 AM
> Subject: Re: 1.3.2: Cygwin && UDP && O_NONBLOCK
>
>
> Hello Corinna,
>
>
> > On Tue, Aug 14, 2001 at 01:54:27PM -0600, Troy Noble wrote:
> > > Roderick,
> > >
> > > Unless I misunderstood entirely, I think you've found a bug.
> >
> > Thanks for tracking that down. I changed the code to use your
> > version 1 (fallback to winsock1) in case of nonblocking sockets.
>
> What is the correct way for me to obtain the new Cygwin DLL with
> correct O_NONBLOCK behaviour?
>
> - Should I compile from source after an CVS update?
That makes sense. You'll get the most fresh developer stuff
including all new errors ;-)
> - Should I take a snapshot?
That's also ok. It's your choice.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin@cygwin.com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2001-08-16 5:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-14 12:54 Troy Noble
2001-08-14 13:17 ` Keith Seitz
2001-08-15 0:50 ` Corinna Vinschen
2001-08-16 5:18 ` Roderick Groesbeek
2001-08-16 5:59 ` Corinna Vinschen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-14 8:12 Roderick Groesbeek
2001-08-14 9:34 ` Keith Seitz
2001-08-14 13:09 ` Roderick Groesbeek
2001-08-14 13:23 ` Keith Seitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010816145913.Q17709@cygbert.vinschen.de \
--to=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).