X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=VCD/gTjYX8/r8teE
	Uo0LMVLgaXiKVFvLttg+kvRrsoDD/yanj4cbh0WToFhhZBD3nTWWwQ1LBekLwCzh
	sy/RpjElM1KfjqoYOmx4SORc1YDq8P5dI50SwRGBSrNr5YPiqgXPhjcXN7t82Akt
	492EvgfGw9kTwGTT1MHUx0WRjfA=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=PFCMIIhFfVieWLrSt7tLoC
	wVkTA=; b=OPPtFdAhUZdPRDEAi8LCN2UjiTAA8SsQMJdiq6ZgkNvMPPWLpyhxpj
	UD/ZRIT4YlxRr9+yteXj+XnSWX2VGNWmLS6zYAnndRXnjt05qLC0/PFFBjfayDMH
	2bWhPfAhj6TiaP6BICkTVqRIXkhZ1WdCmVjc2WCvRSJIi9a6VpahY=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Spam-SWARE-Status:	No, score=-1.9 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Spam-Relays-External:sk:mailsrv, H*RU:sk:mailsrv, HX-HELO:sk:mailsrv, H*r:sk:mailsrv
X-HELO:	mailsrv.cs.umass.edu
Reply-To:	moss AT cs DOT umass DOT edu
Subject:	Re: bug: cygwin-devel v3.0.2-1 socket.h does not #define MSG_EOR per the POSIX standard
To:	cygwin AT cygwin DOT com,
	"Brabant, Edward H CTR (USA)" <edward DOT brabant DOT ctr AT navy DOT mil>
References:	<0873126E9D101A4A983DE738F4346DBC9114A8F3 AT NAWESPSCXM03V DOT nadsuswe DOT nads DOT navy DOT mil> <20190424164358 DOT GG30041 AT calimero DOT vinschen DOT de>
From:	Eliot Moss <moss AT cs DOT umass DOT edu>
Message-ID:	<4e01e86d-83c9-5855-c4a5-29f5375dc2dc@cs.umass.edu>
Date:	Wed, 24 Apr 2019 13:54:51 -0400
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version:	1.0
In-Reply-To:	<20190424164358.GG30041@calimero.vinschen.de>
X-IsSubscribed:	yes

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

- Raw text -