From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1E0iA2-0005wH-O0 for qemu-devel@nongnu.org; Thu, 04 Aug 2005 12:01:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1E0i9z-0005tg-Jx for qemu-devel@nongnu.org; Thu, 04 Aug 2005 12:01:32 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E0i9x-0005pj-96 for qemu-devel@nongnu.org; Thu, 04 Aug 2005 12:01:29 -0400 Received: from [128.8.10.162] (helo=po0.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1E0iGk-0005bC-CF for qemu-devel@nongnu.org; Thu, 04 Aug 2005 12:08:30 -0400 Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.237.180]) by po0.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j74FtC6v026606 for ; Thu, 4 Aug 2005 11:55:12 -0400 (EDT) Date: Thu, 4 Aug 2005 11:55:10 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] qemu CVS not compilable Message-ID: <20050804155510.GA9111@jbrown.mylinuxbox.org> References: <200508041115.14591.heiko.nardmann@secunet.com> <200508041201.55288.heiko.nardmann@secunet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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.