From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] BR + CT-NG integration
Date: Tue, 22 Dec 2009 09:31:16 -0300 [thread overview]
Message-ID: <4B30BC14.3050207@zacarias.com.ar> (raw)
In-Reply-To: <200912212351.11487.yann.morin.1998@anciens.enib.fr>
Yann E. MORIN wrote:
> So, on the overall, it's not that bad. Crosstool-NG brings in four archs
> that buildroot has no support for, while it is missing five archs. For
> some archs, some work in CT-NG is still needed to support some variants.
The CRIS architecture is somewhat going to vanish since Axis won't be
selling/supporting the chips publically any longer. Peter might want to
drop it soonish.
I also doubt it's in working order at the moment either.
For a precise timeline of Axis's plans you can see
http://www.axis.com/products/dev/index.htm
Regards.
next prev parent reply other threads:[~2009-12-22 12:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 22:51 [Buildroot] BR + CT-NG integration Yann E. MORIN
2009-12-22 8:31 ` Anders Darander
2009-12-22 9:10 ` Yann E. MORIN
2009-12-22 10:50 ` Anders Darander
2009-12-22 12:31 ` Gustavo Zacarias [this message]
2009-12-22 12:37 ` Will Newton
2009-12-22 12:44 ` Gustavo Zacarias
2009-12-22 20:34 ` Peter Korsgaard
2009-12-22 20:47 ` Yann E. MORIN
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=4B30BC14.3050207@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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