linux-kernel - Re: 32bit builds on x86-64 host.

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: <4727D391.6080603@goop.org>
Date:	Tue, 30 Oct 2007 18:00:01 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Christoph Hellwig <hch@...radead.org>
CC:	"H. Peter Anvin" <hpa@...or.com>, Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Sam Ravnborg <sam@...nborg.org>
Subject: Re: 32bit builds on x86-64 host.

Christoph Hellwig wrote:
> Which seems rather unnatural to me.  All other merge architectures have
> ARCH=<archdir> where archdir is the name under arch, e.g. mips, powerpc,
> s390.  They then have a CONFIG_FOO_64 and set the utsname and -m32/-m64
> respectively.  It would be nice if x86 could behave like all other
> architectures in this respect.  Especially as the behaviour of the other
> architectures is a lot more intuitive.
>   

Yes, that would be nice.  I keep forgetting the ARCH= in my crossbuild
trees, and end up with strange mismashes.

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