From: Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe>
To: TJ <linux@tjworld.net>
Cc: kvm@vger.kernel.org
Subject: Re: kvm72: configure script mangles --audio-drv-list and --audio-card-list and blocks them from --help
Date: Wed, 30 Jul 2008 12:37:49 -0500 [thread overview]
Message-ID: <20080730173749.GA10849@tapir> (raw)
In-Reply-To: <1217416390.2598.11.camel@hephaestion.lan.tjworld.net>
On Wed, Jul 30, 2008 at 12:13:10PM +0100, TJ wrote:
> The ./configure script, whilst trying to be clever in passing options to
> qemu/configure, mangles the --audio-*-list options. It also prevents the
> audio-*-list options showing up as a result of --help.
this sounds like the problem that was introduced with the qemu merge for
kvm-71; the following patch series addresses it :
http://www.mail-archive.com/kvm@vger.kernel.org/msg01763.html
they should also apply to kvm-72 cleanly, but will try to rebase them and
resend them later so they have a better chance of getting merged.
Carlo
prev parent reply other threads:[~2008-07-30 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 11:13 kvm72: configure script mangles --audio-drv-list and --audio-card-list and blocks them from --help TJ
2008-07-30 17:37 ` 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=20080730173749.GA10849@tapir \
--to=carenas@sajinet.com.pe \
--cc=kvm@vger.kernel.org \
--cc=linux@tjworld.net \
/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