From: Florian Weimer <fweimer@redhat.com>
To: "Joachim Schmitz" <jojo@schmitz-digital.de>
Cc: <rsbecker@nexbridge.com>, <libc-help@sourceware.org>,
<mike_kilpatrick@nskopensource.com>,
"'Shiva Subramanian'" <shiva.subramanian@tcm.uk.com>,
"'Bill Honaker'" <bhonaker@xid.com>
Subject: Re: AW: AW: Re-port Intent for HPE NonStop (a.k.a. Tandem)
Date: Mon, 14 Mar 2022 09:55:14 +0100 [thread overview]
Message-ID: <874k40zzf1.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <003c01d83780$66105e80$32311b80$@schmitz-digital.de> (Joachim Schmitz's message of "Mon, 14 Mar 2022 09:49:20 +0100")
* Joachim Schmitz:
> Not sure what you'd expect us to "release first", out compiler?
> If so: sorry, that won't happen. We don't even own it ourself.
> If we were able to port gcc, I believe we'd not be allowed to share it, due
> to proprietary code needed inside, needed to support the extension out
> platform needs.
Understood, but if you want to even have to a chance at an official
glibc port, you'd have to address these issues somehow.
> If glibc can't be made POSIX complaint, then that's where everything is lost
> for us, as far as I can tell.
There might be a misunderstanding here. glibc is not layered on top of
a POSIX interface, it itself is the POSIX interface for GNU systems.
Thanks,
Florian
next prev parent reply other threads:[~2022-03-14 8:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 12:43 rsbecker
2022-03-14 7:54 ` Florian Weimer
2022-03-14 8:12 ` AW: " Joachim Schmitz
2022-03-14 8:32 ` Florian Weimer
2022-03-14 8:49 ` AW: " Joachim Schmitz
2022-03-14 8:55 ` Florian Weimer [this message]
2022-03-14 12:48 ` rsbecker
2022-03-14 13:12 ` Florian Weimer
2022-03-14 14:20 ` Adhemerval Zanella
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=874k40zzf1.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=bhonaker@xid.com \
--cc=jojo@schmitz-digital.de \
--cc=libc-help@sourceware.org \
--cc=mike_kilpatrick@nskopensource.com \
--cc=rsbecker@nexbridge.com \
--cc=shiva.subramanian@tcm.uk.com \
/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).