Re: bug: cygwin-devel v3.0.2-1 socket.h does not #define MSG_EOR per the POSIX standard

2019-04-25 Thread Hans-Bernhard Bröker
Am 25.04.2019 um 17:48 schrieb Eric Blake: > On 4/25/19 10:28 AM, Brian Inglis wrote: >> Would it be allowed and valid to #define MSG_EOR 0 to simplify lack of >> support? > > No, because that implies that EVERY send() call is requesting MSG_EOR > and that it never fails. And maybe more import

Re: bug: cygwin-devel v3.0.2-1 socket.h does not #define MSG_EOR per the POSIX standard

2019-04-25 Thread Corinna Vinschen
On Apr 24 15:50, Eric Blake wrote: > On 4/24/19 3:36 PM, Hans-Bernhard Bröker wrote: > > Am 24.04.2019 um 19:54 schrieb Eliot Moss: > >> On 4/24/2019 12:43 PM, Corinna Vinschen wrote: > > > >>> Since MSG_EOR isn't implemented in the underlying transport layer, > >>> there's no way to implement it

Re: bug: cygwin-devel v3.0.2-1 socket.h does not #define MSG_EOR per the POSIX standard

2019-04-25 Thread Eric Blake
On 4/25/19 10:28 AM, Brian Inglis wrote: >> - add a define for MSG_EOR to a non-zero value that is bitwise distinct >> from other required MSG_ values >> - return EOPNOTSUPP on attempts to use the flag in >> send()/sendmsg()/sendto() (POSIX permits that failure for protocols that >> don't support

Re: bug: cygwin-devel v3.0.2-1 socket.h does not #define MSG_EOR per the POSIX standard

2019-04-25 Thread Brian Inglis
On 2019-04-24 14:50, Eric Blake wrote: > On 4/24/19 3:36 PM, Hans-Bernhard Bröker wrote: >> Am 24.04.2019 um 19:54 schrieb Eliot Moss: >>> On 4/24/2019 12:43 PM, Corinna Vinschen wrote: >> Since MSG_EOR isn't implemented in the underlying transport layer, there's no way to implement it in

Re: bug: cygwin-devel v3.0.2-1 socket.h does not #define MSG_EOR per the POSIX standard

2019-04-24 Thread Eric Blake
On 4/24/19 3:36 PM, Hans-Bernhard Bröker wrote: > Am 24.04.2019 um 19:54 schrieb Eliot Moss: >> On 4/24/2019 12:43 PM, Corinna Vinschen wrote: > >>> 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

Re: bug: cygwin-devel v3.0.2-1 socket.h does not #define MSG_EOR per the POSIX standard

2019-04-24 Thread Hans-Bernhard Bröker
Am 24.04.2019 um 19:54 schrieb Eliot Moss: > On 4/24/2019 12:43 PM, Corinna Vinschen wrote: >> 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 impleme

Re: bug: cygwin-devel v3.0.2-1 socket.h does not #define MSG_EOR per the POSIX standard

2019-04-24 Thread Eliot Moss
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, 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

Re: bug: cygwin-devel v3.0.2-1 socket.h does not #define MSG_EOR per the POSIX standard

2019-04-24 Thread Corinna Vinschen
On Apr 24 15:47, Brabant, Edward H CTR (USA) wrote: > 1. In cygwin-devel v3.0.2-1, 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 contains the following > e

bug: cygwin-devel v3.0.2-1 socket.h does not #define MSG_EOR per the POSIX standard

2019-04-24 Thread Brabant, Edward H CTR (USA)
1. In cygwin-devel v3.0.2-1, 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 contains the following excerpt regarding #define MSG_EOR: The header shall defin