From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: Bernd Kuhls <bernd@kuhls.net>,
Romain Naour <romain.naour@gmail.com>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] toolchain: introduce BR2_TOOLCHAIN_HAS_BINUTILS_BUG_30730
Date: Mon, 7 Aug 2023 23:34:52 +0200 [thread overview]
Message-ID: <20230807233452.0209f199@windsurf> (raw)
In-Reply-To: <20230806215127.283714-1-giulio.benetti@benettiengineering.com>
On Sun, 6 Aug 2023 23:51:26 +0200
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> libheif package fails to build for the M68K architecture due to a binutils
> bug that leads to:
> Internal error in emit_expr_encoded at dw2gencfi.c:215
>
> Let's add binutils bug to avoid to deal with architectures in packages
> when a binutils bug arises. Let's instead deal directly with binutils
> bug number.
>
> It's been reported upstream:
> https://sourceware.org/bugzilla/show_bug.cgi?id=30730
>
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
> toolchain/Config.in | 6 ++++++
> 1 file changed, 6 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-08-07 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 21:51 [Buildroot] [PATCH 1/2] toolchain: introduce BR2_TOOLCHAIN_HAS_BINUTILS_BUG_30730 Giulio Benetti
2023-08-06 21:51 ` [Buildroot] [PATCH 2/2] package/libheif: let's use BR2_TOOLCHAIN_HAS_BINUTILS_BUG_30730 Giulio Benetti
2023-08-07 21:35 ` Thomas Petazzoni via buildroot
2023-08-07 21:34 ` Thomas Petazzoni via buildroot [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=20230807233452.0209f199@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=giulio.benetti@benettiengineering.com \
--cc=romain.naour@gmail.com \
--cc=thomas.de_schampheleire@nokia.com \
--cc=thomas.petazzoni@bootlin.com \
/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.