From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Makefile.in: set -fno-dwarf2-cfi-asm for m68k_cf
Date: Sun, 13 Jan 2019 14:23:07 +0100 [thread overview]
Message-ID: <20190113142307.55b7cd45@windsurf.home> (raw)
In-Reply-To: <20190112195039.24984-1-fontaine.fabrice@gmail.com>
Hello,
On Sat, 12 Jan 2019 20:50:39 +0100, Fabrice Fontaine wrote:
> Another package (libsquish) is affected by the
> "Internal error in emit_expr_encoded at dw2gencfi.c:215".
>
> This error already affects 5 packages and is due to binutils, see:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79509
>
> No report has been made to binutils yet however as suggested by Yann
> during review of woff2 workaround
> (https://patchwork.ozlabs.org/patch/911344/), remove the workarounds
> from all these packages and put it in package/Makefile.in
>
> Fixes:
> - http://autobuild.buildroot.org/results/77e06c092f4e7804dc166e259b25e779e5f1e83a
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
> package/Makefile.in | 6 ++++++
> package/berkeleydb/berkeleydb.mk | 7 -------
> package/kmsxx/kmsxx.mk | 6 ------
> package/lcdapi/lcdapi.mk | 6 ------
> package/libasplib/libasplib.mk | 8 --------
> package/woff2/woff2.mk | 6 ------
> 6 files changed, 6 insertions(+), 33 deletions(-)
Applied to master, thanks. Let's see if it breaks some packages or
not :)
It would be nice to make a proper bug report to upstream binutils,
though.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-01-13 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 19:50 [Buildroot] [PATCH 1/1] Makefile.in: set -fno-dwarf2-cfi-asm for m68k_cf Fabrice Fontaine
2019-01-13 13:23 ` Thomas Petazzoni [this message]
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=20190113142307.55b7cd45@windsurf.home \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox