From: Lee Revell <rlrevell@joe-job.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: CVS build error with kernel 2.6.13-rc4
Date: Fri, 12 Aug 2005 17:48:22 -0400 [thread overview]
Message-ID: <1123883302.12680.60.camel@mindpipe> (raw)
CC [M] /smb/rlrevell/cvs/alsa/alsa-driver/pci/ac97/ac97_codec.o
/smb/rlrevell/cvs/alsa/alsa-driver/pci/ac97/ac97_codec.c: In function 'snd_ac97_resume':
/smb/rlrevell/cvs/alsa/alsa-driver/include/adriver.h:653: sorry, unimplemented: inlining failed in call to 'msecs_to_jiffies': function body not available
/smb/rlrevell/cvs/alsa/alsa-driver/pci/ac97/ac97_codec.c:2300: sorry, unimplemented: called from here
/smb/rlrevell/cvs/alsa/alsa-driver/include/adriver.h:653: sorry, unimplemented: inlining failed in call to 'msecs_to_jiffies': function body not available
/smb/rlrevell/cvs/alsa/alsa-driver/pci/ac97/ac97_codec.c:2312: sorry, unimplemented: called from here
make[4]: *** [/smb/rlrevell/cvs/alsa/alsa-driver/pci/ac97/ac97_codec.o] Error 1
make[3]: *** [/smb/rlrevell/cvs/alsa/alsa-driver/pci/ac97] Error 2
make[2]: *** [/smb/rlrevell/cvs/alsa/alsa-driver/pci] Error 2
make[1]: *** [_module_/smb/rlrevell/cvs/alsa/alsa-driver] Error 2
make[1]: Leaving directory `/smb/rlrevell/kernel-source/linux-2.6.13-rc4'
make: *** [compile] Error 2
Is this a gcc (4.0.2) bug or a kernel issue?
Lee
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next reply other threads:[~2005-08-12 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 21:48 Lee Revell [this message]
2005-08-13 1:31 ` CVS build error with kernel 2.6.13-rc4 Lee Revell
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=1123883302.12680.60.camel@mindpipe \
--to=rlrevell@joe-job.com \
--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