From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/libupnp18: add upstream patch to fix runtime crash with musl
Date: Sat, 18 May 2019 23:32:42 +0200 [thread overview]
Message-ID: <20190518233242.5d5880ff@windsurf> (raw)
In-Reply-To: <20190509110438.31340-2-joerg.krause@embedded.rocks>
On Thu, 9 May 2019 13:04:38 +0200
J?rg Krause <joerg.krause@embedded.rocks> wrote:
> Applications build with a musl 1.1.20+ toolchain and linked with libupnpp will
> crash at runtime with `Illegal instruction` as musl is more strict with
> trying to detach an already detached thread resulting in undefined
> behaviour.
>
> Upstream status:
> https://github.com/mrjimenez/pupnp/issues/102
>
> Backported from:
> https://github.com/mrjimenez/pupnp/commit/04b454f693d0c71336252380d08f1d02967e133e
>
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
> ...tach-detached-thread-the-result-is-u.patch | 39 +++++++++++++++++++
> 1 file changed, 39 insertions(+)
> create mode 100644 package/libupnp18/0002-Do-not-try-to-detach-detached-thread-the-result-is-u.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-18 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 11:04 [Buildroot] [PATCH 1/2] package/libupnp18: needs host-pkgconf Jörg Krause
2019-05-09 11:04 ` [Buildroot] [PATCH 2/2] package/libupnp18: add upstream patch to fix runtime crash with musl Jörg Krause
2019-05-18 21:32 ` Thomas Petazzoni [this message]
2019-06-06 7:35 ` Peter Korsgaard
2019-05-18 21:32 ` [Buildroot] [PATCH 1/2] package/libupnp18: needs host-pkgconf Thomas Petazzoni
2019-06-06 7:35 ` 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=20190518233242.5d5880ff@windsurf \
--to=thomas.petazzoni@bootlin.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