From: Bob Gill <gillb4@telusplanet.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6.15-rc2-git3 build fails at mtrr/ipi_handler undeclared
Date: Thu, 24 Nov 2005 00:17:57 -0700 [thread overview]
Message-ID: <43856925.1020704@telusplanet.net> (raw)
Hi.
I am trying to build 2.6.15-rc2-git3, but it fails with an error:
make: *** [arch/i386/kernel] Error 2
CHK include/linux/version.h
CHK include/linux/compile.h
CHK usr/initramfs_list
CC arch/i386/kernel/cpu/mtrr/main.o
arch/i386/kernel/cpu/mtrr/main.c: In function `set_mtrr':
arch/i386/kernel/cpu/mtrr/main.c:225: error: `ipi_handler' undeclared
(first use in this function)
arch/i386/kernel/cpu/mtrr/main.c:225: error: (Each undeclared identifier
is reported only once
arch/i386/kernel/cpu/mtrr/main.c:225: error: for each function it
appears in.)
make[3]: *** [arch/i386/kernel/cpu/mtrr/main.o] Error 1
make[2]: *** [arch/i386/kernel/cpu/mtrr] Error 2
make[1]: *** [arch/i386/kernel/cpu] Error 2
make: *** [arch/i386/kernel] Error 2
CHK include/linux/version.h
...
(vmlinuz/initial ramdisk image are not built, etc.)
....
but ipi_handler seems to be defined at line 141 in
/arch/i386/kernel/cpu/mtrr/main.c. However, my build script does not
include SMP (I'm on a single cpu machine), and ipi_handler is wrapped in
#ifdef CONFIG_SMP
#endif
(my SMP build options are):
CONFIG_BROKEN_ON_SMP=y
# CONFIG_X86_BIGSMP is not set
# CONFIG_SMP is not set
CONFIG_X86_FIND_SMP_CONFIG=y
....
(The obvious solution is to change my script to CONFIG_SMP=Y, but I
suspect there is a more elegant solution).
2.6.15-rc2 builds/runs ok with the same build script.
Please mail me directly as I'm not on the list.
TIA
Bob
next reply other threads:[~2005-11-24 7:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 7:17 Bob Gill [this message]
2005-11-24 7:52 ` 2.6.15-rc2-git3 build fails at mtrr/ipi_handler undeclared Hugh Dickins
2005-11-24 20:19 ` Bob Gill
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=43856925.1020704@telusplanet.net \
--to=gillb4@telusplanet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox