From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] gcc: remove 4.5.x
Date: Wed, 24 Feb 2016 17:26:22 -0300 [thread overview]
Message-ID: <56CE11EE.6020501@zacarias.com.ar> (raw)
In-Reply-To: <87io1d3mhr.fsf@dell.be.48ers.dk>
On 24/02/16 17:02, Peter Korsgaard wrote:
> This doesn't apply (seems like you you don't have the commit adding the
> A17 ARM variant), and you forgot to remove our gcc patches.
>
> What do we do with our 4.5 based external toolchains and
> BR2_TOOLCHAIN_GCC_AT_LEAST_4_5 (used by directfb)?
>
> Care to send a v2?
Sure.
I normally pile up on master since the next branch doesn't last much.
Regards.
next prev parent reply other threads:[~2016-02-24 20:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 18:00 [Buildroot] [PATCH 1/2] gcc: mark 4.7.x as deprecated Gustavo Zacarias
2016-02-24 18:00 ` [Buildroot] [PATCH 2/2] gcc: remove 4.5.x Gustavo Zacarias
2016-02-24 20:02 ` Peter Korsgaard
2016-02-24 20:26 ` Gustavo Zacarias [this message]
2016-02-25 9:48 ` Thomas Petazzoni
2016-02-25 9:57 ` Peter Korsgaard
2016-02-25 10:03 ` Thomas Petazzoni
2016-02-25 10:53 ` Gustavo Zacarias
2016-02-25 12:43 ` Thomas Petazzoni
2016-02-25 12:48 ` Gustavo Zacarias
2016-02-24 19:59 ` [Buildroot] [PATCH 1/2] gcc: mark 4.7.x as deprecated Peter Korsgaard
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=56CE11EE.6020501@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