Re: [yocto] [PATCH 1/3] intel-media-driver: check for "opengl" feature

2019-07-29 Thread Hongxu Jia 

On 7/29/19 9:12 AM, Mittal, Anuj wrote:

Hi Hongxu

I have merged these changes but could you send these to meta-intel list
in future please?


OK, I got it

//Hongxu


On Wed, 2019-07-24 at 18:11 +0800, Hongxu Jia wrote:

Since comit [a78c420 libva: check for "opengl" feature] applied in
oe-core,
and intel-media-driver depends on libva, it should check for "opengl"
feature too.

Signed-off-by: Hongxu Jia 
---
  recipes-multimedia/libva/intel-media-driver_19.2.0.bb | 3 +++
  1 file changed, 3 insertions(+)

diff --git a/recipes-multimedia/libva/intel-media-driver_19.2.0.bb
b/recipes-multimedia/libva/intel-media-driver_19.2.0.bb
index 8656992..8084567 100644
--- a/recipes-multimedia/libva/intel-media-driver_19.2.0.bb
+++ b/recipes-multimedia/libva/intel-media-driver_19.2.0.bb
@@ -14,6 +14,9 @@ LIC_FILES_CHKSUM = "
file://LICENSE.md;md5=6aab5363823095ce682b155fef0231f0 \
  # Only for 64 bit until this is resolved:
https://github.com/intel/media-driver/issues/356
  COMPATIBLE_HOST = '(x86_64).*-linux'
  
+inherit distro_features_check

+REQUIRED_DISTRO_FEATURES = "opengl"
+
  DEPENDS += "libva gmmlib"
  
  SRC_URI = "git://github.com/intel/media-

driver.git;protocol=https;branch=intel-media-19.2 \



--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2019-07-29 Thread sjolley.yp.pm 
All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

 

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs

 

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 300
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "2.8", "2.9', "2.99" and "Future", the more pressing/urgent
issues being in "2.8" and then "2.9".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Meta-raspberrypi

2019-07-29 Thread Rudolf J Streif 
Hi Shravan,

You need to checkout warrior from your meta-raspberrypi repo that you
cloned. It looks as it is on the latest master.

:rjs

On 7/22/19 3:07 PM, Shravan Singh wrote:
> Hello All,
>
> I am trying to create a base image for raspberry-pi cm3(compute module 3)
>
> I am using warrior-21.0.1
> I downloaded meta-raspberry-pi from 
> https://git.yoctoproject.org/git/meta-raspberrypi
> I added the layer in bblayer.conf and I have changed the machine
> variable in local.conf
> to *raspberrypi-cm3*
> I am using oe-init-build script to generate the base files
>
> Now when I run the command
> bitbake core-image-base
>
> I get the below mentioned error
> Error: No recipes available for:
> /home/blue/yacto/meta-raspberrypi/recipes-bsp/u-boot/u-boot_2019.07.bbappend
> /home/blue/yacto/meta-raspberrypi/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.16%.bbappend
>
>
> Any help with this?
>
>
> Regards,
> Shravan Singh
> (239) 243-0838
>
> Blue Sparq, Inc.
> 928 NE 24th Lane unit 4 and 5.
> Cape Coral, FL 33993
>
> IMPORTANT: The contents of this email and any attachments are
> confidential. They are intended for the named recipient(s) only. If
> you have received this email by mistake, please notify the sender
> immediately and do not disclose the contents to anyone or make copies
> thereof.
>
-- 
-
Rudolf J Streif
CEO/CTO ibeeto
+1.855.442.3396 x700



signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Why does enabling initramfs pull eudev into my build?

2019-07-29 Thread Patrick Doyle 
Did that get your attention? :-)

I am trying to understand why eudev gets pulled into my build, where
it wasn't part of it before.  I recently added an initramfs to my
build by setting:

INITRAMFS_IMAGE_BUNDLE="1"

in my machine.conf file.  I have a custom, very minimal initramfs.bb
recipe that doesn't do much more than:

