From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: binutils woes
Date: Thu, 1 Jul 2004 19:07:20 +0100 [thread overview]
Message-ID: <20040701190720.C8389@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040701174731.GD15960@smtp.west.cox.net>; from trini@kernel.crashing.org on Thu, Jul 01, 2004 at 10:47:31AM -0700
On Thu, Jul 01, 2004 at 10:47:31AM -0700, Tom Rini wrote:
> On Thu, Jul 01, 2004 at 05:52:31PM +0100, Russell King wrote:
>
> > Hi guys,
> >
> > On ARM, we appear to have somewhat of a problem with binutils. At
> > least the following binutils suffer from a problem whereby it is
> > possible to create programs which contain undefined symbols:
> [snip]
> > I think the only way we can ensure kernel correctness is to add a
> > subsequent stage to kbuild such that whenever we generate a final
> > program, we grep the 'nm' output for undefined symbols.
> >
> > Comments?
>
> Is there a version of binutils that really does get things right? If
> so, can't you Just Say No to older versions and force people to upgrade
> (with a simple testcase done upfront) ?
I've just tested:
GNU assembler 2.15.90 20040409
Copyright 2002 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License. This program has absolutely no warranty.
This assembler was configured for a target of `arm-linux'.
and it also is aflicted with the same problem. I guess the answer
to your question is that currently there are no recent versions which
work correctly.
Looking at the timescale of 2.13 through to present day, we're talking
potentially of 2 years of binutils versions with this problem, and even
if it was fixed tomorrow, I don't think it's acceptable to say "use the
latest binutils version."
Also, I have just received another report that somewhere in the kernel
is an undefined reference to another symbol - I_BIT, but where we have
no idea at present...
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-07-01 18:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 16:52 binutils woes Russell King
2004-07-01 17:47 ` Tom Rini
2004-07-01 18:07 ` Russell King [this message]
2004-07-01 19:44 ` Martin Schlemmer
2004-07-01 19:52 ` Russell King
2004-07-01 22:12 ` Russell King
2004-07-01 22:21 ` Andrew Morton
2004-07-01 22:22 ` Russell King
2004-07-02 10:56 ` Michael Buesch
2004-07-11 11:32 ` Russell King
2004-07-11 13:56 ` Russell King
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=20040701190720.C8389@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=trini@kernel.crashing.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