From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gcc: glibc >= 2.27 needs gcc >= 5 on aarch64
Date: Sun, 16 Sep 2018 21:27:40 +0200 [thread overview]
Message-ID: <20180916212740.71d1c3ed@windsurf> (raw)
In-Reply-To: <20180915155413.17663-1-romain.naour@gmail.com>
Hello,
On Sat, 15 Sep 2018 17:54:13 +0200, Romain Naour wrote:
> With the following defconfig:
> BR2_aarch64=y
> BR2_BINUTILS_VERSION_2_28_X=y
> BR2_GCC_VERSION_4_9_X=y
> BR2_TOOLCHAIN_BUILDROOT_CXX=y
>
> The build fail with this error:
> In file included from ../sysdeps/ieee754/flt-32/math_config.h:23:0,
> from ../sysdeps/ieee754/flt-32/e_expf.c:29:
> ../sysdeps/aarch64/fpu/math_private.h: In function 'roundtoint':
> ../sysdeps/aarch64/fpu/math_private.h:311:3: error: implicit declaration of function 'vrndn_f64' [-Werror=implicit-function-declaration]
> return vget_lane_f64 (vrndn_f64 (vld1_f64 (&x)), 0);
> ^
> cc1: all warnings being treated as errors
>
> vrndn_f64 function has been introduced in glibc code since version 2.27 [1].
> So we can't build a glibc based toolchain with gcc 4.9 anymore.
>
> Add a new dependency in the toolchain infra to avoid selecting
> glibc toolchain using gcc 4.9.
>
> [1] https://sourceware.org/git/?p=glibc.git;a=commit;h=72aa623345ada1276ed89dbc00fdff9639cb8eaf
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> Cc: Arnout Vandecappelle <arnout@mind.be>
> ---
> package/gcc/Config.in.host | 2 ++
> 1 file changed, 2 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-16 19:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-15 15:54 [Buildroot] [PATCH] package/gcc: glibc >= 2.27 needs gcc >= 5 on aarch64 Romain Naour
2018-09-16 19:27 ` Thomas Petazzoni [this message]
2018-10-01 21:51 ` Peter Korsgaard
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=20180916212740.71d1c3ed@windsurf \
--to=thomas.petazzoni@bootlin.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.