From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: BELLEGUEULLE Damien
<d.bellegueulle-B2DOHLE+as5GWvitb5QawA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: KVM-18 Error compilation
Date: Mon, 26 Mar 2007 12:39:37 +0200 [thread overview]
Message-ID: <4607A2E9.2090009@qumranet.com> (raw)
In-Reply-To: <92F16D7652AAF942ACB0578F53E32DE513A942-dK0XnR4e6A3jFbd8tFByRv4CVqVLow9K@public.gmane.org>
BELLEGUEULLE Damien wrote:
>
> ./configure --prefix=/usr --qemu-cc="/usr/bin/gcc-3.3.6"
>
> er -I. -I.. -I/home/bellegueulle/kvm-18/qemu/target-i386
> -I/home/bellegueulle/kvm-18/qemu -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
> -D_LARGEFILE_SOURCE -D__user= -I/home/bellegueulle/kvm-18/qemu/fpu
> -DHAS_AUDIO -I/home/bellegueulle/kvm-18/qemu/slirp -c -o qemu-kvm.o
>
This is on i386, right?
The command line needs to have -fomit-frame-pointer. The 'er' at the
beginning seems to indicate that this is so, can you confirm?
FWIW, i386 builds ok here with gcc 3.4.6.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2007-03-26 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 10:03 KVM-18 Error compilation BELLEGUEULLE Damien
[not found] ` <92F16D7652AAF942ACB0578F53E32DE513A942-dK0XnR4e6A3jFbd8tFByRv4CVqVLow9K@public.gmane.org>
2007-03-26 10:39 ` Avi Kivity [this message]
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=4607A2E9.2090009@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=d.bellegueulle-B2DOHLE+as5GWvitb5QawA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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