On Sat, Feb 26, 2011 at 23:18, Sam Ravnborg <sam@xxxxxxxxxxxx> wrote:
> On Sat, Feb 26, 2011 at 02:47:01PM -0500, Arnaud Lacombe wrote:
>> 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. This is convinient in many cases.
> 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.
Does this detect cross-compiling? The 'depends on !UML' triggered me...
Gr{oetje,eeting}s,
            Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
             Â Â -- Linus Torvalds
--
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
