On Fri, May 20, 2016 at 12:41 PM, akuster@mvista <[email protected]> wrote:

> On 5/20/16 9:33 AM, Bruce Ashfield wrote:
> > merged to master.
> >
>
> Wont this make a depends on the meta-security layer where libseccomp lives?
>

Yep. When enabled (which I have in other builds). But since it is off by
default,
I'm fine with it.

Bruce


>
> - Armin
>
>
> > Bruce
> >
> > On Fri, May 20, 2016 at 2:27 AM, <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> >     From: He Zhe <[email protected] <mailto:[email protected]>>
> >
> >     "WARNING: QA Issue: qemu rdepends on libseccomp, but it isn't a build
> >     dependency? [build-deps]"
> >
> >     Currently qemu itself checks and links with libsecomp(if version >=
> >     2.1.1)
> >     for x86 and x86-64, since it is not specified in configure, and
> >     causes the
> >     above warning.
> >
> >     This patch adds packageconfig for libseccomp and set it disabled as
> >     default.
> >     This feature can be enabled whenever libseccomp exists and is needed.
> >
> >     Signed-off-by: He Zhe <[email protected]
> >     <mailto:[email protected]>>
> >     ---
> >      meta-openstack/recipes-devtools/qemu/qemu_2.%.bbappend | 1 +
> >      1 file changed, 1 insertion(+)
> >
> >     diff --git a/meta-openstack/recipes-devtools/qemu/qemu_2.%.bbappend
> >     b/meta-openstack/recipes-devtools/qemu/qemu_2.%.bbappend
> >     index ca8274e..9d774c4 100644
> >     --- a/meta-openstack/recipes-devtools/qemu/qemu_2.%.bbappend
> >     +++ b/meta-openstack/recipes-devtools/qemu/qemu_2.%.bbappend
> >     @@ -1,4 +1,5 @@
> >      PACKAGECONFIG[spice] = "--enable-spice,--disable-spice,spice,"
> >     +PACKAGECONFIG[libseccomp] =
> >     "--enable-seccomp,--disable-seccomp,libseccomp,libseccomp"
> >
> >      PACKAGECONFIG ?= "fdt spice virtfs libcap-ng"
> >      PACKAGECONFIG_class-native = "fdt"
> >     --
> >     1.9.1
> >
> >     --
> >     _______________________________________________
> >     meta-virtualization mailing list
> >     [email protected]
> >     <mailto:[email protected]>
> >     https://lists.yoctoproject.org/listinfo/meta-virtualization
> >
> >
> >
> >
> > --
> > "Thou shalt not follow the NULL pointer, for chaos and madness await
> > thee at its end"
> >
> >
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"
-- 
_______________________________________________
meta-virtualization mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-virtualization

Reply via email to