NO_RECOMMENDATIONS_pn-initramfs = "1"
PACKAGE_INSTALL = "${VIRTUAL-RUNTIME_base-utils} validate-rootfs"
IMAGE_FEATURES = ""
export IMAGE_BASENAME = "${MLPREFIX}initramfs"
IMAGE_FSTYPES = "${INITRAMFS_FSTYPES}"
inherit core-image

When I run:

$ bitbake base-image -g -u taskexp

I see that eudev.do_build lists "base-image.du_build" as a dependent
task and, for some reason, eudev.do_packagedata lists
"initramfs.do_roofs" as a dependent task.

When I remove INITRAMFS_IMAGE_BUNDLE from my machine.conf file, eudev
is no longer included in my image.  (Although, oddly,
initramfs.do_build is listed as a dependent task of eudev.do_build
when I run taskexp on my initramfs recipe, but not when I run it on
the base-image recipe.)

Can anybody point me at (more) tools that can help me understand what
I did to my initramfs.bb recipe that caused eudev to be included in my
build?

Thanks

--wpd
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Meta-raspberrypi

2019-07-29 Thread Khem Raj 
On Mon, Jul 29, 2019 at 2:15 AM Shravan Singh  wrote:
>
> Hello All,
>
> I am trying to create a base image for raspberry-pi cm3(compute module 3)
>
> I am using warrior-21.0.1
> I downloaded meta-raspberry-pi from  
> https://git.yoctoproject.org/git/meta-raspberrypi
> I added the layer in bblayer.conf and I have changed the machine variable in 
> local.conf
> to raspberrypi-cm3
> I am using oe-init-build script to generate the base files
>
> Now when I run the command
> bitbake core-image-base
>
> I get the below mentioned error
> Error: No recipes available for:
> /home/blue/yacto/meta-raspberrypi/recipes-bsp/u-boot/u-boot_2019.07.bbappend
> /home/blue/yacto/meta-raspberrypi/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.16%.bbappend
>
>
> Any help with this?

always post the Build Configuration printed by bitbake on top, When
you add layers ensure that the branches
match to core layer e.g. if you are using warrior release for
core/poky then use same branch checkout for
meta-raspberrypi as well.

>
>
> Regards,
> Shravan Singh
> (239) 243-0838
>
> Blue Sparq, Inc.
> 928 NE 24th Lane unit 4 and 5.
> Cape Coral, FL 33993
>
> IMPORTANT: The contents of this email and any attachments are confidential. 
> They are intended for the named recipient(s) only. If you have received this 
> email by mistake, please notify the sender immediately and do not disclose 
> the contents to anyone or make copies thereof.
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security] keyutils: migrate to meta-oe

2019-07-29 Thread dbaryshkov 
From: Dmitry Eremin-Solenikov 

keyutils are now part of meta-oe, so remove them from meta-security.

Signed-off-by: Dmitry Eremin-Solenikov 
---
 .../files/fix_library_install_path.patch  | 28 --
 ...ror-report-by-adding-default-message.patch | 42 ---
 .../keyutils-test-fix-output-format.patch | 41 --
 recipes-security/keyutils/files/run-ptest |  3 --
 recipes-security/keyutils/keyutils_1.6.bb | 53 ---
 5 files changed, 167 deletions(-)
 delete mode 100644 
recipes-security/keyutils/files/fix_library_install_path.patch
 delete mode 100644 
recipes-security/keyutils/files/keyutils-fix-error-report-by-adding-default-message.patch
 delete mode 100644 
recipes-security/keyutils/files/keyutils-test-fix-output-format.patch
 delete mode 100755 recipes-security/keyutils/files/run-ptest
 delete mode 100644 recipes-security/keyutils/keyutils_1.6.bb

diff --git a/recipes-security/keyutils/files/fix_library_install_path.patch 
b/recipes-security/keyutils/files/fix_library_install_path.patch
deleted file mode 100644
index 938fe2eb57a4..
--- a/recipes-security/keyutils/files/fix_library_install_path.patch
+++ /dev/null
@@ -1,28 +0,0 @@
-From b0355cc205543ffd33752874295139d57c4fbc3e Mon Sep 17 00:00:00 2001
-From: Wenzong Fan 
-Date: Tue, 26 Sep 2017 07:59:51 +
-Subject: [PATCH] Subject: [PATCH] keyutils: use relative path for link
-
-The absolute path of the symlink will be invalid
-when populated in sysroot, so use relative path instead.
-
-Upstream-Status: Pending
-
-Signed-off-by: Jackie Huang 
-Signed-off-by: Wenzong Fan 
-{rebased for 1.6]
-Signed-off-by: Armin Kuster 
-
-Index: keyutils-1.6/Makefile
-===
 keyutils-1.6.orig/Makefile
