Messages in this thread | | | Date | Fri, 17 Feb 2012 16:06:56 +0400 | From | Konstantin Khlebnikov <> | Subject | Re: linux-next: build failure after merge of the final tree (akpm tree related) |
| |
Stephen Rothwell wrote: > Hi Andrew, > > Today's linux-next fails to build (s390 allnoconfig) like this: > > In file included from arch/s390/mm/maccess.c:15: > include/linux/gfp.h: In function 'gfp_zonelist': > include/linux/gfp.h:267: error: '__enabled_CONFIG_NUMA' undeclared (first use in this function) > include/linux/gfp.h:267: error: (Each undeclared identifier is reported only once > include/linux/gfp.h:267: error: for each function it appears in.) > include/linux/gfp.h:267: error: '__enabled_CONFIG_NUMA_MODULE' undeclared (first use in this function) > > and many more. This also happens in other architectures and configs but > (obviously) not all builds. > > Presumably caused by commit 053361e1a072 ("mm: replace NUMA_BUILD with > IS_ENABLED(CONFIG_NUMA)"). >
Oops, yes, my fault.
'config NUMA' defined in arch-specific Kconfig, some of them does not have it. Thus Kconfig generates these constants not for all architectures.
config MIGRATION and config COMPACTION already in generic mm/Kconfig
| |