From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/cups: fix static linking with GnuTLS
Date: Sun, 28 Feb 2016 23:00:22 +0100 [thread overview]
Message-ID: <20160228230022.3d8805d6@free-electrons.com> (raw)
In-Reply-To: <1456675640-22176-1-git-send-email-joerg.krause@embedded.rocks>
Dear J?rg Krause,
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.
If this was true, then it would not only fail in static linking
scenarios, but also in dynamic linking scenarios.
What apparently is happening is that libcups.so is properly linked
against libgnutls.so, so that when you link a binary against
libcups.so, everything works fine.
However, when you switch to static linking, this doesn't work, because
library dependencies are not recursively taken into account.
While your fix probably works (I haven't tested it), it has the
drawback of linking the cups binaries directly with libgnutls.so even
in a dynamic linking scenario, while this is not really needed.
This is normally fixed with pkg-config by using the Libs.private field,
but here we are *inside* a given package, so the pkg-config files have
not yet been installed by the time we link the cups binaries.
I think this problem is normally handled by libtool, but since cups is
using only autoconf and not automake/libtool... Maybe we should consult
with the cups developers?
Arnout, Yann, do you have other advises?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-28 22:00 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 [this message]
2016-03-01 22:54 ` Arnout Vandecappelle
2016-03-02 8:13 ` Thomas Petazzoni
2016-07-03 10:44 ` Thomas Petazzoni
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=20160228230022.3d8805d6@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