-+++ keyutils-1.6/Makefile
-@@ -184,7 +184,7 @@ ifeq ($(NO_SOLIB),0)
-   $(INSTALL) -D $(LIBNAME) $(DESTDIR)$(LIBDIR)/$(LIBNAME)
-   $(LNS) $(LIBNAME) $(DESTDIR)$(LIBDIR)/$(SONAME)
-   mkdir -p $(DESTDIR)$(USRLIBDIR)
--  $(LNS) $(LIBDIR)/$(SONAME) $(DESTDIR)$(USRLIBDIR)/$(DEVELLIB)
-+  $(LNS) $(SONAME) $(DESTDIR)$(USRLIBDIR)/$(DEVELLIB)
-   sed \
-   -e 's,@VERSION\@,$(VERSION),g' \
-   -e 's,@prefix\@,$(PREFIX),g' \
diff --git 
a/recipes-security/keyutils/files/keyutils-fix-error-report-by-adding-default-message.patch
 
b/recipes-security/keyutils/files/keyutils-fix-error-report-by-adding-default-message.patch
deleted file mode 100644
index acd91c01c483..
--- 
a/recipes-security/keyutils/files/keyutils-fix-error-report-by-adding-default-message.patch
+++ /dev/null
@@ -1,42 +0,0 @@
-fix keyutils test error report
-
-Upstream-Status: Pending
-
-"Permission denied" may be the reason of EKEYEXPIRED and EKEYREVOKED.
-"Required key not available" may be the reason of EKEYREVOKED.
-EXPIRED and REVOKED are 2 status of kernel security keys features.
-But the userspace keyutils lib will output the error message, which may
-have several reasons.
-
-Signed-off-by: Han Chao 
-
-diff --git a/tests/toolbox.inc.sh b/tests/toolbox.inc.sh
-index bbca00a..739e9d0 100644
 a/tests/toolbox.inc.sh
-+++ b/tests/toolbox.inc.sh
-@@ -227,11 +227,12 @@ function expect_error ()
-   ;;
-   EKEYEXPIRED)
-   my_err="Key has expired"
--  alt_err="Unknown error 127"
-+  alt_err="Permission denied"
-   ;;
-   EKEYREVOKED)
-   my_err="Key has been revoked"
--  alt_err="Unknown error 128"
-+  alt_err="Permission denied"
-+  alt2_err="Required key not available"
-   ;;
-   EKEYREJECTED)
-   my_err="Key has been rejected"
-@@ -249,6 +250,9 @@ function expect_error ()
- elif [ "x$alt_err" != "x" ] && expr "$my_errmsg" : ".*: $alt_err" 
>&/dev/null
- then
-   :
-+elif [ "x$alt2_err" != "x" ] && expr "$my_errmsg" : ".*: $alt2_err" 
>&/dev/null
-+then
-+  :
- elif [ "x$old_err" != "x" ] && expr "$my_errmsg" : ".*: $old_err" 
>&/dev/null
- then
-   :
-
diff --git 
a/recipes-security/keyutils/files/keyutils-test-fix-output-format.patch 
b/recipes-security/keyutils/files/keyutils-test-fix-output-format.patch
deleted file mode 100644
index a4ffd50ce54c..
--- a/recipes-security/keyutils/files/keyutils-test-fix-output-format.patch
+++ /dev/null
@@ -1,41 +0,0 @@
-From 49b6321368e4bd3cd233d045cd09004ddd7968b2 Mon Sep 17 00:00:00 2001
-From: Jackie Huang 
-Date: Mon, 15 May 2017 14:52:00 +0800
-Subject: [PATCH] keyutils: fix output format
-
-keyutils ptest output format is incorrect, according to yocto
-Development Manual
-(http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html#testing-packages-with-ptest)
-5.10.6. Testing Packages With ptestThe test generates output in the format 
used by Automake:
-: 
-where the result can be PASS, FAIL, or SKIP, and the testname can be any
-identifying string.
-So we should change the test result format to match yocto ptest rules.
-

[yocto] [meta-integrity] layer.conf: switch to keyutils from meta-oe

2019-07-29 Thread dbaryshkov 
From: Dmitry Eremin-Solenikov 

As pointer by Martin Jansa, keyutils package is now a part of meta-oe,
so switch to using keyutils from that layer.

Signed-off-by: Dmitry Eremin-Solenikov 
---
 meta-integrity/conf/layer.conf | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta-integrity/conf/layer.conf b/meta-integrity/conf/layer.conf
index 1d31edd9b151..41989da38f63 100644
--- a/meta-integrity/conf/layer.conf
+++ b/meta-integrity/conf/layer.conf
@@ -22,5 +22,5 @@ INTEGRITY_BASE := '${LAYERDIR}'
 OE_TERMINAL_EXPORTS += "INTEGRITY_BASE"
 
 LAYERSERIES_COMPAT_integrity = "warrior"
-# ima-evm-utils depends on keyutils from meta-security
-LAYERDEPENDS_integrity = "core security"
+# ima-evm-utils depends on keyutils from meta-oe
+LAYERDEPENDS_integrity = "core openembedded-layer"
-- 
2.20.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-integrity][PATCH 1/3] layer.conf: add dependency on meta-security

