[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d511bd05-6c2e-7d30-f5a1-981ef8122205@mirbsd.de>
Date: Fri, 12 Jun 2026 00:44:35 +0200 (CEST)
From: Thorsten Glaser <tg@...bsd.de>
To: musl@...ts.openwall.com
Subject: Re: Why do sendmmsg and recvmmsg take unsigned int flags?
On Fri, 12 Jun 2026, Alyssa Ross wrote:
>A little bit more research: it's int on OpenBSD, bionic and uClibc-ng as
>well, but unsigned int on NetBSD. macOS has a different interface
>entirely.
Hmm.
TFM says it takes the same flags as sendmsg(2).
Is that unsigned on NetBSD? What does Mac OSX have for sendmsg?
POSIX has:
ssize_t sendmsg(int socket, const struct msghdr *message, int flags);
So it probably should be int everywhere (IMHO, not a musl dev).
bye,
//mirabilos
--
“It is inappropriate to require that a time represented as
seconds since the Epoch precisely represent the number of
seconds between the referenced time and the Epoch.”
-- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
