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

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

On Fri, Dec 2, 2022, 11:10 AM Corinna Vinschen <vinschen@redhat.com> wrote:

> On Dec  2 08:15, Joel Sherrill wrote:
> > 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.
>
> There shouldn't be much Cygwin-specifc in these files and they are quite
> short.  Please check the Cygwin files against the files from RTEMS.
> Maybe it makes sense to use them instead and just add the (minor)
> differences to Cygwin.  If the types used have the same size and the
> same signedness, there shouldn't be much of a problem anyway.
>
> However, I'd like to defer this by a few days or weeks.  We're just
> in the beta phase for Cygwin 3.4, and I would rather have stable
> headers for now :
>

We are also trying to get ready for a release branch. I think I'll push our
tickets to a new milestone. That seems to be better for both projects.

With any luck, I can revisit the long double code around then also.

>
>
> Thanks,
> Corinna
>
>

  reply	other threads:[~2022-12-02 17:19 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
2022-12-02 17:10       ` Corinna Vinschen
2022-12-02 17:19         ` Joel Sherrill [this message]
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=CAF9ehCUjAF8ms4VsPrzsLNaULBMufY8pu8bKHAkftk1C9G8COw@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).