From: Takashi Iwai <tiwai@suse.de>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Trying to get alsa-driver to build on a 2.6.x kernel.
Date: Fri, 30 Jan 2004 16:02:50 +0100 [thread overview]
Message-ID: <s5h4qudscmd.wl@alsa2.suse.de> (raw)
In-Reply-To: <401A6E54.5010605@superbug.demon.co.uk>
[-- Attachment #1: Type: text/plain, Size: 285 bytes --]
At Fri, 30 Jan 2004 14:46:44 +0000,
James Courtier-Dutton wrote:
>
> configure:2962: gcc -o conftest -g -O2 -I/lib/modules/2.6.2-rc2/build/include -I$(CONFIG_SND_KERNELDIR)/include/asm-i386/mach-default conftest.c 1>&5
doh... my bad.
try the attached additional patch.
Takashi
[-- Attachment #2: kinc-fix.dif --]
[-- Type: application/octet-stream, Size: 638 bytes --]
Index: alsa-driver/configure.in
===================================================================
RCS file: /suse/tiwai/cvs/alsa/alsa-driver/configure.in,v
retrieving revision 1.157
diff -u -r1.157 configure.in
--- alsa-driver/configure.in 30 Jan 2004 11:28:57 -0000 1.157
+++ alsa-driver/configure.in 30 Jan 2004 15:01:10 -0000
@@ -887,7 +887,7 @@
machine=`cat machine.id`;AC_MSG_RESULT($machine))
CFLAGS="$ac_save_CFLAGS"
rm -f machine.id
- KERNEL_INC="$KERNEL_INC -I\$(CONFIG_SND_KERNELDIR)/include/asm-i386/mach-$machine"
+ KERNEL_INC="$KERNEL_INC -I$CONFIG_SND_KERNELDIR/include/asm-i386/mach-$machine"
fi
;;
esac
next prev parent reply other threads:[~2004-01-30 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 19:49 Trying to get alsa-driver to build on a 2.6.x kernel James Courtier-Dutton
2004-01-30 11:05 ` Takashi Iwai
2004-01-30 14:04 ` James Courtier-Dutton
2004-01-30 14:13 ` Takashi Iwai
2004-01-30 14:46 ` James Courtier-Dutton
2004-01-30 15:02 ` Takashi Iwai [this message]
2004-01-30 15:50 ` James Courtier-Dutton
2004-01-30 14:48 ` James Courtier-Dutton
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=s5h4qudscmd.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=James@superbug.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
/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