From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] glibc: fix build breakage
Date: Thu, 11 Oct 2018 09:34:01 +0200 [thread overview]
Message-ID: <20181011093401.2f9d4af6@windsurf> (raw)
In-Reply-To: <20181011062348.22396-1-yegorslists@googlemail.com>
Hello,
On Thu, 11 Oct 2018 08:23:48 +0200, yegorslists at googlemail.com wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> On platforms with soft floating point glibc produces a compile time
> warning (maybe-uninitialized) that will be regarded as an error.
>
> Add upstream patch fixing this issue.
>
> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> ---
> ...soft-fp-ignore-maybe-uninitialized-w.patch | 88 +++++++++++++++++++
> 1 file changed, 88 insertions(+)
> create mode 100644 package/glibc/glibc-2.28-18-g2339d6a55eb7a7e040ae888e906adc49eeb59eab/0001-sysdeps-ieee754-soft-fp-ignore-maybe-uninitialized-w.patch
I've applied, but after tweaking the commit title to make it a bit more
specific. "fix build breakage" is indeed very fuzzy.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-10-11 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 6:23 [Buildroot] [PATCH] glibc: fix build breakage yegorslists at googlemail.com
2018-10-11 7:34 ` Thomas Petazzoni [this message]
2018-10-11 11:22 ` Yegor Yefremov
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=20181011093401.2f9d4af6@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.