On Aug 1 14:35, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote: > > I applied a patch which should fix this problem. It always uses > > WSARecvMsg now, if called from recvmsg, still provided it is possible, > > of course (No SOCK_STREAM, no AF_LOCAL). > > > > I'm just generating a new developer snapshot. Please give the today's > > snapshot from http://cygwin.com/snapshots/ a try. Should be up in > > about > > half an hour. > > The patched DLL now returns consistent msg_flags regardless of whether > or not the control message has been requested. Thanks! > > Could I ask for another favor that since the native WSA msg_flags get > propagated to the CYGWIN environment, the definitions for the additional > flag bits, MSG_MCAST and MSG_BCAST (as defined by WSA) to be added to > <cygwin/socket.h> please?
Done. These are Windows-specific values not docuemnted by POSIX. But Linux defines its own return values as well, so, never mind. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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
