From: "H. Peter Anvin" <hpa@zytor.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Jan Beulich <JBeulich@novell.com>,
Alexander van Heukelum <heukelum@fastmail.fm>,
Ingo Molnar <mingo@elte.hu>,
akpm@linux-foundation.org, "H. Peter Anvin" <hpa@linux.intel.com>,
David Howells <dhowells@redhat.com>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Partially revert patch that encloses asm-offset.h numbers in brackets
Date: Tue, 26 Oct 2010 09:33:47 -0700 [thread overview]
Message-ID: <4CC702EB.1000301@zytor.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1010261126590.15889@eddie.linux-mips.org>
On 10/26/2010 03:53 AM, Maciej W. Rozycki wrote:
>
> Also note that *.*.9x versions are snapshots from the FSF repository (so
> there's no fixed date associated with them), which also delegates
> maintenance responsibility to whoever packages them and makes available to
> people. In the state as imported from the repository they may have odd
> problems or grave bugs, as exhaustive regression testing is generally only
> made after a release branch has been created and otherwise changes to the
> head of the tree are only tested for a limited subset of targets before
> they are applied. Therefore local fixes are inevitable for them anyway.
>
Well, sort of... the x.x.9x releases used in production -- specifically
the ones with a numbering scheme like x.x.9x.0.x -- in the Linux world
tend to be the ones maintained and released by H.J. Lu:
http://www.kernel.org/pub/linux/devel/binutils/
> And last but not least binutils are one of the easier tools to build from
> sources, so installing a newer version, especially when it comes to native
> tools (hardly anyone uses cross-compilation targeting x86, I believe),
> somewhere under $HOME to use for kernel builds is a trivial effort:
>
> $ ./configure --prefix=$HOME/somewhere && make && make install
> $ PATH=$HOME/somewhere/bin:$PATH
>
> Certainly much easier than building the kernel, especially when it comes
> to selecting the right configuration options.
Yes, although there is also a version dependency between binutils and
gcc, as I unhappily found out trying to run an upversion gcc on an old
distro at one point.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2010-10-26 16:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 14:02 [PATCH] Partially revert patch that encloses asm-offset.h numbers in brackets David Howells
2010-10-25 14:34 ` Jan Beulich
2010-10-25 14:43 ` Ingo Molnar
2010-10-25 14:54 ` David Howells
2010-10-25 15:05 ` Jan Beulich
2010-10-25 15:17 ` Linus Torvalds
2010-10-25 15:29 ` Jan Beulich
2010-10-25 15:50 ` H. Peter Anvin
2010-10-25 16:16 ` Linus Torvalds
2010-10-25 16:37 ` H. Peter Anvin
2010-10-26 10:53 ` Maciej W. Rozycki
2010-10-26 16:33 ` H. Peter Anvin [this message]
2010-10-26 17:34 ` Maciej W. Rozycki
2010-10-25 15:59 ` David Howells
2010-10-25 17:51 ` H. Peter Anvin
2010-10-31 15:29 ` Alexander van Heukelum
2010-11-02 8:30 ` Ming Lei
2010-11-02 10:19 ` Alexander van Heukelum
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=4CC702EB.1000301@zytor.com \
--to=hpa@zytor.com \
--cc=JBeulich@novell.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=heukelum@fastmail.fm \
--cc=hpa@linux.intel.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).