From: Randy Dunlap <rdunlap@xenotime.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
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>,
Vegard Nossum <vegard@kernel.org>
Subject: Re: RFC: x86: kill binutils 2.16.x?
Date: Wed, 2 Mar 2011 12:30:50 -0800 [thread overview]
Message-ID: <20110302123050.a322a8da.rdunlap@xenotime.net> (raw)
In-Reply-To: <20110302202551.GA7191@merkur.ravnborg.org>
On Wed, 2 Mar 2011 21:25:51 +0100 Sam Ravnborg wrote:
> On Wed, Mar 02, 2011 at 12:11:31PM -0800, H. Peter Anvin 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?
>
> The binaries has never worked for me (on my Intel Atom 32 bit box).
> Today I use crosstool-ng - which works great.
> [Need to polish my patch to add saprc support...]
>
> URL: http://ymorin.is-a-geek.org/projects/crosstool
Hm, thanks, I'll try that. I was also having problems with the kernel.org
crosstools...
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-03-02 20:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 18:15 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 [this message]
2011-03-02 21:28 ` Vegard Nossum
2011-03-02 21:29 ` H. Peter Anvin
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 21:28 ` Benjamin Herrenschmidt
2011-03-08 21:56 ` Scott Wood
2011-03-08 21:59 ` Kyle Moffett
2011-03-08 23:13 ` Benjamin Herrenschmidt
2011-03-08 23:43 ` Kyle Moffett
2011-03-09 4:39 ` Segher Boessenkool
2011-03-10 8:50 ` Michal Marek
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=20110302123050.a322a8da.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=vegard@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
all inboxes | Powered by JetHome®