Hi, On Sat, Feb 26, 2011 at 5:18 PM, Sam Ravnborg <sam@xxxxxxxxxxxx> wrote: > On Sat, Feb 26, 2011 at 02:47:01PM -0500, Arnaud Lacombe wrote: >> Hi, >> >> On Fri, Feb 25, 2011 at 1:07 AM, Sam Ravnborg <sam@xxxxxxxxxxxx> wrote: >> > We already have something remotely similar in kconfig. >> > We use the following list: >> > config DEFCONFIG_LIST >> > string >> > depends on !UML >> > option defconfig_list >> > default "/lib/modules/$UNAME_RELEASE/.config" >> > default "/etc/kernel-config" >> > default "/boot/config-$UNAME_RELEASE" >> > default "$ARCH_DEFCONFIG" >> > default "arch/$ARCH/defconfig" >> > >> I may argue that anything within the Linux tree which point >> _by_default_ to something outside the tree itself is broken. > The above allows the average user to just type "make menuconfig" > and then the configuration of the current kernel is presented to > the user. I'm sure there is a way to do this from the Kbuild and not from the Kconfig. > This is convinient in many cases. this is a subjective point of view. I do build a lot of kernel for anything but the current machine I'm using. > We know the /proc/config.gz is an incresingly popular way to gain > access to the configuration of the running kernel. So extending > the already know and working way to obtaing the configuration > of the running kernel to suppport /proc/config.gz is logical. Then again, this should be doable from Kbuild. > The fact that the configuration is gzipped does not warrant > a new option to deal with this that almost duplicate the > existing functionality. > agree. - Arnaud -- 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
