From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] Add libcap-ng package.
Date: Thu, 5 Apr 2012 09:27:57 +0200 [thread overview]
Message-ID: <20120405092757.585e48c6@skate> (raw)
In-Reply-To: <20120404200933.2D85596A01@busybox.osuosl.org>
Le Wed, 4 Apr 2012 21:57:47 +0200,
Peter Korsgaard <jacmet@sunsite.dk> a ?crit :
> --- /dev/null
> +++ b/package/libcap-ng/Config.in
> @@ -0,0 +1,10 @@
> +config BR2_PACKAGE_LIBCAP_NG
> + bool "libcap-ng"
> + help
> + The libcap-ng library is intended to make programming with
> + posix capabilities much easier than the traditional libcap
> + library. It includes utilities that can analyse all currently
> + running applications and print out any capabilities and whether
> + or not it has an open ended bounding set.
> +
> + http://people.redhat.com/sgrubb/libcap-ng/
This new package should probably depends on BR2_LARGEFILE, or get some
sort of fix for largefile support. See:
http://autobuild.buildroot.org/results/7aab0aecc3a49b55d65f168bb2a7165bcfc62acb/build-end.log
http://autobuild.buildroot.org/results/22ec96b9a821c89ebba804f71b97707718038549/build-end.log
http://autobuild.buildroot.org/results/15d94ece63b89517d8d896785fec5085a573e740/build-end.log
http://autobuild.buildroot.org/results/b76c3195656fa96ffa8446ac03bde51690a4dc90/build-end.log
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-04-05 7:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 19:57 [Buildroot] [git commit] Add libcap-ng package Peter Korsgaard
2012-04-05 7:27 ` Thomas Petazzoni [this message]
2012-04-05 7:49 ` Peter Korsgaard
2012-04-05 8:04 ` 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=20120405092757.585e48c6@skate \
--to=thomas.petazzoni@free-electrons.com \
--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