From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from elephants.elehost.com (elephants.elehost.com [216.66.27.132]) by sourceware.org (Postfix) with ESMTPS id 685DF3858C78 for ; Sun, 13 Mar 2022 12:43:40 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 685DF3858C78 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=nexbridge.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=nexbridge.com Received: from Mazikeen (cpe00fc8d49d843-cm00fc8d49d840.cpe.net.cable.rogers.com [99.229.22.139] (may be forged)) (authenticated bits=0) by elephants.elehost.com (8.16.1/8.16.1) with ESMTPSA id 22DChZhn018102 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 13 Mar 2022 08:43:36 -0400 (EDT) (envelope-from rsbecker@nexbridge.com) Reply-To: From: To: Cc: "Bill Honaker" , , "Shiva Subramanian" , Subject: Re-port Intent for HPE NonStop (a.k.a. Tandem) Date: Sun, 13 Mar 2022 08:43:30 -0400 Organization: Nexbridge Inc. Message-ID: <01ec01d836d7$f59d39a0$e0d7ace0$@nexbridge.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: Adg21y5YIKbfw3LiQkWBzjFEp1/MlQ== Content-Language: en-ca X-Spam-Status: No, score=1.9 required=5.0 tests=BAYES_50, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, KAM_SHORT, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libc-help@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-help mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Mar 2022 12:43:41 -0000 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.