2019-07-29 Thread Dmitry Eremin-Solenikov 
пн, 29 июл. 2019 г. в 12:49, Martin Jansa :
>
> On Wed, Jul 24, 2019 at 02:23:24PM +0300, Dmitry Eremin-Solenikov wrote:
> > ima-evm-utils recipe depends on keyutils recipe which is a part of
> > meta-security layer.
> >
> > Signed-off-by: Dmitry Eremin-Solenikov 
> > ---
> >  meta-integrity/conf/layer.conf | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/meta-integrity/conf/layer.conf b/meta-integrity/conf/layer.conf
> > index 2f696cf7c332..917aa86e11d7 100644
> > --- a/meta-integrity/conf/layer.conf
> > +++ b/meta-integrity/conf/layer.conf
> > @@ -22,3 +22,5 @@ IMA_EVM_BASE := '${LAYERDIR}'
> >  OE_TERMINAL_EXPORTS += "IMA_EVM_BASE"
> >
> >  LAYERSERIES_COMPAT_integrity = "warrior"
> > +# ima-evm-utils depends on keyutils from meta-security
> > +LAYERDEPENDS_integrity = "core security"
>
> keyutils are now in meta-oe:
> http://git.openembedded.org/meta-openembedded/commit/?id=415e213ad75ec9a93171c963395a1c4b92c6233b

Thank you!

-- 
With best wishes
Dmitry
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [meta-integrity][PATCH 1/3] layer.conf: add dependency on meta-security

2019-07-29 Thread Martin Jansa 
On Wed, Jul 24, 2019 at 02:23:24PM +0300, Dmitry Eremin-Solenikov wrote:
> ima-evm-utils recipe depends on keyutils recipe which is a part of
> meta-security layer.
> 
> Signed-off-by: Dmitry Eremin-Solenikov 
> ---
>  meta-integrity/conf/layer.conf | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/meta-integrity/conf/layer.conf b/meta-integrity/conf/layer.conf
> index 2f696cf7c332..917aa86e11d7 100644
> --- a/meta-integrity/conf/layer.conf
> +++ b/meta-integrity/conf/layer.conf
> @@ -22,3 +22,5 @@ IMA_EVM_BASE := '${LAYERDIR}'
>  OE_TERMINAL_EXPORTS += "IMA_EVM_BASE"
>  
>  LAYERSERIES_COMPAT_integrity = "warrior"
> +# ima-evm-utils depends on keyutils from meta-security
> +LAYERDEPENDS_integrity = "core security"

