From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.kundenserver.de (mout.kundenserver.de [217.72.192.75]) by sourceware.org (Postfix) with ESMTPS id 8B0F93858418 for ; Mon, 14 Mar 2022 08:12:28 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8B0F93858418 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=schmitz-digital.de Authentication-Results: sourceware.org; spf=none smtp.mailfrom=schmitz-digital.de Received: from DodekaCore ([178.202.146.137]) by mrelayeu.kundenserver.de (mreue107 [213.165.67.113]) with ESMTPSA (Nemesis) id 1N2VGj-1o7qyO3gQJ-013wMy; Mon, 14 Mar 2022 09:12:07 +0100 From: "Joachim Schmitz" To: "'Florian Weimer'" , Cc: , , "'Shiva Subramanian'" , "'Bill Honaker'" References: <01ec01d836d7$f59d39a0$e0d7ace0$@nexbridge.com> <87k0cxynn8.fsf@oldenburg.str.redhat.com> In-Reply-To: <87k0cxynn8.fsf@oldenburg.str.redhat.com> Subject: AW: Re-port Intent for HPE NonStop (a.k.a. Tandem) Date: Mon, 14 Mar 2022 09:12:06 +0100 Message-ID: <003901d8377b$32ab1e90$98015bb0$@schmitz-digital.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQEXxrPuRx/llDaEPPRRpRc4hfKaWwFqVUXNrjQT5sA= Content-Language: de X-Provags-ID: V03:K1:sZpW2psKjv+yxqU5//j2iBadBwvQWapPq141R0OX5WbtFDpNZ6R /8WfBVIsIxgUFdvBB6r98orxk6j7WVWIuGUEY79HOSFq8DcAQYd+9IRpZkGZMLKnu5J4/as dBglAOh49tFs18/5ph1Z/lWUKIm1yckMJmVDxlwzQNdnKH7Bl6ue7P6LGyJXfFabSObRDbQ fURemwZvWbTcn6tDYSzEg== X-UI-Out-Filterresults: notjunk:1;V03:K0:UrDO5bP1Yw8=:BA7+Q1qIRzib+8hkRKBIuM o5nXafKVur3GJeqE22C30cG1VOcLCiKw/63EZtXwHvkNBzTPnBxh9zbUmTRcacZwTyv0ftXne mS65047ETTuIBHvkjwqN0yv4LmkRlGiMmMjTds+g4DbsnZ8Z8rhUCm2kgvSEEey/UD58Ocy9h HkJ0agHmndb2Gk8vOEJEZJ+6cnRoUEpnjmW9SewAu9j71+7Lzyjl5LOZXQn0/RI8xzlX1bKLJ fW+nULeJIGqIPw5h7XSmuEiQPiPipFJ/ZqQ05lfVSraElfQLdUAs1SbXY5DHC48M7jwScXMn9 zXioi2qOm2yz/i0FFCG+VWLRHVi+gnHc2mwYrxMsxm9ZbSORoUCg4BsnaA3Q0AYWw8JVzp6mn ryGg4uU+MzPipkp5lVwOnNFqzcxFG9gnZZ0q3Xlei2ZVklCQXm1JqVceWzEmvzI545qcB+FPf yQHoeIj4EQiQzUuIylv1d00M4+eIEXVJL1K3UozfZsbe3vudVdk5Z85T9zFper1GyHUO7VRRJ 7vpSavt2FsXdNDZLh4DsJctu7I7hwEhJjtPFShtAqhgpUlOOysX5ZAuVwCwavWgBOH+V6t+4y BOxw+R+QesONmyCpiTw4PWD2DgzLbgeHNskrje7q5DxA96bBcKutxuSceuhapyCuFwqJfgYgE juaqAYZ0LItQ9oL3oE1PdEW7XU75ueK/nKrMWElmoX9nCAeN36bLBLzoccfRNV4t6zTiumJv7 cb7S4ue2jOIC1Ytj X-Spam-Status: No, score=-0.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, KAM_SHORT, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=no 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 08:12:30 -0000 Hi Florian No idea whether that port had ever been send back upstream, it must have been done in 2007 or before. Not sure what you mean by "stable kernel interface"? No, sorry, unfortunately no gcc available nor possible to cross-compile, = it is actually the assembler part that is missing IIRC While gcc may be free (libre) it is also provides quite a few = non-standard features. Our compilers do have some extensions too, but generally are pretty strictly C89/90, C99 compliant. Bye, Jojo -----Urspr=FCngliche Nachricht----- Von: Florian Weimer =20 Gesendet: Montag, 14. M=E4rz 2022 08:55 An: rsbecker@nexbridge.com Cc: libc-help@sourceware.org; mike_kilpatrick@nskopensource.com; Shiva Subramanian ; Bill Honaker = ; jojo@schmitz-digital.de Betreff: Re: Re-port Intent for HPE NonStop (a.k.a. Tandem) > I have been asked by members of the HPE NonStop (formerly Tandem)=20 > community to consider re-porting Glibc to the platform. There was a=20 > 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=20 > officially support the port once done. Although POSIX compliant, we=20 > are limited to using a c99 compiler. gcc does not port, making this=20 > 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=20 > 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