On Fri, 21 Aug 2009, Ingo Molnar wrote: > > * Steven Rostedt <rostedt@xxxxxxxxxxx> wrote: > > > On Fri, 21 Aug 2009, Ingo Molnar wrote: > > > > > > ah - indeed, i forgot that it bases its decision off /proc/config, > > > if available, right? > > > > Here's the list in order of seach: > > > > 1. local .config file (in tree root) > > 2. /proc/config.gz > > 3. /boot/config-`uname -r` > > 4. /boot/vmlinuz-`uname -r` (extracts .config if configured in) > > 5. vmlinux (local built vmlinux if .config is configured in) > > 6. /lib/modules/`uname -r`/kernel/kernel/configs.ko > > 7. kernel/configs.ko > > 8. kernel/configs.o > > > > I originally had /proc/config.gz but Andi Kleen correctly pointed > > out that it would be more intuitive if we use the local .config > > first. This would be something that I myself would expect. If you > > don't want the local .config used, then simply delete it. > > Well, but there's already a mechanism to include configs as a > must-have list: KCONFIG_ALLCONFIG=.config. That's something I can add to try first. -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
