From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Carlo Marcelo Arenas Belon
<carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [RFC v3] passthrough for configure options to qemu
Date: Thu, 25 Oct 2007 20:38:32 +0200 [thread overview]
Message-ID: <4720E2A8.7020107@qumranet.com> (raw)
In-Reply-To: <20071023000749.GB28523@tapir>
Carlo Marcelo Arenas Belon wrote:
> The following patch implement a configure passthrough for qemu and
> migrate all currently implemented qemu specific configuration flags
> (enable-alsa, disable-vnc-tls and disable-gcc-check) to use it.
>
> It uses qemu's configure to get a list of hints for additional options to
> use and to keep backward compatible descriptions of the options that can
> be used, but adding disable-gcc-check statically so it is clear what the
> impact of overriding the use of gcc4 is.
>
> Qemu's configure has been enhanced to protect against the use of invalid
> options as well as reconfigured to stderr for fatal errors so they can be
> integrated into kvm's configure.
>
>
I'd like to see qemu-devel accept the qemu changes first.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
prev parent reply other threads:[~2007-10-25 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 0:07 [RFC v3] passthrough for configure options to qemu Carlo Marcelo Arenas Belon
2007-10-25 18:38 ` 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=4720E2A8.7020107@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=carenas-kLeDWSohozoJb6fo7hG9ng@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