Re: 2.6.8-rc2-mm1 link errors
From: Dave Hansen
Date: Wed Jul 28 2004 - 19:02:40 EST
On Wed, 2004-07-28 at 16:49, Andrew Morton wrote:
> Dave Hansen <haveblue@xxxxxxxxxx> wrote:
> >
> > I'm getting some odd link errors from -rc2-mm1 that don't happen in
> > -rc1-mm1, or plain -rc2:
> >
> > LD .tmp_vmlinux1
> > ldchk: .tmp_vmlinux1: final image has undefined symbols:
> >
> >
> > <bunch of blank lines>
> >
> >
> > make: *** [.tmp_vmlinux1] Error 1
> >
> > Any ideas?
>
> Nope. Could you take a look at the code in the top-level
> Makefile which is doing this, work out why it broke?
Well, it's this patch. cc'ing Russell...
I'd tend to think it's a false-positive, not a real problem that's just
being detected now. Is the sed part of the patch borked?
-----
From: Russell King <rmk+lkml@xxxxxxxxxxxxxxxx>
The only issue with this is that, when a problem is detected, the
reported symbols will also include the Sparc64 register symbols.
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
25-akpm/Makefile | 8 ++++++++
1 files changed, 8 insertions(+)
diff -puN Makefile~handle-undefined-symbols Makefile
--- 25/Makefile~handle-undefined-symbols 2004-07-26 23:24:30.552753872 -0700
+++ 25-akpm/Makefile 2004-07-26 23:24:30.556753264 -0700
@@ -525,6 +525,8 @@ endef
# set -e makes the rule exit immediately on error
+# Note: Ensure that there are no undefined symbols in the final
+# linked image. Not doing this can lead to silent link failures.
define rule_vmlinux__
+set -e; \
$(if $(filter .tmp_kallsyms%,$^),, \
@@ -536,6 +538,12 @@ define rule_vmlinux__
$(if $($(quiet)cmd_vmlinux__), \
echo ' $($(quiet)cmd_vmlinux__)' &&) \
$(cmd_vmlinux__); \
+ if $(OBJDUMP) --syms $@ | egrep -q '^([^R]|R[^E]|RE[^G])[^w]*\*UND\*'; then \
+ echo 'ldchk: $@: final image has undefined symbols:'; \
+ $(NM) $@ | sed 's/^ *U \(.*\)/ \1/p;d'; \
+ $(RM) -f $@; \
+ exit 1; \
+ fi; \
echo 'cmd_$@ := $(cmd_vmlinux__)' > $(@D)/.$(@F).cmd
endef
_
-- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/