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] passthrough for configure options to qemu
Date: Sun, 21 Oct 2007 13:25:34 +0200 [thread overview]
Message-ID: <471B372E.2080807@qumranet.com> (raw)
In-Reply-To: <20071019151940.GB15533@tapir>
Carlo Marcelo Arenas Belon wrote:
> The following patch Implement a configure passthrough for qemu and
> migrate all current qemu specific configuration flags (enable-alsa,
> disable-vnc-tls and disable-gcc-check) to use it.
>
> It leaves a description of the current flags (as used in kvm's configure)
> as a reference but I'm not sure if that is the right approach since the
> wording with the corresponding qemu flags is different and the list is
> obviously never going to be all inclusive.
> @@ -26,8 +24,10 @@ usage() {
> --qemu-cc=CC specify compiler for qemu (must be gcc-3.x)
> --qemu-cflags=CFLAGS CFLAGS to add to qemu configuration
> --qemu-ldflags=LDFLAGS LDFLAGS to add to qemu configuration
> - --enable-alsa enable alsa support for qemu
> - --disable-vnc-tls disable vnc tls support for qemu
> +
> + Any additional option is given to qemu's configure verbatim, including:
> + --enable-alsa enable alsa support
> + --disable-vnc-tls disable vnc tls support
> --disable-gcc-check don't insist on gcc-3.x
> CAUTION: this will break running without kvm
>
Why not call qemu's ./configure to get the help text?
> @@ -111,13 +102,10 @@ fi
> --disable-kqemu --extra-cflags="-I $PWD/../user $qemu_cflags" \
> --extra-ldflags="-L $PWD/../user $qemu_ldflags" \
> --enable-kvm --kernel-path="$libkvm_kerneldir" \
> - ${enable_alsa:+"--enable-alsa"} \
> - ${disable_vnc_tls:+"--disable-vnc-tls"} \
> - ${disable_gcc_check:+"--disable-gcc-check"} \
> --prefix="$prefix" \
> ${qemu_cc:+"--cc=$qemu_cc"} \
> ${cross_prefix:+"--cross-prefix=$cross_prefix"} \
> - ${cross_prefix:+"--cpu=$arch"}
> + ${cross_prefix:+"--cpu=$arch"} $qemu_conf
> )
>
Is it possible in case of a failure due to an unrecognized option to
call out usage() instead of qemu's?
--
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/
next prev parent reply other threads:[~2007-10-21 11:25 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 [this message]
[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
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=471B372E.2080807@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 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.