From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/libupnp18: bump to version 1.8.5
Date: Thu, 14 Nov 2019 09:58:08 +0100 [thread overview]
Message-ID: <20191114095808.38abb979@windsurf> (raw)
In-Reply-To: <20191104140151.14746-1-joerg.krause@embedded.rocks>
Hello J?rg,
On Mon, 4 Nov 2019 15:01:50 +0100
J?rg Krause <joerg.krause@embedded.rocks> wrote:
> Drop patches included in new version. No need for autoreconf anymore.
>
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
> ...-configure.ac-fix-build-with-openssl.patch | 51 -------------------
> ...tach-detached-thread-the-result-is-u.patch | 39 --------------
> package/libupnp18/libupnp18.hash | 6 +--
> package/libupnp18/libupnp18.mk | 4 +-
> 4 files changed, 4 insertions(+), 96 deletions(-)
> delete mode 100644 package/libupnp18/0001-configure.ac-fix-build-with-openssl.patch
> delete mode 100644 package/libupnp18/0002-Do-not-try-to-detach-detached-thread-the-result-is-u.patch
This version bump broke the build of the gerbera package:
http://autobuild.buildroot.net/?reason=gerbera%
Reverting libupnp18 to 1.8.4 fixes the gerbera build issue.
Could you have a look ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-11-14 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 14:01 [Buildroot] [PATCH] package/libupnp18: bump to version 1.8.5 Jörg Krause
2019-11-04 14:01 ` [Buildroot] [PATCH] package/libupnpp: bump to version 0.17.2 Jörg Krause
2019-11-04 20:59 ` Thomas Petazzoni
2019-11-04 20:59 ` [Buildroot] [PATCH] package/libupnp18: bump to version 1.8.5 Thomas Petazzoni
2019-11-14 8:58 ` Thomas Petazzoni [this message]
2019-11-18 7:34 ` Jörg Krause
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=20191114095808.38abb979@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