mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Ankit Paraskar <>
To: Rich Felker <>
Cc: "" <>,
	"Gerrit Huizenga [Notes]" <>,
	Prashant Khoje <>
Subject: RE: [musl] Configuration gives error on ppc64le arch for musl repo
Date: Tue, 5 Jul 2022 13:54:32 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 2903 bytes --]


Sent from Mail<> for Windows

From: Ankit Paraskar<>
Sent: 29 June 2022 17:50
To: Rich Felker<>
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.

Ankit P

Sent from Mail<> for Windows

From: Rich Felker<>
Sent: 10 June 2022 18:15
To: Ankit Paraskar<>
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 version 1.2.1:-
> Download link:-
> 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).


[-- Attachment #2: Type: text/html, Size: 5620 bytes --]

  reply	other threads:[~2022-07-05 14:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 11:14 [musl] Configuration gives error on ppc64le arch for must repo Ankit Paraskar
2022-06-10 12:09 ` David Edelsohn
2022-06-10 12:44 ` Rich Felker
2022-06-29 12:20   ` [musl] Configuration gives error on ppc64le arch for musl repo Ankit Paraskar
2022-07-05 13:54     ` Ankit Paraskar [this message]
2022-07-21  5:46       ` Ankit Paraskar
     [not found]         ` < <>
2022-07-21 13:12           ` alice
2022-07-21 14:08         ` David Edelsohn

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 NNTP newsgroup(s).