From: Ben Hutchings <ben@decadent.org.uk>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC][PATCH] [ia64] Raise minimum binutils version and remove
Date: Sun, 10 Oct 2010 21:00:12 +0000 [thread overview]
Message-ID: <1286744412.2955.239.camel@localhost> (raw)
In-Reply-To: <1286158823.3916.227.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]
On Mon, 2010-10-04 at 11:52 -0700, Tony Luck wrote:
> On Sun, Oct 3, 2010 at 7:20 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> > diff --git a/Documentation/Changes b/Documentation/Changes
> > index 4fb88f1..23fc499 100644
> > --- a/Documentation/Changes
> > +++ b/Documentation/Changes
> > @@ -30,7 +30,7 @@ isdn4k-utils.
> >
> > o Gnu C 3.2 # gcc --version
> > o Gnu make 3.80 # make --version
> > -o binutils 2.12 # ld -v
> > +o binutils 2.12 (2.16 for ia64) # ld -v
> > o util-linux 2.10o # fdformat --version
> > o module-init-tools 0.9.10 # depmod -V
> > o e2fsprogs 1.41.4 # e2fsck -V
>
> Won't this file become a complete mess if each architecture starts
> specifying its own version for each of the tools?
[...]
Maybe, though the only things likely to need per-architecture fixes or
features are gcc and binutils.
By the way, I did a little more research and found that the bug
unwcheck.py is checking for was in binutils 2.16, so the minimum would
actually have to be 2.17 (or a distro-fixed 2.16).
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2010-10-10 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 2:20 [RFC][PATCH] [ia64] Raise minimum binutils version and remove Ben Hutchings
2010-10-04 18:52 ` Tony Luck
2010-10-10 21:00 ` Ben Hutchings [this message]
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=1286744412.2955.239.camel@localhost \
--to=ben@decadent.org.uk \
--cc=linux-ia64@vger.kernel.org \
/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