From: Carlo Marcelo Arenas Belon <carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [RFC] passthrough for configure options to qemu
Date: Mon, 22 Oct 2007 18:49:05 -0500 [thread overview]
Message-ID: <20071022234905.GA28523@tapir> (raw)
In-Reply-To: <471CFF3C.10500-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
On Mon, Oct 22, 2007 at 09:51:24PM +0200, Avi Kivity wrote:
> Carlo Marcelo Arenas Belon wrote:
> > On Sun, Oct 21, 2007 at 01:25:34PM +0200, Avi Kivity wrote:
> >>>
> >> Is it possible in case of a failure due to an unrecognized option to
> >> call out usage() instead of qemu's?
> >
> > not sure what you mean, but qemu's configure ignores any unrecognized options
> > so it won't fail.
> >
>
> That's a bug. I'm sure qemu-devel would appreciate a patch.
I think that was a feature instead, considering that there is almost no
implementation for reinforcing the defaults and so --disable-alsa (as an
example) will fail as an unknown option.
nevertheless will try to upstream the changes required
Carlo
-------------------------------------------------------------------------
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-22 23:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 15:19 [RFC] passthrough for configure options to qemu Carlo Marcelo Arenas Belon
2007-10-21 11:25 ` Avi Kivity
[not found] ` <471B372E.2080807-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-22 18:58 ` Carlo Marcelo Arenas Belon
2007-10-22 19:51 ` Avi Kivity
[not found] ` <471CFF3C.10500-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-22 23:49 ` Carlo Marcelo Arenas Belon [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=20071022234905.GA28523@tapir \
--to=carenas-kledwsohozojb6fo7hg9ng@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@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 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.