kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: matthias.bgg@googlemail.com (Matthias Brugger)
To: kernelnewbies@lists.kernelnewbies.org
Subject: cross compile linux
Date: Sat, 11 Feb 2012 11:02:26 +0100	[thread overview]
Message-ID: <4F363CB2.4040402@gmail.com> (raw)
In-Reply-To: <CAEnQRZBFEnpGEKkGBosuhoKu-Ur1zrw761J5zJd=vK44de45gQ@mail.gmail.com>

On 02/11/2012 10:15 AM, Daniel Baluta wrote:
> On Sat, Feb 11, 2012 at 9:05 AM, chromaticwt zac<zac.3.14159@gmail.com>  wrote:
>> what is the proper way to cross compile the linux kernel from one arch to
>> another? specifically,
>> i386 ->  ppc.
>
> You should use a cross-compiler. I recommend you crosstool-ng.
> Use google for references. [1]
>
> thanks,
> Daniel.
>
> [1] http://forum.samdroid.net/wiki/showwiki/How+to+build+cross+toolchains+for+ARM+crosstool-NG
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

Apart from that in the Makefile you have to specify with
ARCH ?= ppc
and in CROSS_COMPILE the prefix of your cross compiler (e.g. pcc-linux-)

beware that the corss compile toolchain is in you $PATH.

If you want to cross compile for an embedded Linux board, have a look at 
buildroot. With this tool you can build the whole userspace environment 
to get a shell running.

good luck,
matthias

-- 
---
http://motzblog.wordpress.com/

  reply	other threads:[~2012-02-11 10:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-11  7:05 cross compile linux chromaticwt zac
2012-02-11  9:15 ` Daniel Baluta
2012-02-11 10:02   ` Matthias Brugger [this message]
2012-02-12 11:17 ` Mulyadi Santosa
2012-02-12 23:38   ` Anuz Pratap Singh Tomar
2012-02-12 23:40     ` Anuz Pratap Singh Tomar

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=4F363CB2.4040402@gmail.com \
    --to=matthias.bgg@googlemail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).