Received: from out1.migadu.com (out1.migadu.com [91.121.223.63])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id E92C5782B78
	for <~alpine/devel@lists.alpinelinux.org>; Tue,  5 Jan 2021 23:02:46 +0000 (UTC)
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dereferenced.org;
	s=default; t=1609887765;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding:
	 in-reply-to:in-reply-to:references:references;
	bh=bs3WjoNlYfVLCwV4XvCreaPjQ35cOxkG63OXnWTR/JA=;
	b=qEMpFz54jleL7r7ntK3sN8fXKMudP5Jbw0x8gWCD6Ks/QFEFWHWMCgeT197kM/hXHRkC3l
	2LwLhXOM0ppLLx0XIZeMMtRFa8WFInJEdScEs4I1YklgFaOAv4vIooed9TmDBqL45689x3
	+d2KYchB6a5RdumaM4275eNK6V6B36Y=
From: Ariadne Conill <ariadne@dereferenced.org>
To: "~alpine/devel@lists.alpinelinux.org" <~alpine/devel@lists.alpinelinux.org>
Cc: isixfiveyou <isixfiveyou@163.com>
Subject: Re: gcc does not support IBM extended format on ppc64le
Message-ID: <57506152.tmtHFIxSYy@nanabozho>
In-Reply-To: <129df644.75b4.176d29d0baa.Coremail.isixfiveyou@163.com>
References: <129df644.75b4.176d29d0baa.Coremail.isixfiveyou@163.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"
X-Migadu-Flow: FLOW_OUT
X-Migadu-Auth-User: ariadne@dereferenced.org
Date: Tue, 05 Jan 2021 23:02:45 GMT

Hello,

On Tuesday, 5 January 2021 05:54:36 MST isixfiveyou wrote:
> Hi,all:
>  I am trying to compile =E2=80=9Cglibc-2.32=E2=80=9D on ppc64le/alpine:3.=
11. when I run
> =E2=80=9C../configure =E2=80=94prefix=3D/usr=E2=80=9D ,the following erro=
r occurs:
>=20
>=20
> checking whether gcc -g -O2 -mlong-double-128 uses IBM extended format...=
 no
> checking whether gcc -g -O2 supports -mabi=3Dibmlongdouble... no
> configure: error: this configuration requires -mlong-double-128 IBM exten=
ded
> format support /glibc-2.32/build #

Alpine only supports IEEE format for long doubles.  We have no plans to=20
support the legacy IBM format.

Also, it is not advisable to use glibc on Alpine systems, this is an entire=
ly=20
unsupported configuration.  Use gcompat instead, it provides compatibility =
for=20
most glibc applications while being correctly integrated into the Alpine=20
system.

Ariadne