From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] libcap2: add libpam to DEPENDS
Date: Thu, 13 Jan 2011 14:29:16 -0700 [thread overview]
Message-ID: <4D2F6EAC.40209@mentor.com> (raw)
In-Reply-To: <1294953575-30765-1-git-send-email-obi@opendreambox.org>
On 01/13/2011 02:19 PM, Andreas Oberritter wrote:
> * Fixes the following compile error:
>
> pam_cap.c:19:34: error: security/pam_modules.h: No such file or
> directory
> pam_cap.c:20:34: error: security/_pam_macros.h: No such file or
> directory
>
> Signed-off-by: Andreas Oberritter<obi@opendreambox.org>
> CC: Frans Meulenbroeks<fransmeulenbroeks@gmail.com>
Possible to use the pam DISTRO_FEATURE?
> ---
> recipes/libcap/libcap2_2.16.bb | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/recipes/libcap/libcap2_2.16.bb b/recipes/libcap/libcap2_2.16.bb
> index 97b03d5..be0788e 100644
> --- a/recipes/libcap/libcap2_2.16.bb
> +++ b/recipes/libcap/libcap2_2.16.bb
> @@ -2,8 +2,8 @@ DESCRIPTION = "Libcap is a library for getting and setting POSIX.1e (formerly PO
> PRIORITY = "optional"
> SECTION = "libs"
> LICENSE = "GPL"
> -DEPENDS = "bison-native flex-native attr"
> -PR = "r2"
> +DEPENDS = "bison-native flex-native attr libpam"
> +PR = "r3"
>
> BUILD_CFLAGS += "-I${S}/libcap/include"
> CFLAGS += "-I${S}/libcap/include"
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-01-13 21:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 21:19 [PATCH] libcap2: add libpam to DEPENDS Andreas Oberritter
2011-01-13 21:25 ` Otavio Salvador
2011-01-13 21:29 ` Tom Rini [this message]
2011-01-13 22:24 ` [PATCH] libcap2: fix build with and without libpam Andreas Oberritter
2011-01-13 23:57 ` Khem Raj
2011-01-14 1:41 ` [PATCH v3] " Andreas Oberritter
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=4D2F6EAC.40209@mentor.com \
--to=tom_rini@mentor.com \
--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.