From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu CVS not compilable
Date: Thu, 4 Aug 2005 11:55:10 -0400 [thread overview]
Message-ID: <20050804155510.GA9111@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0508041420300.1059@home.oyster.ru>
On Thu, Aug 04, 2005 at 02:25:05PM +0400, malc_ wrote:
> Since there is no default way to install FMOD on *nixes there is no
> default way to check for it's presence either.
Sounds like configure should be cowardly aborting if one attempts to enable
fmod without specifying the path to the include files or the librarys.
An error message of "FMOD library/include path not specified" should be enough.
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
prev parent reply other threads:[~2005-08-04 16:01 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
2005-08-04 10:25 ` malc
2005-08-04 15:55 ` Jim C. Brown [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=20050804155510.GA9111@jbrown.mylinuxbox.org \
--to=jma5@umd.edu \
--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).