From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Christoph Hellwig <hch@infradead.org>,
Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: 32bit builds on x86-64 host.
Date: Tue, 30 Oct 2007 18:11:45 -0700 [thread overview]
Message-ID: <4727D651.2010402@zytor.com> (raw)
In-Reply-To: <4727D391.6080603@goop.org>
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
next prev parent reply other threads:[~2007-10-31 1:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 23:32 32bit builds on x86-64 host Dave Jones
2007-10-30 0:06 ` Al Viro
2007-10-30 0:07 ` H. Peter Anvin
2007-10-30 0:39 ` Dave Jones
2007-10-30 13:10 ` Christoph Hellwig
2007-10-31 1:00 ` Jeremy Fitzhardinge
2007-10-31 1:11 ` H. Peter Anvin [this message]
2007-10-31 8:57 ` Christoph Hellwig
2007-10-31 9:41 ` Sam Ravnborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4727D651.2010402@zytor.com \
--to=hpa@zytor.com \
--cc=davej@redhat.com \
--cc=hch@infradead.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox