public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Herrmann <aherrman@arcor.de>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Kconfig: ARCH=x86
Date: Fri, 16 Nov 2007 13:43:20 +0100	[thread overview]
Message-ID: <20071116124320.GB12086@devil> (raw)
In-Reply-To: <20071116111446.GA16968@devil>

On Fri, Nov 16, 2007 at 12:14:46PM +0100, Andreas Herrmann wrote:
> BTW, is the x86 kernel build documented somewhere?
> At a first glance I didn't find anything suitable under Documentation/.
> Maybe some explanation (like the above) should be added there.

When the ARCH=x86 build is documented, some words about
cross-compilation should be added:

  (1) To compile a 32-bit kernel on a 64-bit system you have to
  Disable 64bit support in menuconfig (config, oldconfig etc.).  A
  subsequent kernel compile will build a 32-bit kernel.  No cross
  compiler is needed.

  (2) To compile a 64-bit kernel on a 32-bit system you have to switch
  on 64-bit support in menuconfig (or config, oldconfig, etc.).  For
  the subsequent kernel compile a cross compiler (supporting 64-bit)
  is needed. You have to use a command line like

        # make CROSS_COMPILE=x86_64-pc-linux-gnu-

  to cross compile your kernel.


Regards,

Andreas


  parent reply	other threads:[~2007-11-16 11:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-16 11:14 Kconfig: ARCH=x86 Andreas Herrmann
2007-11-16 12:37 ` Kconfig: ARCH=x86 causes wrong utsname.machine Andreas Herrmann
2007-11-16 15:20   ` H. Peter Anvin
2007-11-16 22:15     ` Sam Ravnborg
2007-11-16 22:58       ` H. Peter Anvin
2007-11-16 23:33         ` H. Peter Anvin
2007-11-17  7:57         ` Sam Ravnborg
2007-11-17 10:16           ` [PATCH] x86: fix UTS_MACHINE to be "i386" for 32-bit build and "x86_64" for 64-bit build Andreas Herrmann
2007-11-16 12:43 ` Andreas Herrmann [this message]
2007-11-16 12:58 ` Kconfig: ARCH=x86 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=20071116124320.GB12086@devil \
    --to=aherrman@arcor.de \
    --cc=linux-kbuild@vger.kernel.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