All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [meta-oe][PATCH] openldap: fix build against gnutls3
Date: Wed, 7 May 2014 18:48:44 +0200	[thread overview]
Message-ID: <20140507164844.GF30955@jama> (raw)
In-Reply-To: <6062362.lpz6Qfmmsr@peggleto-mobl5.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]

On Wed, May 07, 2014 at 09:57:52AM +0100, Paul Eggleton wrote:
> On Wednesday 07 May 2014 10:29:21 Koen Kooi wrote:
> > Khem Raj schreef op 07-05-14 09:47:
> > > On Tue, May 6, 2014 at 11:53 PM, Koen Kooi <koen.kooi@linaro.org> wrote:
> > >> ++                              TLS_LIBS="-lgnutls -lgcrypt"
> > > 
> > > Does this mean we need something more in DEPENDS or DEPENDS part of
> > > PACKAGECONFIG too ?
> > 
> > Should be automatic since gnutls depends on it. It's not a new dependency.
> 
> BitBake does not automatically ensure dependencies-of-dependencies are in the 
> sysroot. They almost always will be, but I have seen failures in these kinds 

Are you sure it doesn't?

But I'm also in favor of specifying dependencies-of-dependencies in
cases where the recipe configure task explicitly check for them (so that
when the required dependency is no longer included in "parent"
dependency, e.g. after moving it to PACKAGECONFIG).

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  parent reply	other threads:[~2014-05-07 16:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07  6:53 [meta-oe][PATCH] openldap: fix build against gnutls3 Koen Kooi
2014-05-07  7:47 ` Khem Raj
2014-05-07  8:29   ` Koen Kooi
2014-05-07  8:57     ` Paul Eggleton
2014-05-07  9:41       ` Koen Kooi
2014-05-07 16:48       ` Martin Jansa [this message]
2014-05-07 16:56         ` Paul Eggleton

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=20140507164844.GF30955@jama \
    --to=martin.jansa@gmail.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.