From: Linus Torvalds <torvalds@osdl.org>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Paulo Marques <pmarques@grupopie.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: ARM undefined symbols. Again.
Date: Fri, 25 Feb 2005 12:31:59 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0502251227480.9237@ppc970.osdl.org> (raw)
In-Reply-To: <20050225202349.C27842@flint.arm.linux.org.uk>
On Fri, 25 Feb 2005, Russell King wrote:
>
> We can't say "you must use the current CVS binutils to build the
> kernel" because that's not a sane toolchain base to build products
> on.
Sure. But it's probably enough that just a couple of core developers would
have a CVS version to make sure that when it occasionally happens, it gets
noticed quickly enough.
In other words, I don't think you can say "get the CVS version" to most
users, but I do not see for example you you or some of the people around
you don't have at least one setup set up with that fixed version.
This has been going on for at least a year, probably longer. I could
understand it if it was a "we found this old bug, and haven't had time to
get around it", but what I don't understand is when there's been a tools
bug that's been known about for a long time, and apparently nobody has
ever even bothered to try the fixed versions.
> And yes, the toolchain peoples point of view is "fix the kernel".
For a known bug where just having _one_ active developer using a fixed
tool would mean that this doesn't happen?
That makes no sense. Or, more likely, it means that the toolchain people
are incompetent bastards who don't care about bugs and have no pride at
all in what they do.
Linus
next prev parent reply other threads:[~2005-02-25 20:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 15:43 Russell King
2005-01-31 16:17 ` Sam Ravnborg
2005-02-07 11:43 ` Russell King
2005-02-08 19:42 ` Sam Ravnborg
2005-02-08 20:05 ` Russell King
2005-02-09 10:40 ` Russell King
2005-02-13 17:29 ` Russell King
2005-02-14 13:10 ` Paulo Marques
2005-02-25 19:48 ` Russell King
2005-02-25 19:59 ` Linus Torvalds
2005-02-25 20:23 ` Russell King
2005-02-25 20:31 ` Linus Torvalds [this message]
2005-02-25 20:54 ` Paulo Marques
[not found] ` <20050225210254.GB15773@mars>
2005-02-25 21:18 ` Paulo Marques
[not found] ` <20050225222720.D27842@flint.arm.linux.org.uk>
2005-02-25 22:49 ` Linus Torvalds
2005-02-25 22:52 ` Linus Torvalds
2005-02-26 11:17 ` Russell King
2005-02-26 11:29 ` Russell King
2005-02-25 22:03 ` Daniel Jacobowitz
2005-02-08 20:09 ` Alex Muradin
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=Pine.LNX.4.58.0502251227480.9237@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmarques@grupopie.com \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=sam@ravnborg.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®