From: Miles Lane <miles@megapathdsl.net>
To: Jaroslav Kysela <perex@suse.cz>,
ALSA development <alsa-devel@alsa-project.org>
Subject: Build failure in cvs HEAD alsa-tools with kernel 2.5.5-pre1.
Date: Tue, 19 Feb 2002 00:38:03 -0800 [thread overview]
Message-ID: <3C720EEB.30902@megapathdsl.net> (raw)
Hi Jaroslav,
I got alsa-lib and alsa-utils to build fine using the new
--with-kernel=2.5.5-pre1 flag. But, I got the following build
failure with alsa-tools:
make[2]: Entering directory `/usr/src/alsa-tools/seq/sbiload'
gcc -DPACKAGE=\"sbiload\" -DVERSION=\"0.3.0\" -DSTDC_HEADERS=1
-DHAVE_LIBASOUND=1 -I. -I. -Wall -g -c sbiload.c
sbiload.c:23:29: sound/ainstr_fm.h: No such file or directory
make[2]: *** [sbiload.o] Error 1
make[2]: Leaving directory `/usr/src/alsa-tools/seq/sbiload'
make[2]: Entering directory `/usr/src/alsa-tools/seq/sbiload'
gcc -DPACKAGE=\"sbiload\" -DVERSION=\"0.3.0\" -DSTDC_HEADERS=1
-DHAVE_LIBASOUND=1 -I. -I. -Wall -g -c sbiload.c
sbiload.c:23:29: sound/ainstr_fm.h: No such file or directory
make[2]: *** [sbiload.o] Error 1
make[2]: Leaving directory `/usr/src/alsa-tools/seq/sbiload'
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
reply other threads:[~2002-02-19 8:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3C720EEB.30902@megapathdsl.net \
--to=miles@megapathdsl.net \
--cc=alsa-devel@alsa-project.org \
--cc=perex@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox