From: Stephane Wirtel <stephane.wirtel@belgacom.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Compile Error with the 2.5.44-ac5 and the P4
Date: Mon, 28 Oct 2002 16:32:37 +0100 [thread overview]
Message-ID: <20021028153237.GA19602@debian.lan> (raw)
here is an error.
make -f arch/i386/kernel/Makefile
make -f arch/i386/kernel/cpu/Makefile
make -f arch/i386/kernel/cpu/cpufreq/Makefile
make -f arch/i386/kernel/cpu/mcheck/Makefile
gcc -Wp,-MD,arch/i386/kernel/cpu/mcheck/.p4.o.d -D__KERNEL__ -Iinclude
-Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing
-fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -p
-Iarch/i386/mach-voyager -nostdinc -iwithprefix include
-DKBUILD_BASENAME=p4 -c -o arch/i386/kernel/cpu/mcheck/p4.o
arch/i386/kernel/cpu/mcheck/p4.c
arch/i386/kernel/cpu/mcheck/p4.c: In function `intel_thermal_interrupt':
arch/i386/kernel/cpu/mcheck/p4.c:51: warning: implicit declaration of function `ack_APIC_irq'
arch/i386/kernel/cpu/mcheck/p4.c: In function `intel_init_thermal':
arch/i386/kernel/cpu/mcheck/p4.c:91: warning: implicit declaration of function `apic_read'
arch/i386/kernel/cpu/mcheck/p4.c:105: `THERMAL_APIC_VECTOR' undeclared (first use in this function)
arch/i386/kernel/cpu/mcheck/p4.c:105: (Each undeclared identifier is reported only once
arch/i386/kernel/cpu/mcheck/p4.c:105: for each function it appears in.)
arch/i386/kernel/cpu/mcheck/p4.c:107: warning: implicit declaration of function `apic_write_around'
make[3]: *** [arch/i386/kernel/cpu/mcheck/p4.o] Error 1
make[2]: *** [arch/i386/kernel/cpu/mcheck] Error 2
make[1]: *** [arch/i386/kernel/cpu] Error 2
make: *** [arch/i386/kernel] Error 2
Best regards,
Stephane Wirtel
--
Stephane Wirtel <stephane.wirtel@belgacom.net>
GPG ID : 1024D/C9C16DA7 | 5331 0B5B 21F0 0363 EACD B73E 3D11 E5BC C9C1 6DA7
next reply other threads:[~2002-10-28 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 15:32 Stephane Wirtel [this message]
2002-10-28 15:56 ` Compile Error with the 2.5.44-ac5 and the P4 Dave Jones
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=20021028153237.GA19602@debian.lan \
--to=stephane.wirtel@belgacom.net \
--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.