Hi, I was just trying to reproduce that 'register_one_node' build error (and couldn't even with the supplied .config file; weird). Anyway, after I enabled CONFIG_NUMA (but not CONFIG_ACPI), I got the following error message. Seems that some config options should prevent this config from even being possible to create. Any ideas or suggestions? This is still on 2.6.18-rc4-git1. scripts/kconfig/conf -s arch/i386/Kconfig CHK include/linux/version.h CHK include/linux/utsrelease.h CC arch/i386/kernel/asm-offsets.s In file included from include/asm/mmzone.h:18, from include/linux/mmzone.h:439, from include/linux/gfp.h:4, from include/linux/slab.h:14, from include/linux/percpu.h:4, from include/linux/rcupdate.h:41, from include/linux/pid.h:4, from include/linux/sched.h:70, from include/linux/module.h:9, from include/linux/crypto.h:20, from arch/i386/kernel/asm-offsets.c:7: include/asm/srat.h:31:2: error: #error CONFIG_ACPI_SRAT not defined, and srat.h header has been included make[1]: *** [arch/i386/kernel/asm-offsets.s] Error 1 make: *** [prepare0] Error 2 config file is attached. --- ~Randy
Attachment:
config-srat-err
Description: Binary data
- Follow-Ups:
- Re: another NUMA build error
- From: KAMEZAWA Hiroyuki <[email protected]>
- Re: another NUMA build error
- Prev by Date: Re: [PATCH 2.6.9-34.0.1.EL] hid-core.c: Add GTCO CalComp PIDs to blacklist
- Next by Date: Re: RFC - how to balance Dirty+Writeback in the face of slow writeback.
- Previous by thread: 2.6.18-rc4 i386 CONFIG_4KSTACKS does not use the hardirq stack
- Next by thread: Re: another NUMA build error
- Index(es):