From: Ed Tomlinson <tomlins@cam.org>
To: linux-kernel@vger.kernel.org
Subject: [BUG] cs46xx compile error 2.5.47
Date: Mon, 11 Nov 2002 17:40:18 -0500 [thread overview]
Message-ID: <200211111740.18312.tomlins@cam.org> (raw)
Hi,
I get this compiling 2.5.47
gcc -Wp,-MD,sound/pci/cs46xx/.cs46xx_lib.o.d -D__KERNEL__ -Iinclude -Wall
-Wstrict-prototypes -Wrigraphs -O2 -fno-strict-aliasing -fno-common -pipe
-mpreferred-stack-boundary=2 -march=k6 -Iarch//mach-generic -fomit-frame-pointer
-nostdinc -iwithprefix include -DMODULE -include include/linux/ersions.h
-DKBUILD_BASENAME=cs46xx_lib -c -o sound/pci/cs46xx/cs46xx_lib.o sound/pci/cs46xx/cs_lib.c
sound/pci/cs46xx/cs46xx_lib.c: In function `_cs46xx_adjust_sample_rate':
sound/pci/cs46xx/cs46xx_lib.c:1054: structure has no member named `spos_mutex'
sound/pci/cs46xx/cs46xx_lib.c: In function `snd_cs46xx_playback_hw_params':
sound/pci/cs46xx/cs46xx_lib.c:1071: warning: unused variable `chip'
sound/pci/cs46xx/cs46xx_lib.c:1072: warning: unused variable `sample_rate'
sound/pci/cs46xx/cs46xx_lib.c:1073: warning: unused variable `period_size'
sound/pci/cs46xx/cs46xx_lib.c: In function `snd_cs46xx_capture_hw_params':
sound/pci/cs46xx/cs46xx_lib.c:1251: warning: unused variable `period_size'
sound/pci/cs46xx/cs46xx_lib.h: At top level:
sound/pci/cs46xx/cs46xx_lib.c:1028: warning: `_cs46xx_adjust_sample_rate' defined but not used
sound/pci/cs46xx/cs46xx_lib.c:1445: warning: `hw_constraints_period_sizes' defined but not used
make[3]: *** [sound/pci/cs46xx/cs46xx_lib.o] Error 1
make[2]: *** [sound/pci/cs46xx] Error 2
make[1]: *** [sound/pci] Error 2
make: *** [sound] Error 2
Anyone have any ideas?
Ed Tomlinson
next reply other threads:[~2002-11-11 22:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 22:40 Ed Tomlinson [this message]
2002-11-11 23:00 ` [BUG] cs46xx compile error 2.5.47 Florin Iucha
2002-11-12 3:38 ` Chris Friesen
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=200211111740.18312.tomlins@cam.org \
--to=tomlins@cam.org \
--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