From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 17315 invoked from network); 21 Jul 2022 14:08:33 -0000 Received: from second.openwall.net (193.110.157.125) by inbox.vuxu.org with ESMTPUTF8; 21 Jul 2022 14:08:33 -0000 Received: (qmail 5377 invoked by uid 550); 21 Jul 2022 14:08:29 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 5342 invoked from network); 21 Jul 2022 14:08:28 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3AKIVbCFjuP2zwLtkr2R30PwOsoZSTg71gyV/hD4Cr0=; b=Lp8D0C/0vlTrUXRTB55JDV/WTOSHgjCTYwEvfZEjfZf1i+52PlftzT+ygbDyF0ZnM1 ZZ0o0C98pvnBi6+C4ko7xDIIDx5UfxN3pY9XbYWV+T1rHxiQZNUCPIKRSvcz6Db8DEHP Ftez+KvpQKzfesORT6PpfpUaGmppLQHCb6hP+oQAIkRCdMZmgdvc4Lno4fZt9VsBjOmf a+E59uoD5HNvkqjhg28kdOp3Z4zvKkX0bJ3Ez2Ik6Qx9Hzb1IFiAWH4BXx+ohzOKzVSZ jTyYhBwIcshUDSUJfNmjMkgtw+fcuC70KOoApLm6VdLnL/4QE1gQjHx5LQ9cP83asxnf T2ug== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3AKIVbCFjuP2zwLtkr2R30PwOsoZSTg71gyV/hD4Cr0=; b=hIkLaFC9fVsRDHl9j4vOzd7xe/jb2PwVoN/8L7f3RdW1e62yyWtAyPwMa/CpBHmn6D hkG2NfacVng5w16EIM2k4hBpnB0TpeVHYezfl/DUyCQG0pf9Je+Fa7KHtO5eQyFYdM14 kwkymiPvH+NsgvjXBN03/HrvHbnlK/mST+OjQJM7ar4+tL6dqxrISLqRqPcIWU9+rrmJ cYNh+sxvTtoXNNehwfkYtHcCvA/hFlDLyIRxeidynRF4ay108TlyxDWRfz4CqGHSFFtw xPmG/uXjeBjC8MXWTvRUxEUAqQVlp4CLqwwiXODmDjdr8ZjnbVDGs11ddpVzRQZCFieL jBAg== X-Gm-Message-State: AJIora92lYQ8OZaVhIz+c02fSZqh4QKlWl39IcA2DGM179FJBSOBEp32 Wz6BEOf4Ke2h8G6AHcg7kFmDvRqJQrCuZZBU14IuwNJf X-Google-Smtp-Source: AGRyM1sGdpTxtCe0/g7srbLUY1kXFNajW9BmxrrS2g7DHGzCDnVeYhRQ87THULewvsvB1x13QIO3m/b4nCqL/IhZd5o= X-Received: by 2002:a17:902:8505:b0:16c:cf05:dc59 with SMTP id bj5-20020a170902850500b0016ccf05dc59mr31981094plb.125.1658412493400; Thu, 21 Jul 2022 07:08:13 -0700 (PDT) MIME-Version: 1.0 References: <20220610124454.GF7074@brightrain.aerifal.cx> In-Reply-To: From: David Edelsohn Date: Thu, 21 Jul 2022 10:08:00 -0400 Message-ID: To: musl@lists.openwall.com, Ankit Paraskar Cc: Rich Felker , "Gerrit Huizenga [Notes]" , Prashant Khoje Content-Type: text/plain; charset="UTF-8" Subject: Re: [musl] Configuration gives error on ppc64le arch for musl repo Ankit, The problem is with the toolchain that you are using, not with Musl Libc. The Musl community is not going to fix it for you. Please stop waiting for them or implying that they should fix the problem with your build environment. Thanks, David On Thu, Jul 21, 2022 at 8:48 AM Ankit Paraskar wrote: > > Dear Team/Rich, > > Any updates ? > > > > Regards, > > Ankit Paraskar > > > > > > Sent from Mail for Windows > > > > From: Ankit Paraskar > Sent: 05 July 2022 19:24 > To: Rich Felker > Cc: musl@lists.openwall.com; Gerrit Huizenga [Notes]; Prashant Khoje > Subject: RE: [EXTERNAL] Re: [musl] Configuration gives error on ppc64le arch for musl repo > > > > ++ > > > > Sent from Mail for Windows > > > > From: Ankit Paraskar > Sent: 29 June 2022 17:50 > To: Rich Felker > Cc: musl@lists.openwall.com > Subject: RE: [EXTERNAL] Re: [musl] Configuration gives error on ppc64le arch for musl repo > > > > Thank you for the suggestion , this really clarified the error. > > Would also appreciate to share information on code contribution for musl repo, aspect of CLA Contributor License Agreement - Wikipedia requirements. > > > > Thanks, > > Ankit P > > > > > > Sent from Mail for Windows > > > > From: Rich Felker > Sent: 10 June 2022 18:15 > To: Ankit Paraskar > Cc: musl@lists.openwall.com > Subject: [EXTERNAL] Re: [musl] Configuration gives error on ppc64le arch for must repo > > > > On Fri, Jun 10, 2022 at 11:14:03AM +0000, Ankit Paraskar wrote: > > Dear Team, > > > > While trying to configure musl package on power arch(ppc64le) we are getting the below configure issue > > > > Reflink:- > > musl - musl - an implementation of the standard library for Linux-based systems (musl-libc.org) > > > > Musl version 1.2.1:- > > Download link:- https://git.musl-libc.org/cgit/musl/snapshot/musl-1.2.1.tar..gz > > > > > > Detailed issue. > > > > Architure used:- > > uname -a > > Linux f1a836851f19 4.18.0-348.12.2.el8_5.ppc64le #1 SMP Mon Jan 17 06:49:39 EST 2022 ppc64le ppc64le ppc64le GNU/Linux > > > > > > Issue faced:- > > ../configure > > ............ > > checking preprocessor condition _CALL_ELF == 2... true > > checking preprocessor condition __LITTLE_ENDIAN__... true > > checking preprocessor condition _SOFT_FLOAT... false > > configured for powerpc64 variant: powerpc64le > > checking whether compiler's long double definition matches float.h... no > > ../configure: error: unsupported long double type > > You need a toolchain built for powerpc64le-linux-musl target where > long double has the same size/range/representation as double. The musl > ABI for ppc64 uses this because the legacy IBM double-double type for > long double does not match our policy of only using IEEE-conforming > types for long double (which various code in musl depends on), and > support for IEEE quad on ppc64 is limited (even moreso at the time the > port was added) and would have tied us/users to particular compilers > that support it. > > If you're trying to use the musl-gcc wrapper on a glibc host, you > ~may~ be able to make it work by setting the CC variable to something > to override, like CC="gcc -mno-long-double-128" or CC="gcc > -mlong-double-64" (not sure which if either of those works; the GCC > docs seem to be omitting it but referring to it elsewhere). > > Rich > > > > > >