From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Dionna Amalie Glaze <dionnaglaze@google.com>, newlib@sourceware.org
Subject: Re: Shouldn't <sys/uio.h> be available everywhere?
Date: Thu, 13 Jul 2017 07:05:00 -0000 [thread overview]
Message-ID: <fef54be7-91eb-ce1d-894e-2b5daaffce76@embedded-brains.de> (raw)
In-Reply-To: <CAAH4kHYA7H+gAaDgVRgEmSruTNRdF5HuO4suBqC5bk3D3ZMvLQ@mail.gmail.com>
On 12/07/17 21:42, Dionna Amalie Glaze via newlib wrote:
> I'm looking at the POSIX standard for readv and writev, and it looks
> like there should be definitions for each of these given
> __POSIX_VISIBLE >= 200112, not just being on a PowerPC platform with
> an SPU. There should additionally be a definition of IOV_MAX in
> <limits.h>.
> Shall I go ahead and create a patch, or am I in error?
>
There are some uio.h in Newlib/Cygwin:
./winsup/cygwin/include/sys/uio.h
./newlib/libc/machine/spu/sys/uio.h
./newlib/libc/sys/rtems/include/sys/uio.h
./newlib/libc/sys/phoenix/sys/uio.h
It would be nice to unify this and move it to
./newlib/libc/include/sys/uio.h
For the #ifdef _KERNEL part (and similar) we can use something like this:
#ifdef _KERNEL
/* Header file provided outside of Newlib */
#include <machine/_kernel_uio.h>
#endif
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.huber@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
prev parent reply other threads:[~2017-07-13 7:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 19:42 Dionna Amalie Glaze via newlib
2017-07-13 7:05 ` Sebastian Huber [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fef54be7-91eb-ce1d-894e-2b5daaffce76@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=dionnaglaze@google.com \
--cc=newlib@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).