Messages in this thread | | | Date | Sat, 10 Apr 2004 20:08:02 +0100 | From | Russell King <> | Subject | Re: [RFC] Force build error on undefined symbols |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |