From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 34605 invoked by alias); 24 Apr 2019 17:54:56 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 34591 invoked by uid 89); 24 Apr 2019 17:54:56 -0000 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 Received: from mailsrv.cs.umass.edu (HELO mailsrv.cs.umass.edu) (128.119.240.136) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 24 Apr 2019 17:54:54 +0000 Received: from [192.168.24.72] (eduroamgw.cs.umass.edu [128.119.40.194]) by mailsrv.cs.umass.edu (Postfix) with ESMTPSA id 619B74023BAA; Wed, 24 Apr 2019 13:54:52 -0400 (EDT) Reply-To: moss@cs.umass.edu Subject: Re: bug: cygwin-devel v3.0.2-1 socket.h does not #define MSG_EOR per the POSIX standard To: cygwin@cygwin.com, "Brabant, Edward H CTR (USA)" References: <0873126E9D101A4A983DE738F4346DBC9114A8F3@NAWESPSCXM03V.nadsuswe.nads.navy.mil> <20190424164358.GG30041@calimero.vinschen.de> From: Eliot Moss Message-ID: <4e01e86d-83c9-5855-c4a5-29f5375dc2dc@cs.umass.edu> Date: Wed, 24 Apr 2019 17:54:00 -0000 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> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-04/txt/msg00170.txt.bz2 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 man page for contains the following >> excerpt regarding #define MSG_EOR: >> >> The 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