public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: <rsbecker@nexbridge.com>
To: <libc-help@sourceware.org>
Cc: "Bill Honaker" <bhonaker@xid.com>, <jojo@schmitz-digital.de>,
	"Shiva Subramanian" <shiva.subramanian@tcm.uk.com>,
	<mike_kilpatrick@nskopensource.com>
Subject: Re-port Intent for HPE NonStop (a.k.a. Tandem)
Date: Sun, 13 Mar 2022 08:43:30 -0400	[thread overview]
Message-ID: <01ec01d836d7$f59d39a0$e0d7ace0$@nexbridge.com> (raw)

Hi Glibc Team,

I have been asked by members of the HPE NonStop (formerly Tandem) community
to consider re-porting Glibc to the platform. There was a port back around
2.12 but that never made it to x86. The current situation is that the
platform is not on the list of known ports. Glibc is a dependency of many
projects that we want to bring to the platform. How can this be pursued? My
team is willing to officially support the port once done. Although POSIX
compliant, we are limited to using a c99 compiler. gcc does not port, making
this interesting.

Thanks for any pointers.

Note: The link http://www.gnu.org/software/libc/development.html on your
wiki page https://sourceware.org/glibc/wiki/#Development gets a 404.

Regards,
Randall

--
Brief whoami: NonStop&UNIX developer since approximately
UNIX(421664400)
NonStop(211288444200000000)
-- In real life, I talk too much.





             reply	other threads:[~2022-03-13 12:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-13 12:43 rsbecker [this message]
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
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='01ec01d836d7$f59d39a0$e0d7ace0$@nexbridge.com' \
    --to=rsbecker@nexbridge.com \
    --cc=bhonaker@xid.com \
    --cc=jojo@schmitz-digital.de \
    --cc=libc-help@sourceware.org \
    --cc=mike_kilpatrick@nskopensource.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).