From: Lee Revell <rlrevell@joe-job.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: i386 -> x86_64 cross compile failure (binutils bug?)
Date: Sat, 10 Dec 2005 00:12:03 -0500 [thread overview]
Message-ID: <1134191524.18432.82.camel@mindpipe> (raw)
In-Reply-To: <p73oe3ppbxj.fsf@verdi.suse.de>
On Sat, 2005-12-10 at 01:56 -0700, Andi Kleen wrote:
> Lee Revell <rlrevell@joe-job.com> writes:
> > - disable CONFIG_IA32_EMULATION
>
> I just tried it here. Adding -m64 to CFLAGS/AFLAGS on a native
> 64bit biarch toolchain and it compiled without problems. It ends
> up with -m64 -m32 for the 32bit vsyscall files, but that seems
> to DTRT at least in gcc 4.
Nope, passing -m64 -m32 does not seem to DTRT on native 32bit biarch
toolchain:
make -f scripts/Makefile.build obj=arch/x86_64/ia32
gcc -Wp,-MD,arch/x86_64/ia32/.vsyscall-sysenter.o.d -nostdinc
-isystem /usr/lib/gcc/i486-linux-gnu/4.0.2/include -D__KERNEL__
-Iinclude -D__ASSEMBLY__ -m64 -m32 -c -o
arch/x86_64/ia32/vsyscall-sysenter.o
arch/x86_64/ia32/vsyscall-sysenter.S
arch/x86_64/ia32/vsyscall-sysenter.S: Assembler messages:
arch/x86_64/ia32/vsyscall-sysenter.S:14: Error: suffix or operands
invalid for `push'
etc
That command succeeds if I run it by hand only passing -m32.
Lee
next prev parent reply other threads:[~2005-12-10 5:10 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 18:50 i386 -> x86_64 cross compile failure (binutils bug?) Lee Revell
2005-12-09 19:50 ` Ken Moffat
2005-12-09 19:59 ` Lee Revell
2005-12-09 21:30 ` Ken Moffat
2005-12-09 21:40 ` Lee Revell
2005-12-09 22:19 ` Ken Moffat
2005-12-09 19:58 ` Kyle McMartin
2005-12-09 20:21 ` Lee Revell
2005-12-09 20:41 ` Kyle McMartin
2005-12-09 20:58 ` Lee Revell
2005-12-09 21:25 ` Steven Rostedt
2005-12-09 21:35 ` Lee Revell
2005-12-09 21:10 ` Lee Revell
2005-12-09 21:19 ` Kyle McMartin
2005-12-09 22:37 ` Jeffrey Hundstad
2005-12-10 0:05 ` Lee Revell
2005-12-10 0:23 ` Jeffrey Hundstad
2005-12-10 1:28 ` Lee Revell
2005-12-10 1:50 ` Lee Revell
2005-12-10 8:56 ` Andi Kleen
2005-12-10 5:12 ` Lee Revell [this message]
2005-12-10 7:19 ` Andi Kleen
2005-12-10 7:43 ` Lee Revell
2005-12-10 19:34 ` Lee Revell
2005-12-11 0:00 ` Andi Kleen
2005-12-11 0:26 ` Lee Revell
2005-12-16 23:40 ` Lee Revell
2005-12-23 5:59 ` Lee Revell
2006-01-11 16:48 ` Lee Revell
2006-01-11 16:54 ` Andi Kleen
2005-12-09 22:43 ` Xavier Bestel
2005-12-10 1:31 ` Lee Revell
2005-12-10 20:34 ` Xavier Bestel
2005-12-10 20:48 ` Lee Revell
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=1134191524.18432.82.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.