public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com, "Brabant,
	Edward H CTR (USA)" <edward.brabant.ctr@navy.mil>
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 17:54:00 -0000	[thread overview]
Message-ID: <4e01e86d-83c9-5855-c4a5-29f5375dc2dc@cs.umass.edu> (raw)
In-Reply-To: <20190424164358.GG30041@calimero.vinschen.de>

On 4/24/2019 12:43 PM, Corinna Vinschen wrote:
> 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.

I don't have a direct interest in this issue, but I do have a wondering.
If Cygwin fails to define an error code -- even if the error cannot
actually happen under Cygwin -- isn't that a problem when trying to
compile imported software?  I wouldn't mind if the code were defined,
and a note included in comments that the error will not actually
occur under Cygwin ...

Is this a reasonable argument in support of including a define of the
error code?

Regards -- Eliot Mos

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

  reply	other threads:[~2019-04-24 17:54 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
2019-04-24 17:54   ` Eliot Moss [this message]
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=4e01e86d-83c9-5855-c4a5-29f5375dc2dc@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --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).