linux-kernel - Re: [PATCH] kbuild: honor the ARCH setting of the existing configuration

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CACqU3MU1yS73++j3H00fbfeBpmKZJ=S93SObnccsw+Bto4V_8w@mail.gmail.com>
Date:	Mon, 1 Aug 2011 13:33:14 -0400
From:	Arnaud Lacombe <lacombar@...il.com>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Randy Dunlap <rdunlap@...otime.net>, Michal Marek <mmarek@...e.cz>,
	linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org
Subject: Re: [PATCH] kbuild: honor the ARCH setting of the existing configuration

Hi,

On Mon, Aug 1, 2011 at 4:42 AM, David Woodhouse <dwmw2@...radead.org> wrote:
> On Sun, 2011-07-31 at 19:05 -0700, Randy Dunlap wrote:
>>
>> > I would love to see $ARCH turned into a proper configuration option.
>>
>> I don't object in principle, but I'm expecting to have to modify/update
>> multiple *working* scripts as a result.  But of course this won't be
>> the first time and I don't expect it to be the last time either.
>> [signed:  eeyore]
>
> :)
>
> Yeah, that's why I'd kind of like to see it done *once*, *properly*.
>
> Arnaud's hack to read it from .config is cute, but might give behaviour
> that people will come to depend on in their scripts and then we take it
> away again.
>
Instead of talking of irrelevant implementation details, what
_behavior_ do you expect ?

The priority I expect is (from most to least):
 1. command line
 2. existing configuration (.config)
 3. Makefile's default
 4. Kconfig default

 - Arnaud
--
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/