From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libmicrohttpd: update to 0.9.51
Date: Fri, 7 Oct 2016 22:02:46 +0200 [thread overview]
Message-ID: <20161007220246.3af42e98@free-electrons.com> (raw)
In-Reply-To: <20161007165452.GL2052@waldemar-brodkorb.de>
Hello,
On Fri, 7 Oct 2016 18:54:52 +0200, Waldemar Brodkorb wrote:
> Are there any plans to remove this very old toolchain?
> One of my motivation of getting internal bfin toolchain in a good
> shape was the possibility to remove the old toolchain to get rid
> of many package failures regarding the very old uClibc.
Right. What's the state of things with the new toolchain? Are C++
applications now working fine on the target? Are there any other known
issues?
I guess we probably want to keep the Blackfin ADI toolchains around for
a cycle or two, and then get rid of them.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-10-07 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-01 10:01 [Buildroot] [PATCH] libmicrohttpd: update to 0.9.51 Waldemar Brodkorb
2016-10-07 14:04 ` Thomas Petazzoni
2016-10-07 16:54 ` Waldemar Brodkorb
2016-10-07 20:02 ` Thomas Petazzoni [this message]
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=20161007220246.3af42e98@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