From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: alpha: Hangcheck timer doesn't compile
Date: Wed, 19 Feb 2003 09:53:03 +0100 [thread overview]
Message-ID: <20030219085303.GJ351@lug-owl.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]
Hi!
The hangcheck timer seems cannot be compiled on Alphas:
gcc -Wp,-MD,drivers/char/.hangcheck-timer.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mno-fp-regs -ffixed-8 -msmall-data -mcpu=ev4 -Wa,-mev6 -fomit-frame-pointer -nostdinc -iwithprefix include -DMODULE -DKBUILD_BASENAME=hangcheck_timer -DKBUILD_MODNAME=hangcheck_timer -c -o drivers/char/hangcheck-timer.o drivers/char/hangcheck-timer.c
drivers/char/hangcheck-timer.c: In function `hangcheck_init':
drivers/char/hangcheck-timer.c:112: `current_cpu_data' undeclared (first use in this function)
drivers/char/hangcheck-timer.c:112: (Each undeclared identifier is reported only once
drivers/char/hangcheck-timer.c:112: for each function it appears in.)
make[3]: *** [drivers/char/hangcheck-timer.o] Error 1
make[2]: *** [drivers/char] Error 2
make[1]: *** [drivers] Error 2
make: *** [modules] Error 2
This is because current_cpu_data doesn't (currently) exist on alpha.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur
fuer einen Freien Staat voll Freier Bürger" | im Internet!
Shell Script APT-Proxy: http://lug-owl.de/~jbglaw/software/ap2/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-02-19 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 8:53 Jan-Benedict Glaw [this message]
2003-02-23 2:27 ` alpha: Hangcheck timer doesn't compile Richard Henderson
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=20030219085303.GJ351@lug-owl.de \
--to=jbglaw@lug-owl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.