All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denys@ti.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [morty-next][PATCH 1/2] kselftests: add libpcap-ng dependency
Date: Fri, 17 Mar 2017 15:04:05 -0400	[thread overview]
Message-ID: <20170317190405.GC14484@edge> (raw)
In-Reply-To: <CAMKF1so20TiHmt6Q778jhYoc0CFGWudoHN=VF3TPJo5daQquTA@mail.gmail.com>

On Fri, Mar 17, 2017 at 11:57:04AM -0700, Khem Raj wrote:
> On Fri, Mar 17, 2017 at 10:14 AM, Fathi Boudra <fathi.boudra@linaro.org> wrote:
> > On 17 March 2017 at 19:06, Denys Dmytriyenko <denis@denix.org> wrote:
> >> On Fri, Mar 17, 2017 at 07:03:55PM +0200, Fathi Boudra wrote:
> >>> On 17 March 2017 at 18:59, Denys Dmytriyenko <denis@denix.org> wrote:
> >>> > On Fri, Mar 17, 2017 at 04:47:59PM +0000, Khem Raj wrote:
> >>> >> On Fri, Mar 17, 2017 at 9:37 AM Fathi Boudra <fathi.boudra@linaro.org>
> >>> >> wrote:
> >>> >>
> >>> >> > libpcap-ng is required to build capabilities tests.
> >>> >> >
> >>> >> > Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
> >>> >> > ---
> >>> >> >  recipes-kernel/kselftests/kselftests_4.9.bb | 4 +---
> >>> >> >  1 file changed, 1 insertion(+), 3 deletions(-)
> >>> >> >
> >>> >> > diff --git a/recipes-kernel/kselftests/kselftests_4.9.bb
> >>> >> > b/recipes-kernel/kselftests/kselftests_4.9.bb
> >>> >> > index a7b4ba67..dd94a65b 100644
> >>> >> > --- a/recipes-kernel/kselftests/kselftests_4.9.bb
> >>> >> > +++ b/recipes-kernel/kselftests/kselftests_4.9.bb
> >>> >> > @@ -11,7 +11,7 @@ S = "${WORKDIR}/linux-${PV}"
> >>> >> >
> >>> >> >  PACKAGE_ARCH = "${MACHINE_ARCH}"
> >>> >> >
> >>> >> > -DEPENDS = "libcap popt rsync-native"
> >>> >> > +DEPENDS = "libcap libcap-ng popt rsync-native"
> >>> >>
> >>> >>
> >>> >> Would ng replace old libcap
> >>> >
> >>> > Are you asking in general or in this particular case?
> >>> >
> >>> > kselftests-capabilities does use libcap-ng and includes cap-ng.h header file,
> >>> > as I mentioned here:
> >>> > https://lists.yoctoproject.org/pipermail/meta-ti/2017-March/009766.html
> >>> >
> >>> > Fathi's fix is indeed better, even though adding another dependency.
> >>>
> >>> In this particular case, it doesn't replace libcap.
> >>> Upstream managed to use libcap-ng in capabilities test and libpcap in
> >>> bpf test...
> >>> I'm currently queuing patches for upstream.
> >>
> >> What the status of the old libcap? Is it being deprecated everywhere?
> >
> > The traditional libcap is still mainly used. I don't think it's going
> > to be deprecated soon, systemd is using it for example.
> >
> 
> can both libs live together without stepping on each other ?

FWIW, I haven't tested on all platforms yet (still crunching), but the initial 
results I'm getting here show no build, stage or run-time issues with images 
that include both kselftests and systemd...

-- 
Denys


  reply	other threads:[~2017-03-17 19:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-17 16:36 [morty-next][PATCH 1/2] kselftests: add libpcap-ng dependency Fathi Boudra
2017-03-17 16:36 ` [morty-next][PATCH 2/2] kselftests: fix seccomp test build failure Fathi Boudra
2017-03-17 16:47 ` [morty-next][PATCH 1/2] kselftests: add libpcap-ng dependency Khem Raj
2017-03-17 16:59   ` Denys Dmytriyenko
2017-03-17 17:03     ` Fathi Boudra
2017-03-17 17:06       ` Denys Dmytriyenko
2017-03-17 17:14         ` Fathi Boudra
2017-03-17 18:57           ` Khem Raj
2017-03-17 19:04             ` Denys Dmytriyenko [this message]
2017-03-17 19:12               ` Khem Raj
2017-03-17 20:08                 ` Denys Dmytriyenko
2017-03-17 22:26                   ` Khem Raj
2017-03-17 17:04 ` Denys Dmytriyenko
2017-03-17 17:09   ` Fathi Boudra
2017-03-17 18:07     ` Denys Dmytriyenko

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=20170317190405.GC14484@edge \
    --to=denys@ti.com \
    --cc=meta-ti@yoctoproject.org \
    --cc=raj.khem@gmail.com \
    /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.