From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 2D60F3858C27 for ; Mon, 14 Mar 2022 07:55:01 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 2D60F3858C27 Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-32-qxVaotmRPgqQuZykvUPCUg-1; Mon, 14 Mar 2022 03:54:55 -0400 X-MC-Unique: qxVaotmRPgqQuZykvUPCUg-1 Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 11FF5299E77D; Mon, 14 Mar 2022 07:54:55 +0000 (UTC) Received: from oldenburg.str.redhat.com (unknown [10.39.192.88]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 5ED1E54EC84; Mon, 14 Mar 2022 07:54:53 +0000 (UTC) From: Florian Weimer To: Cc: , mike_kilpatrick@nskopensource.com, Shiva Subramanian , Bill Honaker , jojo@schmitz-digital.de Subject: Re: Re-port Intent for HPE NonStop (a.k.a. Tandem) References: <01ec01d836d7$f59d39a0$e0d7ace0$@nexbridge.com> Date: Mon, 14 Mar 2022 08:54:51 +0100 In-Reply-To: <01ec01d836d7$f59d39a0$e0d7ace0$@nexbridge.com> (rsbecker@nexbridge.com's message of "Sun, 13 Mar 2022 08:43:30 -0400") Message-ID: <87k0cxynn8.fsf@oldenburg.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.85 on 10.11.54.9 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-4.8 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_SHORT, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H5, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 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: Mon, 14 Mar 2022 07:55:02 -0000 > 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. It must have been a private port, not released to the general public. Does HPE NonStop provide a stable kernel interface? Linux is somewhat unique in that. Other systems require some level of synchronization between libc and kernel updates. > 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. Can you use a GCC cross-compiler? We need a publicly available, free (libre) toolchain for any port. This is both a matter of policy, and also to prevent the port from bit-rotting. > Note: The link http://www.gnu.org/software/libc/development.html on your > wiki page https://sourceware.org/glibc/wiki/#Development gets a 404. I've removed this section because it is outdated. I'm not sure if we would accept ports to new kernels at this point. (New targets is a different matter.) Thanks, Florian