public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Andrew Morton <akpm@osdl.org>,
	William Lee Irwin III <wli@holomorphy.com>,
	jdike@addtoit.com, kai@germaschewski.name, sam@ravnborg.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] 2.6.8-rc4-mm1 - Fix UML build
Date: Tue, 17 Aug 2004 13:51:39 +0100	[thread overview]
Message-ID: <20040817135139.E25385@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040817144527.GA7286@mars.ravnborg.org>; from sam@ravnborg.org on Tue, Aug 17, 2004 at 04:45:27PM +0200

On Tue, Aug 17, 2004 at 04:45:27PM +0200, Sam Ravnborg wrote:
> On Mon, Aug 16, 2004 at 10:10:17PM -0700, Andrew Morton wrote:
> > William Lee Irwin III <wli@holomorphy.com> wrote:
> > >
> > > On Tue, Aug 17, 2004 at 02:02:21AM -0400, Jeff Dike wrote:
> > > > The undefined symbol checking is continuing to cause UML pain.  This time,
> > > > it picked up a bunch of 'w' symbols as undefined.  They were present in the
> > > > 2.6.8-rc4-mm1 vmlinux and caused no problems for the final link, so I added
> > > > them as a second special case to mksysmap (and I just noticed that I forgot
> > > > a comment there - I can submit a patch for that if there's demand for one).
> > > 
> > > Likewise for sparc64; the 'w' symbols are showing up as 'undefined'
> > > there too. Probably because [^w] isn't behaving as expected.
> > > 
> > 
> > Sigh.  That patch is causing a ton of grief.  But Russell's reasons for
> > needing it on ARM were solid, and it is a bit weird for any architecture to
> > have undefined symbols in vmlinux.  I guess we persist.
> Please note that the functionality is moved to scripts/mksysmap,
> so Russell's original ldchk needs to be backed out.

I'm hopeful that the next release of binutils (any ideas when that'll
be?) should resolve the various problems I've found.

At that point, I think we should consider whether to keep the check
(for possible problems in the future) and/or prevent older ARM
binutils building the kernel.  That depends whether forcing all ARM
people to use the latest and greatest binutils (which may have other
issues) is really the best plan...

-- 
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-08-17 12:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-12  4:14 [PATCH 1/3] 2.6.8-rc4-mm1 - Fix UML build Jeff Dike
2004-08-15 22:06 ` Andrew Morton
2004-08-17  6:02   ` Jeff Dike
2004-08-17  5:06     ` William Lee Irwin III
2004-08-17  5:10       ` Andrew Morton
2004-08-17 14:45         ` Sam Ravnborg
2004-08-17 12:51           ` Russell King [this message]
2004-08-17  5:08     ` Andrew Morton
2004-08-17 19:15       ` Jeff Dike
2004-08-17 18:26         ` Andrew Morton
2004-08-18  2:58           ` Jeff Dike
2004-08-18 18:28           ` Chris Wedgwood
2004-08-17  8:55     ` Andreas Schwab
2004-08-17 18:17       ` Jeff Dike

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=20040817135139.E25385@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=jdike@addtoit.com \
    --cc=kai@germaschewski.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=wli@holomorphy.com \
    /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