From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RFC] Fix avr32 build using internal toolchain
Date: Sun, 20 Jan 2013 11:22:02 -0300 [thread overview]
Message-ID: <50FBFD8A.1030606@zacarias.com.ar> (raw)
In-Reply-To: <CAHt8ZCOMQR8NjrsQzcWqRz3hd2EUc+X_0osKOfn-8c=1wY59_Q@mail.gmail.com>
On 01/20/2013 10:22 AM, Simon Dawson wrote:
>> Testing and fixing is an issue on the toolchain side when there's no
>> upgrade path possible.
>
> I don't quite follow your meaning here, I'm afraid.
Some of the breakage is toolchain-related and we can't upgrade it.
Most of the time it's gcc IIRC.
Like the internal compiler errors for external toolchains, other than
blacklisting/disabling packages there's not much to do.
>> Maybe we can keep it and start marking broken packages as !BR2_avr32 ?
>> That may be a rough ride though with all the dependencies.
>
> I think that's pretty much where we are right now, isn't it?
I don't recall if that's what was agreed on the meetings (particularly
since i never went to one).
But at some point it won't be a workable compromise i'm afraid.
Regards.
next prev parent reply other threads:[~2013-01-20 14:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 22:16 [Buildroot] [PATCH RFC] Fix avr32 build using internal toolchain spdawson at gmail.com
2013-01-19 10:38 ` Thomas Petazzoni
2013-01-20 11:01 ` Simon Dawson
2013-01-20 12:54 ` Gustavo Zacarias
2013-01-20 13:22 ` Simon Dawson
2013-01-20 14:22 ` Gustavo Zacarias [this message]
2013-01-20 21:24 ` Simon Dawson
2013-01-20 14:21 ` Thomas Petazzoni
2013-01-20 21:23 ` Simon Dawson
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=50FBFD8A.1030606@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.