From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] toolchain: kill ADI Blackfin toolchain
Date: Thu, 24 Nov 2016 16:21:53 +0100 [thread overview]
Message-ID: <20161124152153.GF27313@waldemar-brodkorb.de> (raw)
In-Reply-To: <20161123234035.6393-2-arnout@mind.be>
Hi Arnout,
Arnout Vandecappelle (Essensium/Mind) wrote,
> This toolchain has many problems which are fixed in contemporary gcc
> and uClibc-ng. In addition, several hacks are needed to be able to
> work with this toolchain. All these hacks are removed as well. Also
> the package exceptions for this toolchain are removed.
>
> The BR2_BFIN_INSTALL_FDPIC_SHARED and BR2_BFIN_INSTALL_FLAT_SHARED
> options don't get a legacy entry. For the ADI toolchain, there already
> is a legacy entry, so it doesn't make sense to add it twice. For other
> external toolchains, these options didn't actually work, because they
> rely on the specific layout of the ADI toolchain.
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
ACK from me. May be we convince ADI people to get more stuff fixed
upstream, when this toolchain is removed.
best regards
Waldemar
next prev parent reply other threads:[~2016-11-24 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 23:40 [Buildroot] [PATCH v2 1/2] toolchain-external: support gcc < 4.3 Arnout Vandecappelle
2016-11-23 23:40 ` [Buildroot] [PATCH v2 2/2] toolchain: kill ADI Blackfin toolchain Arnout Vandecappelle
2016-11-24 15:21 ` Waldemar Brodkorb [this message]
2016-11-25 22:01 ` Thomas Petazzoni
2016-11-25 22:00 ` [Buildroot] [PATCH v2 1/2] toolchain-external: support gcc < 4.3 Thomas Petazzoni
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=20161124152153.GF27313@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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