All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/cups: fix static linking with GnuTLS
Date: Tue, 1 Mar 2016 23:54:59 +0100	[thread overview]
Message-ID: <56D61DC3.8090502@mind.be> (raw)
In-Reply-To: <20160228230022.3d8805d6@free-electrons.com>

On 02/28/16 23:00, Thomas Petazzoni wrote:
> 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?

 Well, inside a package, it's the responsibility of the package build system to
link with all required libraries (in the required order). That can either be
handled by a helper like libtool, or the Makefile should handle it manually.

 In other words: I beliver Joerg's fix is the correct one.

 Regards,
 Arnout

> 
> Arnout, Yann, do you have other advises?


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2016-03-01 22:54 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 [this message]
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=56D61DC3.8090502@mind.be \
    --to=arnout@mind.be \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.