Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] configs/stm32f429: force usage of BINUTILS 2.28.x
Date: Wed, 30 May 2018 18:24:20 +0200	[thread overview]
Message-ID: <20180530162420.GC2592@scaer> (raw)
In-Reply-To: <5d5e71dc-66ad-3a09-9e1e-863df0de89f2@gezedo.com>

Laurent, All,

On 2018-05-30 14:12 +0200, Laurent GONZALEZ spake thusly:
> On 29/05/2018 23:32, Thomas Petazzoni wrote:
> > On Tue, 29 May 2018 12:09:27 +0000, Christophe PRIOUZEAU wrote:
> > So in fact the proposal that was made back in April at
> > http://lists.busybox.net/pipermail/buildroot/2018-April/219223.html was
> > in the end better.
> Similarly, one can argue that this patch impacts every software, whereas
> only linux kernel is not compatible with newer binutils.

That's not true, as other packages have been reportedly broken as well,
namely libavcodec and openssl (at least):
    http://lists.infradead.org/pipermail/linux-arm-kernel/2017-November/543467.html

So, it's not just about the kernel; virtually any package that has some
ARM/Thumb assembly is impacted.

But once those packages are fixed upstream, well eventually get an
updated version in Buildroot, which fixes that issue, and in the end,
only the kernel wil end up being impacted (because there are so many
older kernels out there in the wild...).

Regards,
Yann E. MORIN.

> Using this kernel patch may help to only fix what need to be fixed:
> 
> http://lists.infradead.org/pipermail/linux-arm-kernel/2018-March/565390.html
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2018-05-30 16:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29 12:09 [Buildroot] [PATCH 1/2] configs/stm32f429: force usage of BINUTILS 2.28.x Christophe PRIOUZEAU
2018-05-29 12:09 ` [Buildroot] [PATCH 2/2] configs/stm32f469: " Christophe PRIOUZEAU
2018-05-29 12:49   ` Romain Naour
2018-05-29 12:39 ` [Buildroot] [PATCH 1/2] configs/stm32f429: " Romain Naour
2018-05-29 12:47   ` Christophe PRIOUZEAU
2018-05-29 12:48   ` Romain Naour
2018-05-29 15:51 ` Peter Korsgaard
2018-05-29 21:32 ` Thomas Petazzoni
2018-05-30 12:12   ` Laurent GONZALEZ
2018-05-30 16:24     ` Yann E. MORIN [this message]
2018-05-30 15:24   ` Christophe PRIOUZEAU
2018-05-30 15:42     ` Thomas Petazzoni
2018-05-30 20:35       ` Arnout Vandecappelle
2018-05-30 20:41         ` Thomas Petazzoni
2018-05-30 20:46           ` Romain Naour
2018-05-31  8:34           ` Christophe PRIOUZEAU
2018-05-31  9:13             ` Arnout Vandecappelle
2018-05-31  9:16             ` Thomas Petazzoni

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=20180530162420.GC2592@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