linux-kernel - Re: [PATCH 0/11 v3] enable "make ARCH=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]

Message-ID: <47356AD5.4070102@garzik.org>
Date:	Sat, 10 Nov 2007 03:24:53 -0500
From:	Jeff Garzik <jeff@...zik.org>
To:	Paul Mundt <lethal@...ux-sh.org>, Sam Ravnborg <sam@...nborg.org>,
	Jeff Garzik <jeff@...zik.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 0/11 v3] enable "make ARCH=x86"

Paul Mundt wrote:
> This is one of the things I've been wondering about with an sh/sh64
> unification, as we have no option but having completely different
> toolchains, and CONFIG_64BIT=y won't work there when they are both
> using a 32-bit ABI.


IMO it seems like you ought to be able to do

	make ARCH=sh
		or
	make ARCH=sh64

and have it do the right thing.  Ditto for ppc/ppc64, etc.

Sane, straightforward, simple, consistent with existing practice...

	Jeff


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