On Mon, 4 May 2009, Peter Zijlstra wrote: > On Mon, 2009-05-04 at 14:15 +0200, Andi Kleen wrote: > > Steven Rostedt <rostedt@xxxxxxxxxxx> writes: > > > > > Here's the list and order of search: > > > > > > /proc/config.gz > > > /boot/vmlinuz-`uname -r` > > > vmlinux # local to the directory > > > /lib/modules/`uname -r`/kernel/kernel/configs.ko > > > kernel/configs.ko > > > kernel/configs.o > > > .config > > > > > > That seems like the wrong order. ./.config should always be first for > > compatibility. > > > > That order would completely wreck all my build scripts, and I suspect > > others too. > > Quite, except that I hardly ever have a ./.config since I make extensive > use of O=foo I'm fine with using .config as first choice (that is what the script originally did) but I wanted to make it as easy for non developers as possible. Taking from /proc or /boot was most likely the best to give a minimal boot environment. But I can see why .config is probably the best choice for having the most power with the tool. It is how you can always force it to do something you want, and is the most logical place to expect the script to read from. I'll update it. Thanks, -- 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
