From: Stas Sergeev <stsp@aknet.ru>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA devel <alsa-devel@alsa-project.org>
Subject: Re: namehint: Evaluate more possibilities for hw devices
Date: Fri, 01 Oct 2010 18:05:06 +0400 [thread overview]
Message-ID: <4CA5EA92.1050102@aknet.ru> (raw)
In-Reply-To: <alpine.LNX.2.00.1010011512520.20467@eeebox2.perex-int.cz>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
01.10.2010 17:14, Jaroslav Kysela wrote:
> Try upgrade alsa-utils (aplay). Appearenly, the bug is there (at least
> on my system the latest aplay lists devices correctly, but aplay
> 1.0.18 is buggy).
Many thanks, now it works!
One thing to note is that previously
also VirMIDI device was listed, and not
any more. But I guess this is intentional,
as it is not a PCM device.
I needed the attached patch to compile
alsa-utils. I am cross-compiling, and without
this change, the configure would pick up
the host's ncurses-config.
Thanks for your help.
[-- Attachment #2: a.diff --]
[-- Type: text/plain, Size: 1315 bytes --]
diff --git a/configure.in b/configure.in
index 8bae007..2f47ef6 100644
--- a/configure.in
+++ b/configure.in
@@ -108,7 +108,8 @@ if test x$alsamixer = xtrue; then
CURSESLIBDIR=""
NCURSESLIBSUFFIX=""
CURSES_NLS="no"
- if test "$curseslib" = "ncursesw" -o \( "$curseslib" = "auto" -a "$USE_NLS" = "yes" \); then
+ if test "$cross_compiling" != "yes"; then
+ if test "$curseslib" = "ncursesw" -o \( "$curseslib" = "auto" -a "$USE_NLS" = "yes" \); then
AC_CHECK_PROG([ncursesw5_config], [ncursesw5-config], [yes])
if test "$ncursesw5_config" = "yes"; then
CURSESINC="<ncurses.h>"
@@ -124,8 +125,8 @@ if test x$alsamixer = xtrue; then
NCURSESLIBSUFFIX="w"
CURSES_NLS="yes"
fi
- fi
- if test "$curseslib" = "ncurses" -o "$curseslib" = "auto"; then
+ fi
+ if test "$curseslib" = "ncurses" -o "$curseslib" = "auto"; then
AC_CHECK_PROG([ncurses5_config], [ncurses5-config], [yes])
if test "$ncurses5_config" = "yes"; then
CURSESINC="<ncurses.h>"
@@ -137,6 +138,7 @@ if test x$alsamixer = xtrue; then
AC_CHECK_LIB(ncurses, initscr,
[ CURSESINC='<ncurses.h>'; CURSESLIB='-lncurses'; curseslib="ncurses"])
fi
+ fi
fi
if test "$curseslib" = "curses" -o "$curseslib" = "auto"; then
AC_CHECK_LIB(curses, initscr,
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2010-10-01 14:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 16:11 namehint: Evaluate more possibilities for hw devices Stas Sergeev
2010-10-01 9:08 ` Raymond Yau
2010-10-01 11:32 ` Jaroslav Kysela
2010-10-01 11:50 ` Stas Sergeev
2010-10-01 12:08 ` Jaroslav Kysela
2010-10-01 12:26 ` Stas Sergeev
2010-10-01 13:14 ` Jaroslav Kysela
2010-10-01 14:05 ` Stas Sergeev [this message]
2010-10-01 14:53 ` Stas Sergeev
2010-10-01 15:04 ` Jaroslav Kysela
2010-10-01 15:21 ` Stas Sergeev
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=4CA5EA92.1050102@aknet.ru \
--to=stsp@aknet.ru \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.