From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/minidlna: unavailable for static builds
Date: Sun, 20 Mar 2016 15:36:38 +0100 [thread overview]
Message-ID: <20160320153638.6be4f246@free-electrons.com> (raw)
In-Reply-To: <1458380622-28765-1-git-send-email-bernd.kuhls@t-online.de>
Hello,
On Sat, 19 Mar 2016 10:43:42 +0100, Bernd Kuhls wrote:
> minidlna has long standing issues with static-only builds:
> http://patchwork.ozlabs.org/patch/501844/
> http://patchwork.ozlabs.org/patch/506310/
>
> This patch fixes
> http://autobuild.buildroot.net/results/d73/d7370d0f8d1c7c028996feab0ea4f36edbf8a698/
> http://autobuild.buildroot.net/results/575/5752be7c1820579425ba24178482ab0d6eea7b62/
> "pack_utils.c:(.text+0x9a8): multiple definition of `free_metadata'"
>
> The multiple definition can be fixed of course but instead of digging
> deeper and deeper into this mess let's disable static builds.
Fully agreed. If anyone wants to build minidlna statically, they can
work with upstream to fix this.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/minidlna/Config.in | 6 ++++--
> package/minidlna/minidlna.mk | 9 ---------
> 2 files changed, 4 insertions(+), 11 deletions(-)
Applied to master, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-03-20 14:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 9:43 [Buildroot] [PATCH 1/1] package/minidlna: unavailable for static builds Bernd Kuhls
2016-03-20 14:36 ` 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=20160320153638.6be4f246@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