From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2 v2] xtensa: add support for the Xtensa architecture
Date: Sat, 10 Nov 2012 10:55:34 +0100 [thread overview]
Message-ID: <20121110105534.614885e3@skate> (raw)
In-Reply-To: <509D35D3.6070607@mind.be>
On Fri, 09 Nov 2012 17:56:51 +0100, Arnout Vandecappelle wrote:
> I get these same error with the default bfin config, and it also breaks
> with BR2_PTHREADS_NONE=y
Right, I should fix the Blackfin architecture so it uses the external
toolchain instead. I don't think gcc/uclibc/binutils have upstream the
needed code to build a Blackfin toolchain. We could certainly point
Buildroot to the Blackfin specific gcc/uclibc/binutils repositories, if
someone has a usage for the internal backend on Blackfin.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-11-10 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 6:33 [Buildroot] [PATCH 1/2 v2] xtensa: add support for the Xtensa architecture Chris Zankel
2012-11-09 9:19 ` Thomas Petazzoni
2012-11-09 9:34 ` Thomas Petazzoni
2012-11-09 16:56 ` Arnout Vandecappelle
2012-11-10 9:55 ` Thomas Petazzoni [this message]
2012-11-09 18:34 ` Chris Zankel
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=20121110105534.614885e3@skate \
--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