From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Sam Ravnborg <sam@ravnborg.org>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: ARM undefined symbols. Again.
Date: Mon, 24 Jan 2005 15:43:26 +0000 [thread overview]
Message-ID: <20050124154326.A5541@flint.arm.linux.org.uk> (raw)
Sam,
Where did the hacks go which detect the silent failure of the ARM binutils?
I'm asking because I've just spent all of today trying to work out why
the hell code isn't working, only to find that it's all down to the
toolchain problem not being detected by kbuild. IOW, the code sequence:
mov r0, #CR1A_SMPE
where CR1A_SMPE is undefined, assembles to:
c001224c: e3a00000 mov r0, #0 ; 0x0
without any warnings or errors, and links a successful kernel, leaving
this in System.map:
U CR1A_SMPE
I absolutely must have the kernel build system detecting this binutils
problem when it occurs.
--
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 reply other threads:[~2005-01-24 15:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 15:43 Russell King [this message]
2005-01-31 16:17 ` ARM undefined symbols. Again Sam Ravnborg
2005-02-07 11:43 ` Russell King
2005-02-08 19:42 ` Sam Ravnborg
2005-02-08 20:05 ` Russell King
2005-02-09 10:40 ` Russell King
2005-02-13 17:29 ` Russell King
2005-02-14 13:10 ` Paulo Marques
2005-02-25 19:48 ` Russell King
2005-02-25 19:59 ` Linus Torvalds
2005-02-25 20:23 ` Russell King
2005-02-25 20:31 ` Linus Torvalds
2005-02-25 20:54 ` Paulo Marques
[not found] ` <20050225210254.GB15773@mars>
2005-02-25 21:18 ` Paulo Marques
[not found] ` <20050225222720.D27842@flint.arm.linux.org.uk>
2005-02-25 22:49 ` Linus Torvalds
2005-02-25 22:52 ` Linus Torvalds
2005-02-26 11:17 ` Russell King
2005-02-26 11:29 ` Russell King
2005-02-25 22:03 ` Daniel Jacobowitz
2005-02-08 20:09 ` Alex Muradin
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=20050124154326.A5541@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@osdl.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