[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <49ecf25e2378234eed@agluck-desktop.sc.intel.com>
Date: Mon, 20 Apr 2009 15:08:30 -0700
From: "Luck, Tony" <tony.luck@...el.com>
To: Nick Piggin <npiggin@...e.de>,
Pekka Enberg <penberg@...helsinki.fi>
Cc: linux-kernel@...r.kernel.org
Subject: linux-next ia64 build problems in slqb
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists