Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libcap: add native BBCLASSEXTEND to fix gnutls-native after ffc32d6436bcd11bd9a431affb9d2508fdb3992e
Date: Fri, 27 May 2011 13:17:29 +0100	[thread overview]
Message-ID: <1306498649.27470.261.camel@rex> (raw)
In-Reply-To: <1306486749-17889-1-git-send-email-Martin.Jansa@gmail.com>

On Fri, 2011-05-27 at 10:59 +0200, Martin Jansa wrote:
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
>  meta/recipes-support/libcap/libcap.inc |    4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/meta/recipes-support/libcap/libcap.inc b/meta/recipes-support/libcap/libcap.inc
> index 292fa78..1b4c0bc 100644
> --- a/meta/recipes-support/libcap/libcap.inc
> +++ b/meta/recipes-support/libcap/libcap.inc
> @@ -6,6 +6,8 @@ LICENSE = "BSD | GPL"
>  LIC_FILES_CHKSUM = "file://License;md5=731de803c1ccbcb05a9b3523279c8d7f"
>  
>  DEPENDS = "libpam attr perl-native"
> +# attr and pam are disabled by EXTRA_OEMAKE_virtclass-native
> +DEPENDS_virtclass-native = "perl-native"
>  
>  SRC_URI = "${KERNELORG_MIRROR}/linux/libs/security/linux-privs/libcap2/${BPN}-${PV}.tar.bz2"
>  
> @@ -32,3 +34,5 @@ do_install() {
>  # pam files
>  FILES_${PN} += "${libdir}/security/*.so"
>  FILES_${PN}-dbg += "${libdir}/security/.debug/*.so"
> +
> +BBCLASSEXTEND = "native"

Applied to master, thanks.

Richard




      reply	other threads:[~2011-05-27 12:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27  8:59 [PATCH] libcap: add native BBCLASSEXTEND to fix gnutls-native after ffc32d6436bcd11bd9a431affb9d2508fdb3992e Martin Jansa
2011-05-27 12:17 ` Richard Purdie [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=1306498649.27470.261.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox