From: ANDY KENNEDY <ANDY.KENNEDY@adtran.com>
To: 'Nikita Orlov' <nikitos1550@yandex.ru>,
Bryan Hundven <bryanhundven@gmail.com>
Cc: "per-arnold.blaasmo@atmel.com" <per-arnold.blaasmo@atmel.com>,
"crossgcc maillist" <crossgcc@sourceware.org>
Subject: RE: Announcing `autocrossgen'
Date: Thu, 23 Oct 2014 17:40:00 -0000 [thread overview]
Message-ID: <F9C551623D2CBB4C9488801D14F864C698E46AE7@ex-mb1.corp.adtran.com> (raw)
In-Reply-To: <6438291414055216@web11m.yandex.ru>
> -----Original Message-----
> From: crossgcc-owner@sourceware.org [mailto:crossgcc-owner@sourceware.org] On Behalf Of Nikita Orlov
> Sent: Thursday, October 23, 2014 4:07 AM
> To: Bryan Hundven
> Cc: per-arnold.blaasmo@atmel.com; crossgcc maillist
> Subject: Re: Announcing `autocrossgen'
>
> I see. Thanks! Maybe you can advice me some tool for such task?
>
Nikita,
Assuming your question was:
Can you give me advice on a tool that would build me a native toolchain
for Arm?
The answer to this would be: Currently, there is nothing that will do
this for you. Older versions of BuildRoot (pre 2013) would build you a
toolchain for the target, but this support has been removed. Having
said this, you can build gcc against your cross-toolchain and make it
work the right way for the target. At that point, it would be a great
idea for you to natively build (assuming the cross-built gcc you have
works) gcc again for the target (this will ensure that gcc has the
correct paths associated with it - which can be a problem when building
some things).
If your target is supported in BuildRoot-2012.02, then you should be
able to select legacy options and choose to build each component of a
toolchain through the menu options.
Good luck!
Andy
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2014-10-23 17:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 2:58 Bryan Hundven
2014-10-23 7:36 ` Per Arnold Blaasmo
2014-10-23 7:41 ` Bryan Hundven
2014-10-23 7:58 ` Bryan Hundven
2014-10-23 8:18 ` Nikita Orlov
2014-10-23 8:27 ` Bryan Hundven
2014-10-23 9:07 ` Nikita Orlov
2014-10-23 17:40 ` ANDY KENNEDY [this message]
2014-10-23 9:18 ` Bryan Hundven
2014-10-23 18:49 ` Thomas Petazzoni
2014-10-23 19:50 ` Bryan Hundven
2014-11-10 2:10 ` Bryan Hundven
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=F9C551623D2CBB4C9488801D14F864C698E46AE7@ex-mb1.corp.adtran.com \
--to=andy.kennedy@adtran.com \
--cc=bryanhundven@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=nikitos1550@yandex.ru \
--cc=per-arnold.blaasmo@atmel.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).