On Wed, 19 Nov 2008, Andrew Morton wrote: > > arch/ia64/kernel/built-in.o(.text+0x4a22): In function `efi_initialize_iomem_resources': > : undefined reference to `__ia64_save_stack_nonlocal' > arch/ia64/kernel/built-in.o(.text+0x16262): In function `pfm_context_create': > : undefined reference to `__ia64_save_stack_nonlocal' > arch/ia64/kernel/built-in.o(.text+0x238a2): In function `sys_perfmonctl': > : undefined reference to `__ia64_save_stack_nonlocal' > arch/ia64/kernel/built-in.o(.text+0x466c2): In function `dup_state_stack': > : undefined reference to `__ia64_save_stack_nonlocal' > arch/ia64/kernel/built-in.o(.text+0x46cf2): In function `desc_prologue': > : undefined reference to `__ia64_save_stack_nonlocal' > arch/ia64/kernel/built-in.o(.text+0x49752): more undefined references to `__ia64_save_stack_nonlocal' follow > > Whatever caused this is fairly well hidden from `grep'.. > That looks like some builtin function that gcc might add. I've seen other types of references before like that on x86. Can't remember what it was exactly, but it hit me when I had two slightly different compilers in my distcc farm. /me goes looks at his http://rostedt.homelinux.com/distcc/ page. Ah, here it is... Found that -fstack-protect-all set will cause the cross compiler to create "stack_chk_guard" calls. These are not defined in the kernel and cause linking problems. Not sure if __ia64_save_stack_nonlocal is equivalent, but perhaps it is related. Maybe some CFLAG was set that caused an issue? -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|