From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] package/binutils: switch to use 2.33.1 as the default version
Date: Mon, 29 Jun 2020 22:51:21 +0200 [thread overview]
Message-ID: <20200629225121.468e8a73@windsurf> (raw)
In-Reply-To: <20200625121302.2286527-2-romain.naour@gmail.com>
On Thu, 25 Jun 2020 14:13:01 +0200
Romain Naour <romain.naour@gmail.com> wrote:
> Now that binutils 2.34 has been released, it is time to move to
> binutils 2.33.1 as the default binutils version, instead of 2.32.
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> ---
> package/binutils/Config.in.host | 2 +-
> package/binutils/binutils.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to master, thanks.
However, I wondered about this:
-BINUTILS_VERSION = 2.32
+BINUTILS_VERSION = 2.33.1
and the BR2_BINFMT_FLAT case. Indeed, if you don't build a
host-binutils and only a target binutils, the version compiled is now
going to be 2.33.1, which is "broken" on BINFMT_FLAT platforms. So I
thought we should keep using 2.32 on those platforms.
But then, in fact, we don't have support for building elf2flt for the
target anyway, so we're not building any useful binutils for the target
for BINFMT_FLAT platforms. So I just left your patch as-is.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-06-29 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 12:13 [Buildroot] [PATCH 1/3] package/binutils: add version 2.34 Romain Naour
2020-06-25 12:13 ` [Buildroot] [PATCH 2/3] package/binutils: switch to use 2.33.1 as the default version Romain Naour
2020-06-29 20:51 ` Thomas Petazzoni [this message]
2020-06-25 12:13 ` [Buildroot] [PATCH 3/3] package/binutils: remove version 2.31.1 Romain Naour
2020-06-29 20:51 ` Thomas Petazzoni
2020-06-29 20:45 ` [Buildroot] [PATCH 1/3] package/binutils: add version 2.34 Thomas Petazzoni
2020-06-29 20:46 ` 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=20200629225121.468e8a73@windsurf \
--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