From: "Nardmann, Heiko" <heiko.nardmann@secunet.com>
To: malc <malc@pulsesoft.com>
Cc: QEMU Development Mailing List <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu CVS not compilable
Date: Thu, 4 Aug 2005 12:01:44 +0200 [thread overview]
Message-ID: <200508041201.55288.heiko.nardmann@secunet.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0508041334450.902@home.oyster.ru>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
Am Donnerstag, 4. August 2005 11:38 schrieb malc:
> On Thu, 4 Aug 2005, Nardmann, Heiko wrote:
> > Problem:
> > the current CVS is not compilable with audio enabled.
> >
> > configure call:
> > ./configure --prefix=/opt/qemu-20050804 --enable-adlib --enable-fmod
>
> You can not build with FMOD unless you specify paths to FMODs include
> and library paths (--fmod-inc=... --fmod-lib=...)
Then configure is not doing its work correctly. It should check for fmod and
disable fmod support if it cannot be found or is missing functionality needed
for qemu.
FMOD is installed with prefix /usr/local at my site which normally is a
candidate for include/library files searching ...
>
> <snip>
>
> P.S. FMOD must be of version 3.xx. FMOD Ex (4.xx) was released 2 days ago
> and i have no idea weather it's ABI compatible with 3.xx.
--
Heiko Nardmann (Dipl.-Ing. Technische Informatik)
secunet Security Networks AG - Sicherheit in Netzwerken (www.secunet.de),
Weidenauer Str. 223-225, D-57076 Siegen
Tel. : +49 271 48950-13, Fax : +49 271 48950-50
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-04 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 9:15 [Qemu-devel] qemu CVS not compilable Nardmann, Heiko
2005-08-04 9:38 ` malc
2005-08-04 10:01 ` Nardmann, Heiko [this message]
2005-08-04 10:25 ` malc
2005-08-04 15:55 ` Jim C. Brown
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=200508041201.55288.heiko.nardmann@secunet.com \
--to=heiko.nardmann@secunet.com \
--cc=malc@pulsesoft.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).