From: "H. Peter Anvin" <hpa@zytor.com>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Tony Breeds <tony@bakeyournoodle.com>
Subject: Re: RFC: x86: kill binutils 2.16.x?
Date: Wed, 02 Mar 2011 13:29:12 -0800 [thread overview]
Message-ID: <4D6EB6A8.6090808@zytor.com> (raw)
In-Reply-To: <AANLkTi=5C3-DkOGFZ3nWCgkQMWC=Va9ZoFRjyV2vxdg7@mail.gmail.com>
On 03/02/2011 01:28 PM, Vegard Nossum wrote:
> On 2 March 2011 21:11, H. Peter Anvin <hpa@zytor.com> wrote:
>> On 03/02/2011 12:03 PM, Andrew Morton wrote:
>>> On Wed, 02 Mar 2011 10:15:14 -0800
>>> "H. Peter Anvin" <hpa@zytor.com> wrote:
>>>
>>>> binutils 2.16 (and presumably its prereleases, binutils 2.15.9x) appears
>>>> to have more bugs than any other version of binutils released in modern
>>>> history, *before or after*.
>>>>
>>>> We chronically run into problems because that particular binutils
>>>> version breaks code that works fine elsewhere.
>>>>
>>>> I would like to know who would suffer from formally discontinuing
>>>> support for that version. I understand some version of SLES shipped it,
>>>> but I don't know for sure.
>>>>
>>>
>>> I gave up and became a customer of
>>> http://www.kernel.org/pub/tools/crosstool/index_old.shtml
>>
>> Vegard,
>>
>> The source directory in the above doesn't seem to match the binary
>> directories, and is stuck at binutils 2.16.1. At the very best this is
>> iffy from a GPL perspective, and very confusing to users.
>>
>> This is obviously a highly useful project, can we straighten out the
>> source situation?
>
> I only uploaded the binaries in
>
> http://www.kernel.org/pub/tools/crosstool/files/bin/old/
>
> which should match the sources in
>
> http://www.kernel.org/pub/tools/crosstool/files/src/
>
> The binaries outside old/ are not made by me, but Tony (added to Cc).
>
> I assume you're talking about the binaries _outside_ bin/old/, but let
> me know if I'm mistaken :-)
>
Sorry, you're right... I got confused because the index file is still
the old one...
-hpa
next prev parent reply other threads:[~2011-03-02 21:29 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 18:15 RFC: x86: kill binutils 2.16.x? H. Peter Anvin
2011-03-02 20:03 ` Andrew Morton
2011-03-02 20:11 ` H. Peter Anvin
2011-03-02 20:25 ` Sam Ravnborg
2011-03-02 20:30 ` Randy Dunlap
2011-03-02 21:28 ` Vegard Nossum
2011-03-02 21:29 ` H. Peter Anvin [this message]
2011-03-02 20:54 ` Thomas Gleixner
2011-03-02 21:02 ` H. Peter Anvin
2011-03-02 21:17 ` Thomas Gleixner
2011-03-02 22:59 ` H. Peter Anvin
2011-03-03 8:30 ` Ingo Molnar
2011-03-08 19:57 ` Kyle Moffett
2011-03-08 19:57 ` Kyle Moffett
2011-03-08 21:28 ` Benjamin Herrenschmidt
2011-03-08 21:28 ` Benjamin Herrenschmidt
2011-03-08 21:56 ` Scott Wood
2011-03-08 21:56 ` Scott Wood
2011-03-08 21:56 ` Scott Wood
2011-03-08 21:59 ` Kyle Moffett
2011-03-08 21:59 ` Kyle Moffett
2011-03-08 23:13 ` Benjamin Herrenschmidt
2011-03-08 23:13 ` Benjamin Herrenschmidt
2011-03-08 23:43 ` Kyle Moffett
2011-03-08 23:43 ` Kyle Moffett
2011-03-09 4:39 ` Segher Boessenkool
2011-03-09 4:39 ` Segher Boessenkool
2011-03-10 8:50 ` Michal Marek
2011-03-10 8:59 ` Ingo Molnar
2011-03-10 8:59 ` Ingo Molnar
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=4D6EB6A8.6090808@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tony@bakeyournoodle.com \
--cc=vegard.nossum@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.