From: Ralf Baechle <ralf@linux-mips.org>
To: Manuel Lauss <manuel.lauss@gmail.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
Matthew Fortune <Matthew.Fortune@imgtec.com>,
Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: [RFC PATCH V2] MIPS: fix build with binutils 2.24.51+
Date: Mon, 25 Aug 2014 21:57:07 +0200 [thread overview]
Message-ID: <20140825195707.GK25892@linux-mips.org> (raw)
In-Reply-To: <CAOLZvyG4F_PCb5hbws1_e8nCeJ+odvnC5u=yitSe9CwY3TWZdw@mail.gmail.com>
On Mon, Aug 25, 2014 at 09:29:24PM +0200, Manuel Lauss wrote:
> > Otherwise we'd have to bump the binutils requirement up to 2.19; this
>
> Do people really update their toolchain so rarely?
The users of very old toolchains mostly fall into two categories:
- build farms. All that matters is if the code is building as it probably
won't ever get to see a CPU from the inside.
- users running into issues with an old kernel in an otherwise well
running system. They will try to use whatever is installed because
an upgrade can be technically hard - or somebody most likely wearing a
tie may throw a tantrum at the thought of upgrding.
Ralf
next prev parent reply other threads:[~2014-08-25 19:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 16:27 [RFC PATCH V2] MIPS: fix build with binutils 2.24.51+ Manuel Lauss
2014-08-25 12:51 ` Ralf Baechle
2014-08-25 14:27 ` Maciej W. Rozycki
2014-08-25 19:29 ` Manuel Lauss
2014-08-25 19:57 ` Ralf Baechle [this message]
2014-08-25 19:57 ` Maciej W. Rozycki
2014-08-26 10:45 ` Matthew Fortune
2014-08-26 10:45 ` Matthew Fortune
2014-10-10 14:39 ` Markos Chandras
2014-10-10 14:39 ` Markos Chandras
2014-10-10 14:40 ` Markos Chandras
2014-10-10 14:40 ` Markos Chandras
2014-10-11 6:53 ` Manuel Lauss
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=20140825195707.GK25892@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Matthew.Fortune@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=manuel.lauss@gmail.com \
/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