From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/cups: fix static linking with GnuTLS
Date: Sun, 3 Jul 2016 12:44:34 +0200 [thread overview]
Message-ID: <20160703124434.342effb4@free-electrons.com> (raw)
In-Reply-To: <1456675640-22176-1-git-send-email-joerg.krause@embedded.rocks>
Hello,
On Sun, 28 Feb 2016 17:07:20 +0100, J?rg Krause wrote:
> cups forgets to link against the libs found by pkg-config if it is build with
> GnuTLS support.
>
> Otherwise, static build fails with:
> ../cups/libcups.a(tls.o): In function `http_gnutls_create_credential':
> cups-2.1.2/cups/tls-gnutls.c:762: undefined reference to `gnutls_x509_crt_init'
> [..]
>
> Fixes:
> http://autobuild.buildroot.net/results/205/20509b7d1edc73dc2a7622f2ae7dbf9f6665a918/
> http://autobuild.buildroot.net/results/b86/b86d685caf8cf812f9505fca2de36fb8c18baee1/
>
> Patch is sent upstream.
>
> Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> ---
> .../cups/0004-Fix-static-linking-with-GnuTLS.patch | 39 ++++++++++++++++++++++
> 1 file changed, 39 insertions(+)
> create mode 100644 package/cups/0004-Fix-static-linking-with-GnuTLS.patch
In the end, since nobody ever worked on a better solution, I applied
your patch (together with a bump to cups 2.1.4).
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-07-03 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 16:07 [Buildroot] [PATCH] package/cups: fix static linking with GnuTLS Jörg Krause
2016-02-28 22:00 ` Thomas Petazzoni
2016-03-01 22:54 ` Arnout Vandecappelle
2016-03-02 8:13 ` Thomas Petazzoni
2016-07-03 10:44 ` 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=20160703124434.342effb4@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