public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: "Brabant, Edward H CTR (USA)" <edward.brabant.ctr@navy.mil>
Cc: cygwin@cygwin.com
Subject: Re: bug:  cygwin-devel v3.0.2-1 socket.h does not #define MSG_EOR per the POSIX standard
Date: Wed, 24 Apr 2019 16:44:00 -0000	[thread overview]
Message-ID: <20190424164358.GG30041@calimero.vinschen.de> (raw)
In-Reply-To: <0873126E9D101A4A983DE738F4346DBC9114A8F3@NAWESPSCXM03V.nadsuswe.nads.navy.mil>

[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]

On Apr 24 15:47, Brabant, Edward H CTR (USA) wrote:
> 1. In cygwin-devel v3.0.2-1, <cygwin/socket.h> does not #define
> MSG_EOR.  In bash, with CWD=/usr/include, the command "find . -name
> '*.h' -exec grep -Hn MSG_EOR {} \;" does not find any matches.
> 
> 2. The Open Group man page for <sys/socket.h> contains the following
> excerpt regarding #define MSG_EOR:
> 
>      The <sys/socket.h> header shall define the following symbolic
>      constants with distinct values for use as the valid values for
>      the msg_flags field in the msghdr structure, or the flags
>      parameter in recv(), recvfrom(), recvmsg(), send(), sendmsg(), or
>      sendto() calls:
> ...
> MSG_EOR
> Terminates a record (if supported by the protocol).
> ...

MSG_EOR is not supported by underlying WinSock.  There's a similar
MSG_PARTIAL, but it's defined differently.  It's also unsupported by
all of the predefined protocols, including UDP.

Since MSG_EOR isn't implemented in the underlying transport layer,
there's no way to implement it in userspace.  That's why it's not
defined in Cygwin's headers.  If you have an idea how to implement
this in plain userspace, feel free to provide patches.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-04-24 16:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24 15:48 Brabant, Edward H CTR (USA)
2019-04-24 16:44 ` Corinna Vinschen [this message]
2019-04-24 17:54   ` Eliot Moss
2019-04-24 20:36     ` Hans-Bernhard Bröker
2019-04-24 20:50       ` Eric Blake
2019-04-25 15:28         ` Brian Inglis
2019-04-25 15:48           ` Eric Blake
2019-04-25 18:36             ` Hans-Bernhard Bröker
2019-04-25 17:08         ` Corinna Vinschen

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=20190424164358.GG30041@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    --cc=edward.brabant.ctr@navy.mil \
    /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).