kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: madhavi.linux@gmail.com (Madhavi Manchala)
To: kernelnewbies@lists.kernelnewbies.org
Subject: ARM Cross Compilation Toolchain on x86 machine
Date: Fri, 7 Jan 2011 15:00:58 +0530	[thread overview]
Message-ID: <AANLkTin+vx=8COLYP8LSqcnQ3H1CWsM27DegTsio6BKC@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinq4maamtZyw86Cswna8m2=vP7L8efONCg+ap8G@mail.gmail.com>

On Fri, Jan 7, 2011 at 6:44 AM, Manohar Vanga <manohar.vanga@gmail.com> wrote:
> Hi,
> I would suggest using ELDK. I have had an easy time setting it up in the
> past.
> $ wget ftp://ftp.denx.de/pub/eldk/4.2/arm-linux-x86/iso/arm-2008-11-24.iso
> $ mount -o loop arm-2008-11-24.iso /mnt
> $ cd /mnt
> $ sudo ./install -d /opt/eldk-4.2
> Now add "/opt/eldk-4.2/usr/bin/" to your PATH. ?My preferred method is to
> instead do
> $ export CROSS_COMPILE=/opt/eldk-4.2/usr/bin/arm-linux-
> and use the $CROSS_COMPILE variable when setting the toolchains in my
> Makefiles. Hope this helps :-)

Thanks Manohar.

Where can I get the list of supported CPU family types for ARM
architecture like ARM5, ARM7, ARM926EJ etc. In case of Power
Architecture (PPC) there is a list as shown in the below link at ELDK
site
http://www.denx.de/wiki/view/DULG/ELDKSupportedTargetArchitectures

The same is also mentioned in the table at 3.6.A Table of possible
values for $CROSS_COMPILE section of the ELDK at
http://www.denx.de/wiki/view/DULG/ELDKUsage

For us, ARM9 is suitable.

Thanks and Regards,
Madhavi M.

  reply	other threads:[~2011-01-07  9:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-06 15:38 ARM Cross Compilation Toolchain on x86 machine Madhavi Manchala
2011-01-06 15:48 ` vinit agrawal
2011-01-07  0:55   ` Alexandre Courbot
2011-01-07  7:34   ` Madhavi Manchala
2011-01-07  8:36     ` Alexandre Courbot
2011-01-07  1:14 ` Manohar Vanga
2011-01-07  9:30   ` Madhavi Manchala [this message]
2011-01-07 16:26     ` Dave Hylands
2011-02-01 16:34       ` Chaitannya Mahatme
2011-02-01 17:53         ` vinit agrawal

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='AANLkTin+vx=8COLYP8LSqcnQ3H1CWsM27DegTsio6BKC@mail.gmail.com' \
    --to=madhavi.linux@gmail.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).