From: "H. Peter Anvin" <hpa@zytor.com>
To: Vivek Goyal <vgoyal@redhat.com>, Thomas Glanzmann <thomas@glanzmann.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@amacapital.net>,
Baoquan He <bhe@redhat.com>, Borislav Petkov <bp@suse.de>,
Dave Young <dyoung@redhat.com>,
Eric Biederman <ebiederm@xmission.com>,
Greg Kroah-Hartman <greg@kroah.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
WANG Chao <chaowang@redhat.com>, Yinghai Lu <yinghai@kernel.org>,
ubuntu@iam.tj
Subject: Re: REGRESSION: 8fc5b4d: Unable to compile x86_64 kernel with x86_32 userland
Date: Wed, 20 Aug 2014 11:56:14 -0500 [thread overview]
Message-ID: <f7583da0-c49c-48d9-b69e-0257db583115@email.android.com> (raw)
In-Reply-To: <20140820154817.GA21518@redhat.com>
Yes, that is exactly right. The lack of -m64 is a bug.
On August 20, 2014 10:48:18 AM CDT, Vivek Goyal <vgoyal@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.
next prev parent reply other threads:[~2014-08-20 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 6:04 Regression: Can't compile x86_64 with 32 Bit userland: arch/x86/purgatory/purgatory.c:1:0: error: code model 'large' not supported in the 32 bit mode Thomas Glanzmann
2014-08-20 6:24 ` REGRESSION: 8fc5b4d: Unable to compile x86_64 kernel with x86_32 userland Thomas Glanzmann
2014-08-20 12:56 ` Vivek Goyal
2014-08-20 15:07 ` H. Peter Anvin
2014-08-20 15:48 ` Vivek Goyal
2014-08-20 16:21 ` Thomas Glanzmann
2014-08-20 16:56 ` H. Peter Anvin [this message]
2014-08-20 16:16 ` Thomas Glanzmann
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=f7583da0-c49c-48d9-b69e-0257db583115@email.android.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=bp@suse.de \
--cc=chaowang@redhat.com \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mjg59@srcf.ucam.org \
--cc=mtk.manpages@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=thomas@glanzmann.de \
--cc=torvalds@linux-foundation.org \
--cc=ubuntu@iam.tj \
--cc=vgoyal@redhat.com \
--cc=yinghai@kernel.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
Powered by JetHome