keyutils are now in meta-oe:
http://git.openembedded.org/meta-openembedded/commit/?id=415e213ad75ec9a93171c963395a1c4b92c6233b

> -- 
> 2.20.1
> 
> -- 
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com


signature.asc
Description: Digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] ODP: Recipes for gcc-native

2019-07-29 Thread Taborski, Krzysztof (Nokia - PL/Wroclaw) 
It's fully understandable for me, that gcc handling is more complex and harder 
to maintain, than other -native recipes.
Nevertheless I am feeling inconsistency, because all native tools can be 
delivered in container and native recipes would be not needed at all.


Best regards,

Krzysztof Taborski


Od: Khem Raj 
Wysłane: poniedziałek, 22 lipca 2019 22:22
Do: Taborski, Krzysztof (Nokia - PL/Wroclaw) 
DW: yocto@yoctoproject.org 
Temat: Re: [yocto] Recipes for gcc-native



On Mon, Jul 22, 2019 at 1:14 PM Taborski, Krzysztof (Nokia - PL/Wroclaw) 
mailto:krzysztof.tabor...@nokia.com>> wrote:
Hello,
I am wondering, if there is any reason, that yocto project does not delivers 
recipes for gcc-native ( in similar way as python-native for example)?

It would allow to build native recipes with different/higher version of gcc, 
than this, which user has on my build servers.


This would not solve the problem fully and yet create more maintainer burden 
since the supporting libraries are still coming from distribution underneath 
and this would create yet another combination for variable

I think container approach would solve this for us in a nicer way

Most supported distribution do support newer compiler packages and that’s a 
better option since they would have tested it on that distribution to some 
extent


Best regards,

Krzysztof Taborski

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] QA notification for completed autobuilder build (yocto-2.8_M2.rc1)

2019-07-29 Thread pokybuild 


A build flagged for QA (yocto-2.8_M2.rc1) was completed on the autobuilder and 
is available at:


https://autobuilder.yocto.io/pub/releases/yocto-2.8_M2.rc1


Build hash information: 

bitbake: f5ea06fc2b6713c9f8e85ecf7cb981ae9a84d896
meta-gplv2: 1e2480e50f34e55bdfd5e06f98441e03a3752d5a
meta-intel: 3227874941bb8f9b706d6057b1de3997881bdffd
meta-mingw: 3fa43aa92f1a1c90304f6f4f49270915d1392cce
oecore: e0c3436241afca93f107e325d1b9ffcdebf706cd
poky: 835f7eac0610325e906591cd81890bebe8627580



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.pur...@linuxfoundation.org


 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Meta-raspberrypi

2019-07-29 Thread Shravan Singh 
Hello All,

I am trying to create a base image for raspberry-pi cm3(compute module 3)

I am using warrior-21.0.1
I downloaded meta-raspberry-pi from
https://git.yoctoproject.org/git/meta-raspberrypi
I added the layer in bblayer.conf and I have changed the machine variable
in local.conf
to *raspberrypi-cm3*
I am using oe-init-build script to generate the base files

Now when I run the command
bitbake core-image-base

I get the below mentioned error
Error: No recipes available for:
/home/blue/yacto/meta-raspberrypi/recipes-bsp/u-boot/u-boot_2019.07.bbappend
/home/blue/yacto/meta-raspberrypi/recipes-multimedia/gstreamer/gstreamer1.0-omx_1.16%.bbappend


Any help with this?


Regards,
Shravan Singh
(239) 243-0838

Blue Sparq, Inc.
928 NE 24th Lane unit 4 and 5.
Cape Coral, FL 33993

IMPORTANT: The contents of this email and any attachments are confidential.
They are intended for the named recipient(s) only. If you have received
this email by mistake, please notify the sender immediately and do not
disclose the contents to anyone or make copies thereof.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] NPM yocto build problem

2019-07-29 Thread Dvorkin Dmitry 
I see Jean-Marie made this commit

https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=a34d0d539e5fdf341541fb628652d22289e80512

I'm experiencing problems building and installing more then one node
modules into image:

https://pastebin.com/CXPkqD8j

