From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] external toolchain
Date: Tue, 1 Dec 2009 15:33:15 +0100 [thread overview]
Message-ID: <20091201153315.210f2e33@surf> (raw)
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAAHWPmCJoh6pNraKNfwnUAkLCgAAAEAAAAJsvlB0+B11LmskjkLHLmJkBAAAAAA==@cimeq.qc.ca>
Le Tue, 1 Dec 2009 08:59:46 -0500,
"Jonathan dumaresq" <jdumaresq@cimeq.qc.ca> a ?crit :
> Does any one here have used the crosstoll-ng for AVR32 with
> buildroot ?
The AVR32 support in Crosstool-NG is bare-meta only (based on newlib).
So such a toolchain cannot be used in Buildroot. You'd first have to
contribute to Crosstool-NG to add support for uClibc and/or glibc.
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2009-12-01 14:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 13:59 [Buildroot] external toolchain Jonathan dumaresq
2009-12-01 14:33 ` Thomas Petazzoni [this message]
2009-12-01 14:38 ` Jonathan dumaresq
2009-12-01 14:49 ` Peter Korsgaard
2009-12-01 15:32 ` Jonathan dumaresq
2009-12-01 15:34 ` Peter Korsgaard
2009-12-01 20:16 ` Jonathan dumaresq
2009-12-01 20:32 ` Peter Korsgaard
2009-12-01 20:53 ` Jonathan dumaresq
-- strict thread matches above, loose matches on Subject: below --
2012-08-19 18:46 Zoran Djordjevic
2012-08-18 7:33 Zoran Djordjevic
2012-08-18 9:47 ` Yann E. MORIN
2012-08-17 12:47 Zoran Djordjevic
2012-08-17 13:19 ` Yann E. MORIN
2012-08-17 18:05 ` Zoran Djordjevic
2011-04-10 1:39 [Buildroot] External Toolchain Charles Krinke
2009-03-25 22:14 [Buildroot] External toolchain H Hartley Sweeten
2009-03-25 23:36 ` Daniel Mack
2009-03-25 23:45 ` H Hartley Sweeten
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=20091201153315.210f2e33@surf \
--to=thomas.petazzoni@free-electrons.com \
--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