From: Tony Lindgren <tony@atomide.com>
To: Trilok Soni <soni.trilok@gmail.com>
Cc: kuldeep nigam <kuldeepnigam@gmail.com>, linux-omap@vger.kernel.org
Subject: Re: How to build Native GCC for ARM
Date: Tue, 11 Mar 2008 08:32:47 +0200 [thread overview]
Message-ID: <20080311063247.GF7524@atomide.com> (raw)
In-Reply-To: <5d5443650803102345s15a9adaai19893faec8cc3a92@mail.gmail.com>
* Trilok Soni <soni.trilok@gmail.com> [080311 08:46]:
> Hi Kuldeep,
>
> On Tue, Mar 11, 2008 at 12:03 PM, kuldeep nigam <kuldeepnigam@gmail.com> wrote:
> >
> >
> >
> > On Tue, Mar 11, 2008 at 11:48 AM, Trilok Soni <soni.trilok@gmail.com> wrote:
> > > Hi Kuldeep,
> > >
> > > On Tue, Mar 11, 2008 at 10:54 AM, kuldeep nigam <kuldeepnigam@gmail.com>
> > wrote:
> > > > Hi all,
> > > >
> > >
> > > Why you have such requirement and why you can't use the existing
> > > cross-compilers? Please explain.
> > >
> > > --
> > > ---Trilok Soni
> > > http://triloksoni.wordpress.com
> > >
> >
> >
> > i m working on OMAP2430 board and want to compile some application on the
> > board itself.
> >
>
> Please use cross-compiler instead. I don't suggest use this approach.
> Did you tried scratchbox?
You can also use crosstool.org to compile it, but it may be a big to
get that bootstrapped natively on arm :) How about just install debian
armel to an nfsroot and compile with that?
Tony
next prev parent reply other threads:[~2008-03-11 7:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5ae31d3b0803102224s7c99170bv7e5d056ba37689d7@mail.gmail.com>
[not found] ` <5d5443650803102318k3fc9cacdkb49c2fe23fafc5ba@mail.gmail.com>
[not found] ` <5ae31d3b0803102333y1d5e8c3ev9fc3dec844d05fd3@mail.gmail.com>
2008-03-11 6:45 ` How to build Native GCC for ARM Trilok Soni
2008-03-11 6:32 ` Tony Lindgren [this message]
2008-03-11 11:56 ` Luís Vitório Cargnini
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=20080311063247.GF7524@atomide.com \
--to=tony@atomide.com \
--cc=kuldeepnigam@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=soni.trilok@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.