It says, /usr/lib/node is a FILE and is is already installed by another
package. I'm using RPM package manager in Yocto and I'm pre-installing
several NPM modules into my image.


Did I make something wrong?








signature.asc
Description: OpenPGP digital signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH 1/2 V2] openscap: update recipe

2019-07-29 Thread Yi Zhao 
* Add PACKAGECONFIG for gcrypt, nss3 and selinux
* Use EXTRA_OECMAKE rather than EXTRA_OECONF
* Set CMAKE_SKIP_RPATH and CMAKE_SKIP_INSTALL_RPATH instead of chrpath
* Remove ptest since there are many host contamination issues on target.
  We will add it back when these issues are solved.
* Drop the unused patch
* Add PV
* Clean up DEPENDS

Signed-off-by: Yi Zhao 
---
 .../openscap/files/probe_dir_fixup.patch   | 17 --
 .../recipes-openscap/openscap/files/run-ptest  |  3 -
 .../recipes-openscap/openscap/openscap.inc | 67 --
 .../recipes-openscap/openscap/openscap_1.3.1.bb|  1 -
 .../recipes-openscap/openscap/openscap_git.bb  |  3 +-
 5 files changed, 25 insertions(+), 66 deletions(-)
 delete mode 100644 
meta-security-compliance/recipes-openscap/openscap/files/probe_dir_fixup.patch
 delete mode 100644 
meta-security-compliance/recipes-openscap/openscap/files/run-ptest

diff --git 
a/meta-security-compliance/recipes-openscap/openscap/files/probe_dir_fixup.patch
 
b/meta-security-compliance/recipes-openscap/openscap/files/probe_dir_fixup.patch
deleted file mode 100644
index ecbe602..000
--- 
a/meta-security-compliance/recipes-openscap/openscap/files/probe_dir_fixup.patch
+++ /dev/null
@@ -1,17 +0,0 @@
-Index: git/configure.ac
-===
 git.orig/configure.ac
-+++ git/configure.ac
-@@ -1109,11 +1109,7 @@ AC_ARG_WITH([crypto],
-  [],
-  [crypto=gcrypt])
- 
--if test "x${libexecdir}" = xNONE; then
--  probe_dir="/usr/local/libexec/openscap"
--else
--  EXPAND_DIR(probe_dir,"${libexecdir}/openscap")
--fi
-+probe_dir="/usr/local/libexec/openscap"
- 
- AC_SUBST(probe_dir)
- 
diff --git a/meta-security-compliance/recipes-openscap/openscap/files/run-ptest 
b/meta-security-compliance/recipes-openscap/openscap/files/run-ptest
deleted file mode 100644
index 454a6a3..000
--- a/meta-security-compliance/recipes-openscap/openscap/files/run-ptest
+++ /dev/null
@@ -1,3 +0,0 @@
-#!/bin/sh
-cd tests
-make -k check
diff --git a/meta-security-compliance/recipes-openscap/openscap/openscap.inc 
b/meta-security-compliance/recipes-openscap/openscap/openscap.inc
index e5daaf8..5a66d5e 100644
--- a/meta-security-compliance/recipes-openscap/openscap/openscap.inc
+++ b/meta-security-compliance/recipes-openscap/openscap/openscap.inc
@@ -6,71 +6,50 @@ HOME_URL = "https://www.open-scap.org/tools/openscap-base/;
 LIC_FILES_CHKSUM = "file://COPYING;md5=fbc093901857fcd118f065f900982c24"
 LICENSE = "LGPL-2.1"
 
-DEPENDS = "autoconf-archive dbus acl bzip2 pkgconfig gconf procps curl libxml2 
libxslt libcap swig libgcrypt chrpath-replacement-native "
-
-DEPENDS_class-native = "autoconf-archive-native pkgconfig-native swig-native 
curl-native libxml2-native libxslt-native dpkg-native libgcrypt-native 
nss-native"
+DEPENDS = "dbus acl bzip2 pkgconfig gconf procps curl libxml2 libxslt libcap 
swig"
+DEPENDS_class-native = "pkgconfig-native swig-native curl-native 
libxml2-native libxslt-native libcap-native"
 
 S = "${WORKDIR}/git"
 
