linux-kernel - Re: [PATCH] Add ``cloneconfig'' target

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTimnvAZW_EBC_Y72pEWz2fjE+djkfi60u78XPpeT@mail.gmail.com>
Date:	Sun, 27 Feb 2011 12:13:47 -0500
From:	Arnaud Lacombe <lacombar@...il.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Sam Ravnborg <sam@...nborg.org>, Jeff Mahoney <jeffm@...e.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Roman Zippel <zippel@...ux-m68k.org>,
	linux-kbuild@...r.kernel.org
Subject: Re: [PATCH] Add ``cloneconfig'' target

Hi,

On Sun, Feb 27, 2011 at 4:03 AM, Geert Uytterhoeven
<geert@...ux-m68k.org> wrote:
> On Sat, Feb 26, 2011 at 23:18, Sam Ravnborg <sam@...nborg.org> 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@...nborg.org> 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?
>
No.

% gmake ARCH=mips menuconfig
#
# using defaults found in /boot/config-2.6.35.11-83.fc14.x86_64
#
[...]

% gmake CROSS_COMPILE=bla ARCH=mips menuconfig
#
# using defaults found in /boot/config-2.6.35.11-83.fc14.x86_64
#
[...]

Which is plainly just wrong.

 - Arnaud

> Gr{oetje,eeting}s,
>
>                         Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
>
> 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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/