From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Sam Ravnborg <sam@ravnborg.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix kallsyms dependency
Date: Sun, 8 Aug 2004 16:54:29 +0100 [thread overview]
Message-ID: <20040808165429.A17968@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040808154610.GA18740@mars.ravnborg.org>; from sam@ravnborg.org on Sun, Aug 08, 2004 at 05:46:10PM +0200
On Sun, Aug 08, 2004 at 05:46:10PM +0200, Sam Ravnborg wrote:
> On Sun, Aug 08, 2004 at 12:32:30PM +0100, Russell King wrote:
> > Hi,
> >
> > It appears that kallsyms data is not updated if the kallsyms program is
> > changed. The following patch adds an appropriate dependency.
>
> Added, and implemented your suggestion in scripts/Makefile
> with a few other CONFIG selections.
>
> Btw. any specific reason to hack kallsyms? Just curious if something
> shows up in this area.
Yes - later ARM binutils adds extra symbols like "$a" and "$d" to the
symbol table as "mapping symbols" (binutils terminology). It's not
clear whether these will continue to be visible via normal tools or
not, and I was considering getting kallsyms to filter them out.
Depending on the outcome of the binutils side depends whether or not
I end up modifying kallsyms to ignore these symbols and whether we
end up saying "binutils earlier than <todays latest and greatest
release> can not be used for ARM."
If a release of binutils is imminent which solves both the mapping
symbol visibility problem and the undefined symbol issue, then I
suspect its just all round easier to prevent the ARM kernel being
built with older binutils versions.
--
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
prev parent reply other threads:[~2004-08-08 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-08 11:32 Russell King
2004-08-08 15:46 ` Sam Ravnborg
2004-08-08 15:54 ` Russell King [this message]
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=20040808165429.A17968@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome