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: <4727D651.2010402@zytor.com>
Date:	Tue, 30 Oct 2007 18:11:45 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
CC:	Christoph Hellwig <hch@...radead.org>,
	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.

Jeremy Fitzhardinge wrote:
> 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.
> 

That, however, is a bigger problem that also affects, for example, 
compiling for MIPS on an x86 host.  I believe Sam is working on a 
solution for that.

(That doesn't mean that is not the right thing to do.)

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