From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jeffrey Merkey <jeffmerkey@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.28.10 and Linux 2.6.29.6 XEN Guest Support Broken x86_64 in BUILD
Date: Thu, 15 Jul 2010 14:17:06 -0700 [thread overview]
Message-ID: <4C3F7AD2.8050908@goop.org> (raw)
In-Reply-To: <AANLkTim2dCrCisUmunVsUoP3uSvYDvRvNPUD0eNFxPwj@mail.gmail.com>
On 07/14/2010 04:33 PM, Jeffrey Merkey wrote:
> [root@cloudstream linux-2.6.29.6]#
> [root@cloudstream linux-2.6.29.6]#
> [root@cloudstream linux-2.6.29.6]#
> [root@cloudstream linux-2.6.29.6]# make bzImage modules modules_install install
> CHK include/linux/version.h
> CHK include/linux/utsrelease.h
> SYMLINK include/asm -> include/asm-x86
> CALL scripts/checksyscalls.sh
> CHK include/linux/compile.h
> AS arch/x86/xen/xen-asm_64.o
> arch/x86/xen/xen-asm_64.S: Assembler messages:
> arch/x86/xen/xen-asm_64.S:48: Error: suffix or operands invalid for `mov'
> arch/x86/xen/xen-asm_64.S:55: Error: suffix or operands invalid for `test'
> arch/x86/xen/xen-asm_64.S:72: Error: suffix or operands invalid for `mov'
> arch/x86/xen/xen-asm_64.S:90: Error: suffix or operands invalid for `test'
> arch/x86/xen/xen-asm_64.S:110: Error: suffix or operands invalid for `setz'
> arch/x86/xen/xen-asm_64.S:116: Error: suffix or operands invalid for `cmp'
> make[1]: *** [arch/x86/xen/xen-asm_64.o] Error 1
> make: *** [arch/x86/xen] Error 2
> [root@cloudstream linux-2.6.29.6]#
>
Do you have a particular reason to be using those kernels? They're very
old.
J
next prev parent reply other threads:[~2010-07-15 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 23:33 Jeffrey Merkey
2010-07-15 21:17 ` Jeremy Fitzhardinge [this message]
2010-07-16 4:27 ` Jeffrey Merkey
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=4C3F7AD2.8050908@goop.org \
--to=jeremy@goop.org \
--cc=jeffmerkey@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome