From: Christoph Hellwig <hch@infradead.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: 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 13:10:32 +0000 [thread overview]
Message-ID: <20071030131032.GA32366@infradead.org> (raw)
In-Reply-To: <472675AC.3070509@zytor.com>
On Mon, Oct 29, 2007 at 05:07:08PM -0700, H. Peter Anvin wrote:
> Dave Jones wrote:
> >Before the arch merge, I frequently would test 32bit compiles
> >by doing make ARCH=i386 {bzImage/modules/file.o}
> >
> >Since commit 47572387d58a9584c60ebbbdee56fc92c627f16f
> >how does one do this?
> >
>
> make ARCH=i386 {bzImage/modules/file.o}
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.
>
> Amazing, isn't it?
>
> -hpa
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
---end quoted text---
next prev parent reply other threads:[~2007-10-30 13:10 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 [this message]
2007-10-31 1:00 ` Jeremy Fitzhardinge
2007-10-31 1:11 ` H. Peter Anvin
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=20071030131032.GA32366@infradead.org \
--to=hch@infradead.org \
--cc=davej@redhat.com \
--cc=hpa@zytor.com \
--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