From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/transmission: Fix compilation when using system libminiupnpc with libutp disabled
Date: Wed, 27 Jul 2016 23:32:58 +0200 [thread overview]
Message-ID: <20160727233258.244d4c8b@free-electrons.com> (raw)
In-Reply-To: <20160717154436.GI3614@free.fr>
Hello,
On Sun, 17 Jul 2016 17:44:36 +0200, Yann E. MORIN wrote:
> So it means that headers from the internal libutp will always be used,
> even if an external one is found. This is probably not very good...
>
> Instead, I think the fix is probably something like:
>
> --- configure.ac(revision 14736)
> +++ configure.a c)(working copy)
> @@ -358,6 +358,10 @@
> else
> AC_MSG_ERROR("Unable to build uTP support -- C++ compiler not found")
> fi
> +else
> + # For the system libminiupnpc with UTC disabled,
> + # point to our bundled UTP headers
> + LIBUTP_CFLAGS="-I\$(top_srcdir)/third-party/"
> fi
> AC_SUBST(LIBUTP_CFLAGS)
> AC_SUBST(LIBUTP_LIBS)
> @@ -457,7 +461,7 @@
> LIBUPNP_LIBS_QT="\$\${TRANSMISSION_TOP}/third-party/miniupnp/libminiupnp.a"
> else
> AC_DEFINE([SYSTEM_MINIUPNP])
> - LIBUPNP_CFLAGS=""
> + LIBUPNP_CFLAGS="${LIBUTP_CFLAGS}"
> LIBUPNP_LIBS="-lminiupnpc"
> LIBUPNP_LIBS_QT="-lminiupnpc"
> fi
>
> Can you test and respin if OK, please? Thanks! :-)
Bernd, I'll mark your patch as Changes Requested in patchwork. Could
you respin a new version that takes into account Yann's comment?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-07-27 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 5:13 [Buildroot] [PATCH 1/1] package/transmission: Fix compilation when using system libminiupnpc with libutp disabled Bernd Kuhls
2016-07-12 16:42 ` Yann E. MORIN
2016-07-17 15:44 ` Yann E. MORIN
2016-07-27 21:32 ` 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=20160727233258.244d4c8b@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