From: Avi Kivity <avi@redhat.com>
To: Farkas Levente <lfarkas@lfarkas.org>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: [ANNOUNCE] qemu-kvm-0.10.6
Date: Sun, 02 Aug 2009 17:06:15 +0300 [thread overview]
Message-ID: <4A759D57.8000806@redhat.com> (raw)
In-Reply-To: <4A759A4E.4070509@lfarkas.org>
On 08/02/2009 04:53 PM, Farkas Levente wrote:
> On 08/02/2009 01:40 PM, Avi Kivity wrote:
>> qemu-kvm-0.10.6 is now available. This is the third release of the 0.10
>> stable branch of qemu-kvm. qemu-kvm 0.10.6 includes all of the
>> features and fixes of qemu-0.10.6, plus adaptations for improved kvm
>> support.
>
> not build under rhel/centos-5:
> ----------------------------------------------------
> gcc -I. -I.. -I/home/robot/rpm/BUILD/qemu-kvm-0.10.6/target-i386
> -I/home/robot/rpm/BUILD/qemu-kvm-0.10.6 -MMD -MT op_helper.o -MP
> -DNEED_CPU_H -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
> -D__user= -I/home/robot/rpm/BUILD/qemu-kvm-0.10.6/tcg
> -I/home/robot/rpm/BUILD/qemu-kvm-0.10.6/tcg/x86_64
> -I/home/robot/rpm/BUILD/qemu-kvm-0.10.6/fpu -DHAS_AUDIO
> -DHAS_AUDIO_CHOICE -I/home/robot/rpm/BUILD/qemu-kvm-0.10.6/slirp -O2
> -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
> --param=ssp-buffer-size=4 -m64 -mtune=generic -O2 -g
> -fno-strict-aliasing -Wall -Wundef -Wendif-labels -Wwrite-strings
> -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls
> -I/home/robot/rpm/BUILD/qemu-kvm-0.10.6/kvm/libkvm -m64
> -I/home/robot/rpm/BUILD/qemu-kvm-0.10.6/kvm/kernel/include
> -I/home/robot/rpm/BUILD/qemu-kvm-0.10.6/kvm/kernel/arch/x86/include
> -c -o op_helper.o
> /home/robot/rpm/BUILD/qemu-kvm-0.10.6/target-i386/op_helper.c
> {standard input}: Assembler messages:
> {standard input}:20758: Warning: end of file not at end of a line;
> newline inserted
> {standard input}:20994: Error: unknown pseudo-op: `.lbe35'
> gcc: Internal error: Killed (program cc1)
That file (or indeed, tcg) has not changed since qemu-kvm-0.10.5. Does
qemu-kvm-0.10.5 build on the same host with the same compiler?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-08-02 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 11:40 [ANNOUNCE] qemu-kvm-0.10.6 Avi Kivity
2009-08-02 13:53 ` Farkas Levente
2009-08-02 14:06 ` Avi Kivity [this message]
2009-08-02 14:21 ` Farkas Levente
2009-08-02 14:27 ` Farkas Levente
2009-08-02 14:43 ` Avi Kivity
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=4A759D57.8000806@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lfarkas@lfarkas.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