linux-kernel - Re: kbuild feature/question: default ARCH

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: <20070214091144.GA25846@uranus.ravnborg.org>
Date:	Wed, 14 Feb 2007 10:11:44 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	lkml <linux-kernel@...r.kernel.org>, olecom@...wer.upol.cz,
	zippel@...ux-m68k.org
Subject: Re: kbuild feature/question: default ARCH

On Tue, Feb 13, 2007 at 10:06:19PM -0800, Randy Dunlap wrote:
> Hi,
> 
> I'd like for kbuild to default ARCH to the already-symlinked
> arch in include/asm-$(ARCH) if ARCH is not specified on the
> command line or in the environment.
Another approach I have been toying with previously was to
include ARCH in .config. But I somehow failed
to get it working and it went on my TODO list.

If kconfig get extended to so it can include Kconfig
files for all archs then it could be a Kconfig
option like anything else to select architecture
and this would also solve your issue.

As for the "export ARCH=i386" proposal this is of no
use for people crosscompiling a lot.
Think of the 'Al Viro' setup with crosscompile for 5+
different architectures.

But as I have no patches this is just cheap talk for now.

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