From: "Luck, Tony" <tony.luck@intel.com>
To: Nick Piggin <npiggin@suse.de>, Pekka Enberg <penberg@cs.helsinki.fi>
Cc: linux-kernel@vger.kernel.org
Subject: linux-next ia64 build problems in slqb
Date: Mon, 20 Apr 2009 15:08:30 -0700 [thread overview]
Message-ID: <49ecf25e2378234eed@agluck-desktop.sc.intel.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
The ia64 "allnoconfig" build ends up with the (possibly dubious) combination
of .config options:
CONFIG_SMP=n
CONFIG_NUMA=y
which leads to the following build problems with mm/slqb.c
CC mm/slqb.o
mm/slqb.c: In function ‘__slab_free’:
mm/slqb.c:1735: error: implicit declaration of function ‘slab_free_to_remote’
mm/slqb.c: In function ‘kmem_cache_open’:
mm/slqb.c:2274: error: implicit declaration of function ‘kmem_cache_dyn_array_free’
mm/slqb.c:2275: warning: label ‘error_cpu_array’ defined but not used
mm/slqb.c: In function ‘kmem_cache_destroy’:
mm/slqb.c:2395: error: implicit declaration of function ‘claim_remote_free_list’
mm/slqb.c: In function ‘kmem_cache_init’:
mm/slqb.c:2885: error: ‘per_cpu__kmem_cpu_nodes’ undeclared (first use in this function)
mm/slqb.c:2885: error: (Each undeclared identifier is reported only once
mm/slqb.c:2885: error: for each function it appears in.)
mm/slqb.c:2886: error: ‘kmem_cpu_cache’ undeclared (first use in this function)
-Tony
next reply other threads:[~2009-04-20 22:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 22:08 Luck, Tony [this message]
2009-04-20 23:42 ` linux-next ia64 build problems in slqb Randy Dunlap
2009-04-20 23:59 ` Luck, Tony
2009-04-21 5:51 ` Pekka Enberg
2009-04-21 6:29 ` Paul Mundt
2009-04-21 14:35 ` Christoph Lameter
2009-04-21 18:25 ` Pekka Enberg
2009-04-21 18:45 ` Luck, Tony
2009-04-21 19:07 ` Pekka Enberg
2009-04-21 22:31 ` Luck, Tony
2009-04-22 7:02 ` Pekka J Enberg
2009-04-23 5:50 ` Paul Mundt
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=49ecf25e2378234eed@agluck-desktop.sc.intel.com \
--to=tony.luck@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=penberg@cs.helsinki.fi \
/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.