public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Martin Schlemmer <azarah@nosferatu.za.org>
Cc: Tom Rini <trini@kernel.crashing.org>,
	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 20:52:55 +0100	[thread overview]
Message-ID: <20040701205255.F8389@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1088711048.8875.5.camel@nosferatu.lan>; from azarah@nosferatu.za.org on Thu, Jul 01, 2004 at 09:44:10PM +0200

On Thu, Jul 01, 2004 at 09:44:10PM +0200, Martin Schlemmer wrote:
> You might try (which should be on any kernel mirror):
> 
> GNU assembler 2.15.91.0.1 20040527
> 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 `i686-pc-linux-gnu'.

I don't think there's any point in trying - I just received a mail
from Nick Clifton who has found the problem in the ARM backend of
GAS and is apparantly in the process of committing it to CVS.

So, all ARM binutils versions from 2002 to date are affected by
the bug.

Whether ld --no-undefined successfully producing binaries with
undefined symbols is a problem or not remains unclear, however.

Even so, we still can not check whether we are actually using a late
enough version of binutils and force kernel build failure on that
basis.  About the best we can do is as I originally suggested which
is to add a postprocessing step after we link a binary object to
ensure there are no undefined symbols remaining.

The alternative is we just say "Sorry, we're not prepared to provide
any form of support for problems reported for ARM builds until the
next stable release of binutils."  Realistically, I don't think
that's an acceptable position to take.

Therefore, unless anyone has any objections, I shall be cooking up
a patch which adds an extra pass to any final object link for the
kernel build system.

-- 
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

  reply	other threads:[~2004-07-01 19:53 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
2004-07-01 19:44     ` Martin Schlemmer
2004-07-01 19:52       ` Russell King [this message]
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=20040701205255.F8389@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=azarah@nosferatu.za.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