From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] gcc: remove 4.5.x
Date: Thu, 25 Feb 2016 13:43:38 +0100 [thread overview]
Message-ID: <20160225134338.4973dffd@free-electrons.com> (raw)
In-Reply-To: <56CEDD11.7060603@zacarias.com.ar>
Dear Gustavo Zacarias,
On Thu, 25 Feb 2016 07:53:05 -0300, Gustavo Zacarias wrote:
> On 25/02/16 06:57, Peter Korsgaard wrote:
>
> > >> What do we do with our 4.5 based external toolchains and
> > >> BR2_TOOLCHAIN_GCC_AT_LEAST_4_5 (used by directfb)?
> >
> > > I think the BR2_TOOLCHAIN_GCC_AT_LEAST_* must be kept for pretty much
> > > all versions of gcc. This symbol is not related to whether we support
> > > that gcc version in our internal toolchain backend or not. Possibly any
> > > gcc version can be used with the external toolchain backend.
> >
> > True, but we might consider removing preconfigured external toolchains
> > using ancient versions if there's sensible newer alternatives available.
>
> Blackfin is 4.5.x so at least this low we must keep.
Blackfin is actually 4.3.
They have an alpha 4.5 compiler, but when we switched to it, many
things broke and the ADI guys told us to stay on 4.3.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-25 12:43 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
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 [this message]
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=20160225134338.4973dffd@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