From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] taskd: add patch for correct gnutls libraries in static build
Date: Mon, 21 Nov 2016 21:19:58 +0100 [thread overview]
Message-ID: <20161121211958.22df4922@free-electrons.com> (raw)
In-Reply-To: <20161120230217.13881-1-arnout@mind.be>
Hello,
On Mon, 21 Nov 2016 00:02:17 +0100, Arnout Vandecappelle
(Essensium/Mind) wrote:
> The CMakeLists.txt was using the wrong variables names to add to
> includes and libs, so the additional libraries for static build
> weren't added to the link command.
>
> Patch sent upstream to taskwarrior-dev at googlegroups.com but it doesn't
> seem to be very active.
>
> Fixes:
> http://autobuild.buildroot.net/results/d01e947fa807336ffcfd0fad27397af8e7442833
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> ...se-correct-variables-for-GnuTLS-detection.patch | 32 ++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
> create mode 100644 package/taskd/0002-Use-correct-variables-for-GnuTLS-detection.patch
Regardless of the feedback from upstream which says it's an upstream
CMake bug, I've nonetheless applied to fix the immediate problem.
Would indeed be good if Samuel could have a look, and take this
upstream to the CMake developers.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-11-21 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-20 23:02 [Buildroot] [PATCH] taskd: add patch for correct gnutls libraries in static build Arnout Vandecappelle
2016-11-21 8:57 ` Arnout Vandecappelle
2016-11-21 20:19 ` 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=20161121211958.22df4922@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