Yes, that is exactly right. The lack of -m64 is a bug. On August 20, 2014 10:48:18 AM CDT, Vivek Goyal <vgo...@redhat.com> wrote: >On Wed, Aug 20, 2014 at 10:07:01AM -0500, H. Peter Anvin wrote: >> It says "32-bit mode" which means it is another issue: we are >dropping -m64 at some point. > >Thanks hpa. I am not adding -m64 to kbuild flags at all. So 32bit tool >chain must be assuming -m32 by default, and probably that's the issue. > >Thomas, > >Can you please try attached single line patch and see if it fixes the >issue for you. > >Thanks >Vivek > > >--- > arch/x86/purgatory/Makefile | 1 + > 1 file changed, 1 insertion(+) > >Index: linux-2.6/arch/x86/purgatory/Makefile >=================================================================== >--- linux-2.6.orig/arch/x86/purgatory/Makefile 2014-08-20 >11:32:21.723559119 -0400 >+++ linux-2.6/arch/x86/purgatory/Makefile 2014-08-20 11:32:23.654570231 >-0400 >@@ -11,6 +11,7 @@ targets += purgatory.ro > # sure how to relocate those. Like kexec-tools, use custom flags. > >KBUILD_CFLAGS := -fno-strict-aliasing -Wall -Wstrict-prototypes >-fno-zero-initialized-in-bss -fno-builtin -ffreestanding -c -MD -Os >-mcmodel=large >+KBUILD_CFLAGS += -m$(BITS) > > $(obj)/purgatory.ro: $(PURGATORY_OBJS) FORCE > $(call if_changed,ld)
-- Sent from my mobile phone. Please pardon brevity and lack of formatting. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
