qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bernhard Fischer <rep.nop@aon.at>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [patch] add configure check for working alsa
Date: Thu, 4 Jan 2007 16:02:59 +0100	[thread overview]
Message-ID: <20070104150259.GE28746@aon.at> (raw)

[-- Attachment #1: Type: text/plain, Size: 364 bytes --]

Hi,

This patchlet adds a check to configure that makes sure that we have a
working alsa setup.

Previously, if --enable-alsa was given but the user forgot to install
the alsa libs proper, the build failed later on due to eventually
missing libs. The patch makes sure that the user can spot that alsa
support was turned off after configuration completed.

thanks,

[-- Attachment #2: qemu.cvs-20070104.add-alsa-config-check.diff --]
[-- Type: text/x-diff, Size: 725 bytes --]

diff --exclude='*.diff' -rduNp ../qemu_trunk.orig/configure ./configure
--- ../qemu_trunk.orig/configure	2007-01-04 14:38:58.000000000 +0100
+++ ./configure	2007-01-04 14:48:14.000000000 +0100
@@ -509,6 +509,17 @@ fi # sdl compile test
 fi # cross compilation
 fi # -z $sdl
 
+##########################################
+# sound support libraries
+# alsa
+if test "$alsa" = "yes" ; then
+  cat > $TMPC << EOF
+#include <alsa/asoundlib.h>
+int main(void) { snd_pcm_t **handle; return snd_pcm_close(*handle); }
+EOF
+  $cc -o $TMPE $TMPC -lasound 2> /dev/null || alsa="no"
+fi # alsa
+
 # Check if tools are available to build documentation.
 if [ -x "`which texi2html`" ] && [ -x "`which pod2man`" ]; then
   build_docs="yes"

             reply	other threads:[~2007-01-04 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 15:02 Bernhard Fischer [this message]
2007-01-04 19:21 ` [Qemu-devel] [patch] add configure check for working alsa Paul Brook
2007-01-04 19:47   ` Bernhard Fischer

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=20070104150259.GE28746@aon.at \
    --to=rep.nop@aon.at \
    --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).