From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/4] libcap-ng: Allow host compilation.
Date: Sat, 16 Jul 2016 15:57:27 +0200 [thread overview]
Message-ID: <20160716155727.04d3fe81@free-electrons.com> (raw)
In-Reply-To: <1468518424-11785-2-git-send-email-Aduskett@gmail.com>
Hello,
On Thu, 14 Jul 2016 13:47:02 -0400, Adam Duskett wrote:
> Audit may require libcap-ng as a dependency, this allows
> libcap-ng to compile as a host package.
>
> Signed-off-by: Adam Duskett <Aduskett@gmail.com>
> ---
> package/libcap-ng/libcap-ng.mk | 4 ++++
> 1 file changed, 4 insertions(+)
Following my comments on PATCH 1/4, not sure if this patch is still
needed. If it is still needed, then this patch must appear *before* it
is used.
Imagine I apply only PATCH 1/4, but not PATCH 2/4: PATCH 1/4 might lead
to host-libcap-ng being used, but this package doesn't exist.
Please make sure that the *order* of the patches in your series is
correct.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-16 13:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 17:47 [Buildroot] [PATCH 1/4] package/audit: Allow Host compilation Adam Duskett
2016-07-14 17:47 ` [Buildroot] [PATCH 2/4] libcap-ng: Allow host compilation Adam Duskett
2016-07-16 13:57 ` Thomas Petazzoni [this message]
2016-07-14 17:47 ` [Buildroot] [PATCH 3/4] package/libsemanage: Add host-audit as a dependency Adam Duskett
2016-07-15 3:41 ` Baruch Siach
2016-07-15 16:45 ` Adam Duskett
2016-07-16 13:58 ` Thomas Petazzoni
2016-07-14 17:47 ` [Buildroot] [v13, 4/4] policycoreutils: new package Adam Duskett
2016-07-16 13:55 ` [Buildroot] [PATCH 1/4] package/audit: Allow Host compilation 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=20160716155727.04d3fe81@free-electrons.com \
--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