From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] WIP: glibc 2.16 bump
Date: Mon, 14 Aug 2017 16:24:21 +0200 [thread overview]
Message-ID: <20170814162421.4228d9c1@windsurf> (raw)
In-Reply-To: <50207c65-6029-298c-6b69-f5937a107487@gmail.com>
Hello,
On Mon, 14 Aug 2017 15:04:10 +0200, Romain Naour wrote:
> > Can you try with this branch ?
> > https://github.com/RomainNaour/buildroot/tree/glibc-2.26
>
> I started a build on gcc farm and the only failing build is powerpc64le.
>
> I added this hunk in gcc.mk
>
> # Since Glibc 2.26, poerpc64le requires double/long double.
> # See sysdeps/powerpc/powerpc64le/configure.ac
> ifeq ($(BR2_TOOLCHAIN_USES_GLIBC)$(BR2_powerpc64le),yy)
> HOST_GCC_COMMON_CONF_OPTS += \
> --with-long-double-128
> endif
>
> I updated glibc-2.26 branch on github.
>
> Note: float128 require at least gcc 6.2 or gcc 7.1, so we need to disable older
> gcc on powerpc64le with glibc.
OK. I'm about to start a rebuild of all my toolchains + Qemu tests with
glibc 2.26 (and gcc 7.x, binutils 2.29, etc, i.e the bleeding edge
toolchains).
FYI: the two gcc patches that you needed to build glibc 2.26 are no
longer needed once you bump gcc to 7.2.0, which I have done for this
toolchain rebuild. I'll send the gcc 7.2.0 bump patch once all
toolchains have been rebuilt.
I'll let you know the result.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-08-14 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-12 10:24 [Buildroot] WIP: glibc 2.16 bump Romain Naour
2017-08-12 11:46 ` Thomas Petazzoni
2017-08-12 13:04 ` Romain Naour
2017-08-14 13:04 ` Romain Naour
2017-08-14 14:24 ` Thomas Petazzoni [this message]
2017-08-14 14:44 ` 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=20170814162421.4228d9c1@windsurf \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox