From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libmicrohttpd: update to 0.9.51
Date: Fri, 7 Oct 2016 18:54:52 +0200 [thread overview]
Message-ID: <20161007165452.GL2052@waldemar-brodkorb.de> (raw)
In-Reply-To: <20161007160432.635dc932@free-electrons.com>
Hi,
Thomas Petazzoni wrote,
> Hello,
>
> On Sat, 1 Oct 2016 12:01:02 +0200, Waldemar Brodkorb wrote:
> > Bfin workaround is not required if the gcc bfin patch is applied.
> > (gcc: enable _REENTRANT for bfin when -lpthread is used)
> >
> > Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
>
> I initially applied this patch, but immediately reverted it after I
> realized it was breaking a valid situation: you're breaking the build
> with the Blackfin external toolchains.
Okay. I always forget about the external toolchains.
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.
> In addition to this, this patch is mixing a version bump, with removing
> some work-arounds, which are unrelated to the version bump.
The removal of the workround worked only in the latest version for
me.
> So I've marked this patch as Rejected in patchwork. Please resend a
> patch that does just the version bump, and leaves the work-around in
> place.
Okay. But I think version bumps are made mostly from other
developers, I just needed it to remove the workaround.
Sorry I should have mentioned that in the commit log.
best regards
Waldemar
next prev parent reply other threads:[~2016-10-07 16:54 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 [this message]
2016-10-07 20:02 ` 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=20161007165452.GL2052@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 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.