From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Blackfin Buildroot toolchain issue
Date: Tue, 17 Mar 2015 15:43:54 +0100 [thread overview]
Message-ID: <20150317154354.34f4d39d@free-electrons.com> (raw)
In-Reply-To: <55083CDE.7040007@zacarias.com.ar>
Hello,
On Tue, 17 Mar 2015 11:40:30 -0300, Gustavo Zacarias wrote:
> Back when i enabled it, the ADI toolchain gcc was pretty old compared to
> what we got with this.
> But newer gcc versions are broken, and although it may be something
> simple to fix, i'm not inclined to dig further.
Yeah, me neither.
> So it's probably best to just disable it, after all if someone wants to
> throw some time into fixing it, it's just a line away from re-enabling
> it and doing so.
Yes, I believe it's the sanest / easiest solution. Can you send a patch
to disable Blackfin in the internal toolchain backend ?
I'll remove the Buildroot generated Blackfin external toolchain from
the autobuilders.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-17 14:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-15 21:17 [Buildroot] Blackfin Buildroot toolchain issue Thomas Petazzoni
2015-03-15 21:18 ` Thomas Petazzoni
2015-03-17 14:20 ` Gustavo Zacarias
2015-03-17 14:30 ` Thomas Petazzoni
2015-03-17 15:08 ` Gustavo Zacarias
2015-03-17 15:13 ` Thomas Petazzoni
2015-03-17 17:55 ` Gustavo Zacarias
2015-03-17 21:34 ` Waldemar Brodkorb
2015-03-17 21:55 ` Thomas Petazzoni
2015-03-17 23:00 ` Waldemar Brodkorb
2015-03-17 13:45 ` Gustavo Zacarias
2015-03-17 13:49 ` Thomas Petazzoni
2015-03-17 14:40 ` Gustavo Zacarias
2015-03-17 14:43 ` Thomas Petazzoni [this message]
2015-03-17 16:41 ` Gustavo Zacarias
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=20150317154354.34f4d39d@free-electrons.com \
--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