From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] toolchain: add binutils bug 20765 to linaro Aarch64be
Date: Sun, 2 Dec 2018 17:35:09 +0100 [thread overview]
Message-ID: <20181202163509.GA2649@scaer> (raw)
In-Reply-To: <20181202172702.29a7c6be@windsurf.home>
Thomas, All,
On 2018-12-02 17:27 +0100, Thomas Petazzoni spake thusly:
> 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 ?
I was expecting that question, so I did my homework first, to get ready
to answer it:
I have no clue about that.
There, that was all I could dig up as a reason. ;-)
But more seriously, I think I'll take that patch back, because the
uopstream BZ is about aarch64, not aarch64be...
Regards,
Yann E. MORIN.
> Thanks,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-12-02 16:35 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
2018-12-02 16:35 ` Yann E. MORIN [this message]
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=20181202163509.GA2649@scaer \
--to=yann.morin.1998@free.fr \
--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