public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 32bit builds on x86-64 host.
Date: Wed, 31 Oct 2007 10:41:48 +0100	[thread overview]
Message-ID: <20071031094148.GA24100@uranus.ravnborg.org> (raw)
In-Reply-To: <20071031085739.GA5468@infradead.org>

On Wed, Oct 31, 2007 at 08:57:39AM +0000, Christoph Hellwig wrote:
> On Tue, Oct 30, 2007 at 06:00:01PM -0700, 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's a problem with all architectures currently.  But I think Sam has
> a patch that at least stores ARCH when using objdir != srcdir builds.
kbuild check's the asm symlink and error out if it is wrong.
So forgetting ARCH should be captured. But the check does not
store ARCH which is what I hope to have fixed for next merge window.

So for now if you forget ARCH you should be warned.
And in the future kbuild will remember what ARCH (and CROSS_COMPILE)
you used when configuring the kernel.

For x86 the current check does not help use because the asm symlink
is the same for i386 and x86_64 - so for now we are out of luck.

	Sam

      reply	other threads:[~2007-10-31  9:40 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
2007-10-31  8:57       ` Christoph Hellwig
2007-10-31  9:41         ` Sam Ravnborg [this message]

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=20071031094148.GA24100@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=davej@redhat.com \
    --cc=hch@infradead.org \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.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