linux-kernel - Re: [PATCH] replace "make ARCH=i386/x86

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 05 Nov 2007 15:46:20 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Sam Ravnborg <sam@...nborg.org>
CC:	Roland Dreier <rdreier@...co.com>,
	Christoph Hellwig <hch@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] replace "make ARCH=i386/x86_64 with make ARCH=x86"

Sam Ravnborg wrote:
> On Mon, Nov 05, 2007 at 01:36:42PM -0800, Roland Dreier wrote:
>>  > Like this:
>>  > $ make ARCH=foo
>>  > Makefile:201: *** "ERROR: ARCH (foo) does not exist".  Stop.
>>
>> Seems sane, but maybe it would be worth putting in a special case
>> check for someone using i386 or x86_64 for ARCH, and tell them to
>> switch to x86?
> 
> Will do so if my patchset gets applied. Need to redo it but
> that will be later this week and then I hope for a bit more
> feedback from the x86 guys.

The patchset has looked good to me, and I believe it would be better to 
take this particular breakage sooner rather than later.

I haven't spoken up actively mostly because I wanted to look at the user 
comments as they have been coming in.

The issue with "make allyesconfig" concerns me, although the same 
situation already exists with any multiple-choice configuration.  What I 
guess we really want is to be able to specify a few specific choices.

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