From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] libcap: Add optional support for libattr capabilities
Date: Tue, 19 Mar 2013 13:11:04 +0100 [thread overview]
Message-ID: <87a9pzwpwn.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1363690308-29680-1-git-send-email-markos.chandras@gmail.com> (Markos Chandras's message of "Tue, 19 Mar 2013 10:51:48 +0000")
>>>>> "Markos" == Markos Chandras <markos.chandras@gmail.com> writes:
Markos> From: Markos Chandras <markos.chandras@imgtec.com>
Markos> libcap can optionally link to libattr to support extra
Markos> file capabilities. Link to this library and pull it as
Markos> dependency if BR2_PACKAGE_ATTR is selected.
Markos> Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
Markos> ---
Markos> package/libcap/libcap.mk | 13 ++++++++++---
Markos> 1 files changed, 10 insertions(+), 3 deletions(-)
Markos> diff --git a/package/libcap/libcap.mk b/package/libcap/libcap.mk
Markos> index dcd3a18..87d5b85 100644
Markos> --- a/package/libcap/libcap.mk
Markos> +++ b/package/libcap/libcap.mk
Markos> @@ -15,18 +15,25 @@ LIBCAP_LICENSE_FILES = License
Markos> LIBCAP_DEPENDENCIES = host-libcap
Markos> LIBCAP_INSTALL_STAGING = YES
Markos> +ifeq ($(BR2_PACKAGE_ATTR),y)
Markos> + LIBCAP_DEPENDENCIES += attr
Markos> + HAVE_LIBATTR = yes
Markos> +else
Markos> + HAVE_LIBATTR = no
Markos> +endif
Buildroot uses a global namespace, so I renamed this to
LIBCAP_HAVE_LIBATTR and committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-03-19 12:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 10:51 [Buildroot] [PATCH v2] libcap: Add optional support for libattr capabilities Markos Chandras
2013-03-19 12:11 ` Peter Korsgaard [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=87a9pzwpwn.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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