From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43437) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XtJGv-0005uk-MT for qemu-devel@nongnu.org; Tue, 25 Nov 2014 11:47:31 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XtJGm-0002sk-7A for qemu-devel@nongnu.org; Tue, 25 Nov 2014 11:47:25 -0500 Received: from mx1.redhat.com ([209.132.183.28]:55696) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XtJGm-0002sG-0Q for qemu-devel@nongnu.org; Tue, 25 Nov 2014 11:47:16 -0500 Message-ID: <5474B28C.6080205@redhat.com> Date: Tue, 25 Nov 2014 11:47:08 -0500 From: John Snow MIME-Version: 1.0 References: <6c538796.a24d.149dfb4389a.Coremail.lijiamin036@163.com> In-Reply-To: <6c538796.a24d.149dfb4389a.Coremail.lijiamin036@163.com> Content-Type: text/plain; charset=gbk; format=flowed Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] configure options of qemu List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: li , qemu-devel@nongnu.org On 11/23/2014 09:49 PM, li wrote: > Hi all, > Thank you for your time to read this email, is there anyone can tell me > the options qemu was configured when it was released? > I configured it by myself and found that there was a audio latency > problem, but the qemu in the repository doesn't have this problem, > so i want to kown about its configuration options. > the options i using is as below: > ./configure --enable-spice --enable-usb-redir --enable-kvm > --disable-werror --prefix=3D/home/stone/qemu --target-list=3Dx86_64-sof= tmmu > --audio-card-list=3Dac97,es1370,sb16,cs4231a,adlib,gus,hda,ich6 > --audio-drv-list=3Dpa,alsa,sdl,oss > Best Regards > stone > "The repository" -- whose? We don't dictate the configuration options=20 that the various distributions decide to package with. You'd have to ask=20 your distribution (Ubuntu? Debian? Fedora? CentOS?) what options they=20 packaged with. Before you jump down that rabbit hole, though, try comparing the=20 versions you're using. It might just be a version difference. It would=20 be worth trying to configure the upstream sources that match the version=20 your distribution ships and seeing if you have the same problem to=20 determine if it's a bug or a configuration problem. --=20 =A1=AAjs