From: Takashi Iwai <tiwai@suse.de>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: alsa-driver, alsa-kernel cvs does not install now.
Date: Wed, 30 Jun 2004 11:08:22 +0200 [thread overview]
Message-ID: <s5hisd9begp.wl@alsa2.suse.de> (raw)
In-Reply-To: <40E1D6C7.2080104@superbug.demon.co.uk>
At Tue, 29 Jun 2004 21:53:27 +0100,
James Courtier-Dutton wrote:
>
> Can you maybe fix the problem below.
> I am using the latest alsa-driver and alsa-kernel cvs.
>
> I do make, and get
> ...
> *** Warning: "snd_compat_kcalloc"
> [/u/alsacvs/alsa-driver/kbuild/../acore/snd.ko] undefined!
> ...
Fixed now on cvs. The patch below was applied.
> Then later
>
> make install
> ....
> WARNING: Module /lib/modules/2.6.7/kernel/sound/acore/snd-pcm.ko
> ignored, due to loop
> WARNING: Loop detected: /lib/modules/2.6.7/kernel/sound/acore/snd.ko
> which needs snd.ko again!
> WARNING: Module /lib/modules/2.6.7/kernel/sound/acore/snd.ko ignored,
> due to loop
> ...
That I can't reproduce. Could you run make clean once, or build on
the fresh alsa-driver tree?
Takashi
--- alsa-driver/acore/misc.c 29 Jun 2004 15:58:54 -0000 1.24
+++ alsa-driver/acore/misc.c 30 Jun 2004 08:56:38 -0000
@@ -239,7 +239,7 @@
#endif
#ifndef CONFIG_HAVE_KCALLOC
-#ifdef CONFIG_SND_DEBUG_MEMORY
+#ifndef CONFIG_SND_DEBUG_MEMORY
/* Don't put this to wrappers.c. We need to call the kmalloc wrapper here. */
void *snd_compat_kcalloc(size_t n, size_t size, int flags)
{
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
prev parent reply other threads:[~2004-06-30 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 20:53 alsa-driver, alsa-kernel cvs does not install now James Courtier-Dutton
2004-06-30 9:08 ` Takashi Iwai [this message]
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=s5hisd9begp.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