From: Adrian Bunk <bunk@fs.tum.de>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, "Martin J. Bligh" <mbligh@aracnet.com>
Subject: 2.5.64-mm8: link error with CONFIG_NUMA and !CONFIG_SMP
Date: Sun, 16 Mar 2003 20:10:13 +0100 [thread overview]
Message-ID: <20030316191012.GG10253@fs.tum.de> (raw)
In-Reply-To: <20030316024239.484f8bda.akpm@digeo.com>
I get many errors at the final linking when compiling a kernel with
CONFIG_NUMA enabled but CONFIG_SMP disabled:
<-- snip -->
...
/home/bunk/linux/kernel-2.5/linux-2.5.64-mm8/include/asm/topology.h:41:
undefined reference to `cpu_2_node'
...
<-- snip -->
the problem is that include/asm-i386/topology.h says:
<-- snip -->
...
#ifdef CONFIG_NUMA
...
extern volatile int cpu_2_node[];
...
<-- snip -->
but cpu_2_node is in arch/i386/kernel/smpboot.c that only gets included
with CONFIG_SMP.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2003-03-16 18:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-16 10:42 2.5.64-mm8 Andrew Morton
2003-03-16 11:45 ` [patch] 2.5.64-mm8: fs/affs/dir.c doesn't compile Adrian Bunk
2003-03-16 12:21 ` 2.5.64-mm8 Roman Zippel
2003-03-16 13:02 ` 2.5.64-mm8: drivers/atm/idt77252.c doesn't compile Adrian Bunk
2003-03-16 15:44 ` Adrian Bunk
2003-03-17 15:43 ` [Linux-ATM-General] " chas williams
2003-03-18 20:49 ` Adrian Bunk
2003-03-20 8:44 ` David S. Miller
2003-03-16 18:00 ` Adrian Bunk
2003-03-16 13:43 ` [patch] 2.5.64-mm8: miropcm20-rds.c " Adrian Bunk
2003-03-16 13:49 ` 2.5.64-mm8 Mike Galbraith
2003-03-16 17:12 ` 2.5.64-mm8 Helge Hafting
2003-03-16 19:10 ` Adrian Bunk [this message]
2003-03-16 19:32 ` 2.5.64-mm8: link error with CONFIG_NUMA and !CONFIG_SMP Martin J. Bligh
2003-03-16 19:44 ` Martin J. Bligh
2003-03-16 19:58 ` Adrian Bunk
2003-03-16 19:20 ` 2.5.64-mm8 Josh McKinney
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=20030316191012.GG10253@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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;
as well as URLs for NNTP newsgroup(s).