From: Denys Dmytriyenko <denys@ti.com>
To: "Saran, Sajesh Kumar" <sajesh@ti.com>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>,
"Senicic, Djordje" <d-senicic1@ti.com>
Subject: Re: Compiling gcc for A15 in Yocto
Date: Wed, 10 Jul 2013 12:32:14 -0400 [thread overview]
Message-ID: <20130710163214.GA16407@edge> (raw)
In-Reply-To: <8EAE6244CE843044A42356038645C85515733685@DFLE12.ent.ti.com>
On Wed, Jul 10, 2013 at 03:52:47PM +0000, Saran, Sajesh Kumar wrote:
> I am not clear in last e-mail.
>
> We are trying to compile gcc for ARM in an X86 Ubuntu machine.
Sajesh,
If you use recent recipes in Yocto to build gcc from sources, it doesn't use
any git or svn repositories any more, but downloads a release tarball. I've
done it before and there's an easy way to enable it in Arago - just set
TOOLCHAIN_TYPE=internal
--
Denys
> From: meta-arago-bounces@arago-project.org [mailto:meta-arago-bounces@arago-project.org] On Behalf Of Saran, Sajesh Kumar
> Sent: Wednesday, July 10, 2013 11:51 AM
> To: meta-arago@arago-project.org; Senicic, Djordje
> Subject: [meta-arago] Compiling gcc for A15 in Yocto
>
> Hi,
>
> We are trying to compile gcc for ARM (A15).
> The cloning of SVN repo is very slow and taking very long time (~6 hours and still continuing).
>
> Have anybody have similar experience on building gcc on ARM?
>
> Regards,
> Sajesh
>
> _______________________________________________
> meta-arago mailing list
> meta-arago@arago-project.org
> http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
next prev parent reply other threads:[~2013-07-10 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 15:51 Compiling gcc for A15 in Yocto Saran, Sajesh Kumar
2013-07-10 15:52 ` Saran, Sajesh Kumar
2013-07-10 16:32 ` Denys Dmytriyenko [this message]
2013-07-11 2:23 ` Siddharth Heroor
2013-07-11 2:57 ` Denys Dmytriyenko
2013-07-11 3:34 ` Siddharth Heroor
2013-07-11 4:11 ` Denys Dmytriyenko
2013-07-11 4:22 ` Siddharth Heroor
2013-07-10 15:53 ` Maupin, Chase
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=20130710163214.GA16407@edge \
--to=denys@ti.com \
--cc=d-senicic1@ti.com \
--cc=meta-arago@arago-project.org \
--cc=sajesh@ti.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.