Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] toolchain: add binutils bug 20765 to linaro Aarch64be
Date: Sun, 2 Dec 2018 17:27:02 +0100	[thread overview]
Message-ID: <20181202172702.29a7c6be@windsurf.home> (raw)
In-Reply-To: <698923c53dba1a744211581ff830d2294965ff69.1543759351.git.yann.morin.1998@free.fr>

Hello,

On Sun,  2 Dec 2018 15:04:16 +0100, Yann E. MORIN wrote:

> diff --git a/toolchain/toolchain-external/toolchain-external-linaro-aarch64-be/Config.in b/toolchain/toolchain-external/toolchain-external-linaro-aarch64-be/Config.in
> index 9e7d2a6233..72d33140da 100644
> --- a/toolchain/toolchain-external/toolchain-external-linaro-aarch64-be/Config.in
> +++ b/toolchain/toolchain-external/toolchain-external-linaro-aarch64-be/Config.in
> @@ -10,6 +10,7 @@ config BR2_TOOLCHAIN_EXTERNAL_LINARO_AARCH64_BE
>  	select BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_10
>  	select BR2_TOOLCHAIN_GCC_AT_LEAST_7
>  	select BR2_TOOLCHAIN_HAS_FORTRAN
> +	select BR2_TOOLCHAIN_HAS_BINUTILS_BUG_20765

Any idea why the aarch64-be toolchain is affected, but not the aarch64
toolchain ?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-12-02 16:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-02 14:04 [Buildroot] [PATCH 0/2] package/qt5base: disable for toolchains with binutils bug 20765 (branch yem/fixes) Yann E. MORIN
2018-12-02 14:04 ` [Buildroot] [PATCH 1/2] toolchain: add binutils bug 20765 to linaro Aarch64be Yann E. MORIN
2018-12-02 16:27   ` Thomas Petazzoni [this message]
2018-12-02 16:35     ` Yann E. MORIN
2018-12-02 14:04 ` [Buildroot] [PATCH 2/2] package/qt5: hide for toolchains with binutils bug 20765 Yann E. MORIN

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=20181202172702.29a7c6be@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