-inherit cmake pkgconfig python3native perlnative ptest
-
-PACKAGECONFIG ?= "python3 rpm perl"
-PACKAGECONFIG[python3] = "-DENABLE_PYTHON3=True, , python3, python3"
-PACKAGECONFIG[perl] = "-DENABLE_PERL=True,, perl, perl"
-PACKAGECONFIG[rpm] = "-DENABLE_OSCAP_UTIL_AS_RPM=True, ,rpm, rpm"
-
-EXTRA_OECONF += "-DENABLE_PROBES_INDEPENDENT=yes -DENABLE_PROBES_LINUX=yes 
-DWITH_CRYPTO=gcrypt\
-   -DENABLE_PROBES_SOLARIS=yes -DENABLE_PROBES_UNIX=yes  
-DENABLE_TESTS=no \
-   -DENABLE_OSCAP_UTIL_SSH=yes -DENABLE_OSCAP_UTIL=yes 
-DENABLE_SCE=yes \
--DENABLE_OSCAP_UTIL_DOCKER=no \
-"
-
+inherit cmake pkgconfig python3native perlnative
+
+PACKAGECONFIG ?= "python3 rpm perl gcrypt 
${@bb.utils.contains('DISTRO_FEATURES', 'selinux', 'selinux', '', d)}"
+PACKAGECONFIG[python3] = "-DENABLE_PYTHON3=ON, ,python3, python3"
+PACKAGECONFIG[perl] = "-DENABLE_PERL=ON, ,perl, perl"
+PACKAGECONFIG[rpm] = "-DENABLE_OSCAP_UTIL_AS_RPM=ON, ,rpm, rpm"
+PACKAGECONFIG[gcrypt] = "-DWITH_CRYPTO=gcrypt, ,libgcrypt"
+PACKAGECONFIG[nss3] = "-DWITH_CRYPTO=nss3, ,nss"
+PACKAGECONFIG[selinux] = ", ,libselinux"
+
+EXTRA_OECMAKE += "-DENABLE_PROBES_LINUX=ON -DENABLE_PROBES_UNIX=ON \
+  -DENABLE_PROBES_SOLARIS=OFF -DENABLE_PROBES_INDEPENDENT=ON \
+  -DENABLE_OSCAP_UTIL=ON -DENABLE_OSCAP_UTIL_SSH=ON \
+  -DENABLE_OSCAP_UTIL_DOCKER=OFF 
-DENABLE_OSCAP_UTIL_CHROOT=OFF \
+  -DENABLE_OSCAP_UTIL_PODMAN=OFF -DENABLE_OSCAP_UTIL_VM=OFF \
+  -DENABLE_PROBES_WINDOWS=OFF -DENABLE_VALGRIND=OFF \
+  -DENABLE_SCE=ON -DENABLE_MITRE=OFF -DENABLE_TESTS=OFF \
+  -DCMAKE_SKIP_INSTALL_RPATH=ON -DCMAKE_SKIP_RPATH=ON \
+ "
 
 STAGING_OSCAP_DIR = "${TMPDIR}/work-shared/${MACHINE}/oscap-source"
 STAGING_OSCAP_BUILDDIR =

[yocto] [meta-security][PATCH 2/2 V2] scap-security-guide: update recipe

2019-07-29 Thread Yi Zhao 
* Set B="${S}/build" to fix the build failure for out of source
  directory
* Remove do_complile and do_install. Use the default functions from
  cmake.bbclass.
* Install the artifacts to /usr/share rather than /usr/local/share

Signed-off-by: Yi Zhao 
---
 .../scap-security-guide/scap-security-guide.inc| 28 +-
 .../scap-security-guide/scap-security-guide_git.bb |  6 +
 2 files changed, 7 insertions(+), 27 deletions(-)

diff --git 
a/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide.inc
 
b/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide.inc
index ed70c18..341721a 100644
--- 
a/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide.inc
+++ 
b/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide.inc
@@ -7,6 +7,7 @@ LIC_FILES_CHKSUM = 
"file://LICENSE;md5=97662e4486d9a1d09f358851d9f41a1a"
 LICENSE = "LGPL-2.1"
 
 DEPENDS = "openscap-native python3 python3-pyyaml-native python3-jinja2-native 
