From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Force build error on undefined symbols
Date: Sat, 10 Apr 2004 20:08:02 +0100 [thread overview]
Message-ID: <20040410200802.E4221@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040410172827.GA2106@mars.ravnborg.org>; from sam@ravnborg.org on Sat, Apr 10, 2004 at 07:28:27PM +0200
On Sat, Apr 10, 2004 at 07:28:27PM +0200, Sam Ravnborg wrote:
> How does output from your nm look?
> My version (GNU nm 2.14.90.0.5 20030722 (SuSE Linux)) looks like this:
> c04e56ac B zone_table
>
> So I assume an undefined symbol would look like this:
> 00000000 U undef_symbol
No, because an undefined symbol does not have an address associated with
it. So, it looks like this:
U symbol
More than one blank space at the beginning, U, then one space and the
symbol. On binutils built on 32-bit architectures, 9 spaces prefixing
the 'U'. On 64-bit architectures, 17 spaces prefixing the 'U'.
(Yes, even a cross-built binutils building for a 32-bit architecture
on a 64-bit architecture gives you 64-bit addresses.)
Does the format _really_ matter this much?
--
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-04-10 19:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-10 12:10 Russell King
2004-04-10 14:24 ` Sam Ravnborg
2004-04-10 14:35 ` Russell King
2004-04-10 17:28 ` Sam Ravnborg
2004-04-10 19:08 ` Russell King [this message]
2004-04-10 19:33 ` Brian Gerst
2004-04-10 20:19 ` 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=20040410200802.E4221@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.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®