From: Alexander Koch <efraim@clues.de>
To: linux-kernel@vger.kernel.org
Subject: sound, sb16, not compiling
Date: Fri, 28 Mar 2003 15:47:10 +0100 [thread overview]
Message-ID: <20030328144710.GA8522@shekinah.ip.tiscali.net> (raw)
Hiya.
I fail to get the SB16 module compiled, it does not like me.
This is 2.5.66, .65 does not work either.
Hope anyone can help as I miss it. ;-)
Thanks,
Alexander
[ make modules ]
make -f scripts/Makefile.build obj=sound/isa/opti9xx
make -f scripts/Makefile.build obj=sound/isa/sb
gcc -Wp,-MD,sound/isa/sb/.sb16.o.d -D__KERNEL__ -Iinclude
-Wall -Wstrict-prototypes -Wno-trigraphs -O2
-fno-strict-aliasing -fno-common -pipe
-mpreferred-stack-boundary=2 -march=pentium3
-Iinclude/asm-i386/mach-default -fomit-frame-pointer
-nostdinc -iwithprefix include -DMODULE
-DKBUILD_BASENAME=sb16 -DKBUILD_MODNAME=snd_sb16 -c -o
sound/isa/sb/sb16.o sound/isa/sb/sb16.c
sound/isa/sb/sb16.c: In function `snd_sb16_isapnp':
sound/isa/sb/sb16.c:279: warning: implicit declaration of
function `isapnp_find_dev'
sound/isa/sb/sb16.c:279: warning: assignment makes pointer
from integer without a cast
sound/isa/sb/sb16.c:280: structure has no member named `active'
sound/isa/sb/sb16.c:293: structure has no member named `prepare'
sound/isa/sb/sb16.c:296: warning: implicit declaration of
function `isapnp_resource_change'
sound/isa/sb/sb16.c:307: structure has no member named `activate'
sound/isa/sb/sb16.c: In function `snd_sb16_deactivate':
sound/isa/sb/sb16.c:347: structure has no member named `deactivate'
sound/isa/sb/sb16.c: In function `alsa_card_sb16_init':
sound/isa/sb/sb16.c:632: warning: implicit declaration of function `isapnp_probe_cards'
make[3]: *** [sound/isa/sb/sb16.o] Error 1
make[2]: *** [sound/isa/sb] Error 2
make[1]: *** [sound/isa] Error 2
make: *** [sound] Error 2
next reply other threads:[~2003-03-28 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 14:47 Alexander Koch [this message]
2003-03-28 15:01 ` Zwane Mwaikambo
2003-04-02 18:30 ` Alexander Koch
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=20030328144710.GA8522@shekinah.ip.tiscali.net \
--to=efraim@clues.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®