libxml2-native"
+RDEPENDS_${PN} = "openscap"
 
 S = "${WORKDIR}/git"
 
@@ -20,28 +21,11 @@ OECMAKE_GENERATOR = "Unix Makefiles"
 
 EXTRA_OECMAKE += "-DENABLE_PYTHON_COVERAGE=OFF"
 
-do_configure_prepend () {
-   sed -i -e 's:NAMES\ sed:NAMES\ ${HOSTTOOLS_DIR}/sed:g'   
${S}/CMakeLists.txt
-sed -i 
's:/usr/share/openscap/:${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/:g' 
${S}/cmake/SSGCommon.cmake
-}
-
-do_compile () {
-   cd ${S}/build
-   cmake ../
-   # oddly rhel7 needs to build first
-   make rhel7
-}
+B = "${S}/build"
 
-do_install () {
-   cd ${S}/build
-   make DESTDIR=${D} install
+do_configure_prepend () {
+sed -i -e 's:NAMES\ sed:NAMES\ ${HOSTTOOLS_DIR}/sed:g' ${S}/CMakeLists.txt
+sed -i -e 's:NAMES\ grep:NAMES\ ${HOSTTOOLS_DIR}/grep:g' 
${S}/CMakeLists.txt
 }
 
-localdatadir = "${prefix}/local/share"
-localmandir = "${localdatadir}/man"
-localdocdir = "${localdatadir}/doc"
-localxmldir = "${localdatadir}/xml"
-
-FILES_${PN} += "${localdatadir} ${localxmldir}"
-FILES_${PN}-doc += "${localmandir} ${localdocdir}"
-RDEPNEDS_${PN} = "openscap"
+FILES_${PN} += "${datadir}/xml"
diff --git 
a/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide_git.bb
 
b/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide_git.bb
index cb21fed..d9238c0 100644
--- 
a/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide_git.bb
+++ 
b/meta-security-compliance/recipes-openscap/scap-security-guide/scap-security-guide_git.bb
@@ -2,12 +2,8 @@ SUMARRY = "SCAP content for various platforms, OE changes"
 
 SRCREV = "5fdfdcb2e95afbd86ace555beca5d20cbf1043ed"
 SRC_URI = "git://github.com/akuster/scap-security-guide.git;branch=oe-0.1.44;"
-PV = "v0.1.44+git${SRCPV}"
+PV = "0.1.44+git${SRCPV}"
 
 require scap-security-guide.inc
 
-do_compile_append () {
-make openembedded
-}
-
 EXTRA_OECMAKE += "-DSSG_PRODUCT_OPENEMBEDDED=ON"
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [meta-security][PATCH 0/2 V2] openscap/scap-security-guide: update recipes

2019-07-29 Thread Yi Zhao 
Changes from V1:

openscap: Clean up DEPENDS. Remove autoconf-archive and dpkg-native from 
DEPENDS because we are using CMake/Ninjia now
scap-security-guide: Fix typo: RDEPNEDS_${PN} -> RDEPENDS_${PN}

Yi Zhao (2):
  openscap: update recipe
  scap-security-guide: update recipe

 .../openscap/files/probe_dir_fixup.patch   | 17 --
 .../recipes-openscap/openscap/files/run-ptest  |  3 -
 .../recipes-openscap/openscap/openscap.inc | 67 --
 .../recipes-openscap/openscap/openscap_1.3.1.bb|  1 -
 .../recipes-openscap/openscap/openscap_git.bb  |  3 +-
 .../scap-security-guide/scap-security-guide.inc| 28 ++---
 .../scap-security-guide/scap-security-guide_git.bb |  6 +-
 7 files changed, 32 insertions(+), 93 deletions(-)
 delete mode 100644 
meta-security-compliance/recipes-openscap/openscap/files/probe_dir_fixup.patch
 delete mode 100644 
meta-security-compliance/recipes-openscap/openscap/files/run-ptest

-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto