From: Corinna Vinschen <vinschen@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: newlib@sourceware.org, contact@phoenix-rtos.com
Subject: Re: [PATCH] newlib: drop phoenix support
Date: Thu, 17 Mar 2022 11:14:10 +0100 [thread overview]
Message-ID: <YjMJ8mr1XNBvejag@calimero.vinschen.de> (raw)
In-Reply-To: <YjMF1iWv/hwSpIls@calimero.vinschen.de>
On Mar 17 10:56, Corinna Vinschen wrote:
> [CC official contact address of the phoenix-rtos HQ]
The message you sent to jakub.sejdak@phoesys.com couldn't be delivered due to:
Recipient email address is possibly incorrect.
So let's see if anybody from the company reads the contact inbox.
> On Mar 14 23:58, Mike Frysinger wrote:
> > This code has not been updated since 2016, and it looks like it has
> > rotted quite a bit since. It does not build against the current set
> > of phoenix sources -- I had to hack both the kernel headers and the
> > newlib headers up to get it to build, and I still have no idea if it
> > actually links or runs. It seems like the project itself has moved
> > away from newlib and to its own C library:
> > https://phoenix-rtos.com/documentation/libc/README.md
> >
> > So since there's no interest from the phoenix folks to maintain this,
> > and it has a significant amount of non-standard code that we try to
> > keep up-to-date (without actually testing it), just punt it all.
>
> Let's wait another week for a reply from the phoenix folks. If we
> don't get one, feel free to push the patches same time next week.
>
>
> Thanks,
> Corinna
prev parent reply other threads:[~2022-03-17 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 3:58 Mike Frysinger
2022-03-17 9:56 ` Corinna Vinschen
2022-03-17 10:14 ` Corinna Vinschen [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=YjMJ8mr1XNBvejag@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=contact@phoenix-rtos.com \
--cc=newlib@sourceware.org \
--cc=vapier@gentoo.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).