From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Binutils version used on MIPS
Date: Wed, 2 Jul 2014 17:46:47 +0200 [thread overview]
Message-ID: <20140702174647.4021cc92@free-electrons.com> (raw)
In-Reply-To: <87simjbx8x.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Wed, 02 Jul 2014 17:23:26 +0200, Peter Korsgaard wrote:
> FYI, the current (arch independent) default binutils version is 2.22,
> not 2.24.
>
> We moved from 2.21 to 2.22 back in october:
>
> commit 9777dbedb012f68e54e14f9567d9dc0187d53b17
> Author: Peter Korsgaard <peter@korsgaard.com>
> Date: Sun Oct 6 23:45:10 2013 +0200
>
> binutils: default to 2.22
>
> 2.21.1 is getting quite old, the linker issues with 2.22 seems to be
> (mostly?) sorted out by now and armhf needs 2.22+, so let's bump the
> default version.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
>
>
> Time has perhaps come to move to 2.23 or 2.24, I don't really know.
Right, but Vicente patch simply removes the usage of a special version
for MIPS, so MIPS now just uses whatever is the default version used
for all architectures in Buildroot. Which I think is the right thing to
do, unless there are special reasons to use a different version than
the default one (such as AVR32 need of an old version, or
Microblaze/PowerPC64LE need of a new version).
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-07-02 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 18:14 [Buildroot] Binutils version used on MIPS Thomas Petazzoni
2014-07-02 7:51 ` Markos Chandras
2014-07-02 15:23 ` Peter Korsgaard
2014-07-02 15:46 ` Thomas Petazzoni [this message]
2014-07-02 19:51 ` Peter Korsgaard
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=20140702174647.4021cc92@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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