public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel@rtems.org>
To: newlib@sourceware.org, Jeff Johnston <jjohnstn@redhat.com>
Subject: Re: Adding aio.h and mqueue.h
Date: Fri, 2 Dec 2022 08:15:00 -0600	[thread overview]
Message-ID: <CAF9ehCWLgfDidX_LmNz9AW352WaGiGPMBwcA3XVuRdX28aQZLA@mail.gmail.com> (raw)
In-Reply-To: <Y4nOPsQJ0FAFKuuQ@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 1481 bytes --]

On Fri, Dec 2, 2022 at 4:07 AM Corinna Vinschen <vinschen@redhat.com> wrote:

> On Dec  1 18:22, Jeff Johnston wrote:
> > As long as the licensing is shared-newlib-compatible (non-GPL), it should
> > be ok.
> >
> > -- Jeff J.
>
> Cygwin already comes with aio.h and mqueue.h headers.
>
> Ideally they are reused for newlib, or the new aio.h/mqueue.h headers
> are checked that they provide the same definitions and replace the
> Cygwin-only ones.
>

OK. So the same defines with the same values? Anything cygwin specific
goes into an ifdef, etc. I vaguely recall doing this before for other
header files.

RTEMS is always built from source so changing the values isn't a huge
binary compatibility issue. But moving the header file from RTEMS to
newlib will require everyone using the git master to build new tools.
So there is a bit of coordination on our side.

--joel

>
>
> Thanks,
> Corinna
>
>
>
>
>
> >
> > On Thu, Dec 1, 2022 at 11:37 AM Joel Sherrill <joel@rtems.org> wrote:
> >
> > > Hi
> > >
> > > We have migrated almost all of our POSIX defined header files from
> RTEMS
> > > itself to newlib.  I think aio.h and mqueue.h are the last POSIX
> headers
> > > left on our side.
> > >
> > > What's the feeling on merging these? Would it be ok to put them in
> > > newlib/libc/include?
> > >
> > > Our version of the headers have Doxygen comments. Would these be OK in
> > > newlib or do I need to remove the Doxygen?
> > >
> > > Thanks.
> > >
> > > --joel
> > >
> > >
>
>

  reply	other threads:[~2022-12-02 14:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01 16:37 Joel Sherrill
2022-12-01 23:22 ` Jeff Johnston
2022-12-02 10:06   ` Corinna Vinschen
2022-12-02 14:15     ` Joel Sherrill [this message]
2022-12-02 17:10       ` Corinna Vinschen
2022-12-02 17:19         ` Joel Sherrill
2022-12-04 18:59           ` Corinna Vinschen

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=CAF9ehCWLgfDidX_LmNz9AW352WaGiGPMBwcA3XVuRdX28aQZLA@mail.gmail.com \
    --to=joel@rtems.org \
    --cc=jjohnstn@redhat.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).