From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/7] package/gcc: enable float128 on powerpc64le with glibc >= 2.26 toolchains
Date: Wed, 30 Aug 2017 22:51:22 +0200 [thread overview]
Message-ID: <20170830225122.1b9bb0b8@windsurf.lan> (raw)
In-Reply-To: <20170827173606.13144-7-romain.naour@gmail.com>
Hello,
On Sun, 27 Aug 2017 19:36:05 +0200, Romain Naour wrote:
> float128 is now required on powerpc64le with glibc >= 2.26 toolchains.
>
> Fixes:
> running configure fragment for sysdeps/gnu
> running configure fragment for sysdeps/powerpc/powerpc64le
> checking if [...]powerpc64le-buildroot-linux-gnu-gcc supports binary128 floating point type... no
> checking if the target machine is at least POWER8... yes
> configure: error: *** binary128 floating point type (GCC >= 6.2) is required on powerpc64le.
>
> In order to prepare the glibc bump to this version, we enable
> binary128 floating point in gcc. This require at least gcc >= 6.2.
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> ---
> package/gcc/gcc.mk | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/package/gcc/gcc.mk b/package/gcc/gcc.mk
> index 49ccccf..54ef70c 100644
> --- a/package/gcc/gcc.mk
> +++ b/package/gcc/gcc.mk
> @@ -254,6 +254,14 @@ HOST_GCC_COMMON_CONF_OPTS += \
> --without-long-double-128
> endif
>
> +# Since glibc >= 2.26, poerpc64le requires double/long double which
Typo: powerpc64le.
> +# requires at least gcc 6.2.
> +# See sysdeps/powerpc/powerpc64le/configure.ac
> +ifeq ($(BR2_TOOLCHAIN_USES_GLIBC)$(BR2_TOOLCHAIN_GCC_AT_LEAST_6)$(BR2_powerpc64le),yyy)
So what happens if I build a gcc 5.x / glibc 2.26 / powerpc64le
toolchain ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-08-30 20:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 17:35 [Buildroot] [PATCH 0/7] glibc: bump to 2.26 Romain Naour
2017-08-27 17:36 ` [Buildroot] [PATCH 1/7] package/gcc: fix build issue with glibc 2.26 Romain Naour
2017-08-27 17:36 ` [Buildroot] [PATCH 2/7] " Romain Naour
2017-08-27 17:36 ` [Buildroot] [PATCH 3/7] package/mesa3d: fix build issue with glibc >= 2.26 Romain Naour
2017-08-30 20:49 ` Thomas Petazzoni
2017-08-30 20:57 ` Romain Naour
2017-08-27 17:36 ` [Buildroot] [PATCH 4/7] package/jsoncpp: fix build " Romain Naour
2017-08-27 17:36 ` [Buildroot] [PATCH 5/7] package/glibc: needs kernel headers >= 3.10 on powerpc64le Romain Naour
2017-08-27 17:36 ` [Buildroot] [PATCH 6/7] package/gcc: enable float128 on powerpc64le with glibc >= 2.26 toolchains Romain Naour
2017-08-30 20:51 ` Thomas Petazzoni [this message]
2017-08-30 21:07 ` Romain Naour
2017-08-27 17:36 ` [Buildroot] [PATCH 7/7] package/glibc: bump to 2.26 Romain Naour
2017-08-28 5:18 ` [Buildroot] [PATCH 0/7] glibc: " Bernd Kuhls
2017-08-28 7:59 ` Romain Naour
2017-09-02 9:56 ` Romain Naour
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170830225122.1b9bb0b8@windsurf.lan \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.