On Tue, Feb 10, 2009 at 01:53:51PM +0200, Pekka Enberg wrote: > On Tue, Feb 10, 2009 at 11:54 AM, Sachin P. Sant <sachinp@xxxxxxxxxx> wrote: > > Sachin P. Sant wrote: > >> > >> Hi Stephen, > >> > >> Todays next randconfig build on powerpc fails with > >> > >> CC mm/slqb.o > >> mm/slqb.c: In function __slab_free: > >> mm/slqb.c:1648: error: implicit declaration of function > >> slab_free_to_remote > >> mm/slqb.c: In function kmem_cache_open: > >> mm/slqb.c:2174: error: implicit declaration of function > >> kmem_cache_dyn_array_free > >> mm/slqb.c:2175: warning: label error_cpu_array defined but not used > >> mm/slqb.c: In function kmem_cache_destroy: > >> mm/slqb.c:2294: error: implicit declaration of function > >> claim_remote_free_list > >> mm/slqb.c: In function kmem_cache_reap_percpu: > >> mm/slqb.c:2547: error: implicit declaration of function > >> flush_remote_free_cache > >> mm/slqb.c: In function kmem_cache_init: > >> mm/slqb.c:2783: error: per_cpu__kmem_cpu_nodes undeclared (first use in > >> this function) > >> mm/slqb.c:2783: error: (Each undeclared identifier is reported only once > >> mm/slqb.c:2783: error: for each function it appears in.) > >> mm/slqb.c:2784: error: kmem_cpu_cache undeclared (first use in this > >> function) > >> make[1]: *** [mm/slqb.o] Error 1 > >> make: *** [mm] Error 2 > > > > CONFIG_SMP is not set hence the failure. > > Actually, that's not the root cause here. You seem to have CONFIG_SMP > disabled but CONFIG_NUMA enabled. That's not possible on x86 which > makes me think it's a ppc kconfig bug. Hmm? If it is really a valid config, then we should be able to make slqb build with it... -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
