[yocto] How to build and deploy with devtool without running it again

2019-07-22 Thread Mübin İçyer 
Hi,

I want to build a recipe and then deploy it on target immediately after
that.
Each time devtool is loading cache parsing all recipes and builds or
deploys.

Can I make these two steps in only one step?

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

[yocto] [yocto-docs][PATCH] ref-manual: Sync list of image types with source

2019-07-22 Thread Daniel Ammann 
hdddirect was removed from openembedded-core in commit
929ba563f1bc7195c4981b8e139c432b2cc388ea.

f2fs was added in commit dec029686a47b574edfce4472fe2167db54398fb.

container was added in commit e45f074b792a43aa2fd84a5a3f0e20bf1d88ad7e.

squashfs-lz4 was added in commit de70799af1a8bfe2fac22b90401053275d4714ba.
---
 documentation/ref-manual/ref-variables.xml | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/documentation/ref-manual/ref-variables.xml 
b/documentation/ref-manual/ref-variables.xml
index 0080364e4..cbbd684ae 100644
--- a/documentation/ref-manual/ref-variables.xml
+++ b/documentation/ref-manual/ref-variables.xml
@@ -6606,6 +6606,7 @@
 by default:
 
  btrfs
+ container
  cpio
  cpio.gz
  cpio.lz4
@@ -6621,13 +6622,14 @@
  ext3.gz
  ext4
  ext4.gz
- hdddirect
+ f2fs
  hddimg
  iso
  jffs2
  jffs2.sum
  multiubi
  squashfs
+ squashfs-lz4
  squashfs-lzo
  squashfs-xz
  tar
-- 
2.11.0

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

Re: [yocto] ERROR: Actual rootfs size is larger than allowed

2019-07-22 Thread María del Mar Velasco AERTEC Solutions – Aerospace & Aviation 

Thanks you very much for your reply! You’ve helped me a lot!

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

Re: [yocto] Looking for a recommendation for the right Yocto dev board that supports MIPI CSI-2...

2019-07-22 Thread Khem Raj 
On Wed, Jul 3, 2019 at 4:32 PM Bob Cochran  wrote:
>
> On 6/20/19 11:24 PM, Bob Cochran wrote:
> > Hi,
> >
> > I'm doing some work with MIPI cameras, and I need a development board
> > with stable Yocto and MIPI CSI-2 support.   At this point, I'm
> > thinking i.MX, but I'm open to any suggestion.
>
> It looks like we're going to purchase an NXP MCIMX8M-EVK dev board (at
> least one to get started).   Can someone please confirm that the
> imx8mqevk.conf machine file is for this board?
>
> Is this board Yocto Project stable?  I need to be able to build the
> master branch for this board (or should I be using next?). Any comments
> or feedback will be great appreciated.
>
> https://www.nxp.com/support/developer-resources/evaluation-and-development-boards/i.mx-evaluation-and-development-boards/evaluation-kit-for-the-i.mx-8m-applications-processor:MCIMX8M-EVK
>

seems it is in meta-freescale.
https://git.yoctoproject.org/cgit/cgit.cgi/meta-freescale/tree/conf/machine/imx8mqevk.conf?h=master

> Thanks
>
> Bob
>
>
> >
> > I'm not sure what type of access I'll have to the D-PHY data streams.
> > Do they always terminate into a GPU?   However, I would like a board
> > that gives me the most capability to control / route the data with
> > open source drivers.
> >
> > I suppose I want CSI-2 in and HDMI out.
> >
> > Thank you,
> >
> > Bob
> >
> >
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Create an image from deployed files

2019-07-22 Thread Khem Raj 
On Wed, Jul 3, 2019 at 12:43 PM Stefan Herbrechtsmeier
 wrote:
>
> Hi,
>
> what would be the best solution to create an image from deployed files?
>
> The wic bootimg-partition plugin copy over files listed in
> IMAGE_BOOT_FILES and create a partition inside the wic image. The
> image.bbclass creates an image from individual packages.
>
> I want to create an image like the image.bbclass but from deployed files
> like the wic bootimg-partition plugin.
>
> I have add an image_types_vfat.bbclass to create vfat images, move the
> common parts from image.bbclass into image-common.bbclass and add a
> boot-image.bbclass. This class duplicates some code from the wic
> bootimg-partition plugin inside the do_rootfs function and add some
> dummy tasks to minimize the changes in the common code.
>
> I wonder if this is the right direction or if another solution exists.
>

I would think you can add a wic kickstart image to generate your desired image

> Best regards
>Stefan
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] How to specify a different kernel for an image

2019-07-22 Thread Patrick Doyle 
On Mon, Jul 22, 2019 at 2:05 AM Gabriele Zampieri
 wrote:
>
> Hi Patrick,
>
> thank you for the clarification.
> I have no idea on how to encapsulate the output of bitbake into another image 
> in a nice and clean way. I'm pretty sure that you must run two separate 
> bitbake, one per MACHINE.
> What about a partitioned USB stick? You could have the base partition schema 
> plus an extra partition that contains the production image. The 
> implementation depends on which tool you are going to use to partition the 
> output image (if any).
>
> Gabriele
Thanks again for your thoughts, ideas, and conversation.  Based on
this conversation and further research around the web, it seems like
defining a new MACHINE is the best/only way to go.  (This is where you
say, "That's what I TOLD you at the beginning)

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

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

2019-07-22 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 304
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] Create an image from deployed files

2019-07-22 Thread Stefan Herbrechtsmeier 

Am 22.07.19 um 18:34 schrieb Khem Raj:

On Wed, Jul 3, 2019 at 12:43 PM Stefan Herbrechtsmeier
 wrote:


Hi,

what would be the best solution to create an image from deployed files?

The wic bootimg-partition plugin copy over files listed in
IMAGE_BOOT_FILES and create a partition inside the wic image. The
image.bbclass creates an image from individual packages.

I want to create an image like the image.bbclass but from deployed files
like the wic bootimg-partition plugin.

I have add an image_types_vfat.bbclass to create vfat images, move the
common parts from image.bbclass into image-common.bbclass and add a
boot-image.bbclass. This class duplicates some code from the wic
bootimg-partition plugin inside the do_rootfs function and add some
dummy tasks to minimize the changes in the common code.

I wonder if this is the right direction or if another solution exists.



I would think you can add a wic kickstart image to generate your desired image


How should this work? I need an image of a single partition without MBR 
or GPT. Furthermore I have multiple independent images with different sizes.


Meanwhile I have a working solution with a bare-image bbclass which 
installs a list of images from the deploy directory into the image 
rootfs. This images could be used by other wic and swupdate images. 
Thereby the bare-image bbclass supports all image types plus vfat and 
with two additional patches the wic rawcopy plugin supports on the fly 
unpack of packed images.


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

[yocto] Recipes for gcc-native

2019-07-22 Thread Taborski, Krzysztof (Nokia - PL/Wroclaw) 
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.


Best regards,

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

Re: [yocto] Recipes for gcc-native

2019-07-22 Thread Khem Raj 
On Mon, Jul 22, 2019 at 1:14 PM Taborski, Krzysztof (Nokia - PL/Wroclaw) <
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

Re: [yocto] No GNU_HASH in the elf binary

2019-07-22 Thread Burton, Ross 
On Mon, 22 Jul 2019 at 21:13, Madhu Krishnamurthy  wrote:
> INSANE_SKIP_mlc = "ldflags"
> INSANE_SKIP_mlc-dev = "ldflags"
> INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
> INHIBIT_PACKAGE_STRIP = "1"
>
> But after adding that I still get this error.
> ERROR: mem-tst-0.1 do_package_qa: QA Issue: No GNU_HASH in the elf binary: 
> '/home/cluser/ac/z_cpu/build/tmp/work/corei7-64-poky-linux/mem/tst-0.1/packages-split/mem/usr/local/flex_pkgs/diags/mlc'
>  [ldflags]

The _mlc part is the package name, which isn't mlc.  Use INSANE_SKIP_mem-tst.

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

Re: [yocto] [meta-security-compliance][PATCH 2/4] openscap: add 1.3.1 recipes for upstream source

2019-07-22 Thread Yi Zhao 

Hi Armin,


I got the following error when build openscap:

ERROR: openscap-git-r0 do_compile_ptest_base: Function failed: 
do_compile_ptest_base (log file is located at 
/buildarea/build/tmp/work/core2-64-poky-linux/openscap/git-r0/temp/log.do_compile_ptest_base.329146)
ERROR: Logfile of failure stored in: 
/buildarea/build/tmp/work/core2-64-poky-linux/openscap/git-r0/temp/log.do_compile_ptest_base.329146

Log data follows:
| DEBUG: Executing shell function do_compile_ptest_base
| 
/buildarea/build/tmp/work/core2-64-poky-linux/openscap/git-r0/temp/run.do_compile_ptest_base.329146: 
line 108: oe-runcmake: command not found
| WARNING: 
/buildarea/build/tmp/work/core2-64-poky-linux/openscap/git-r0/temp/run.do_compile_ptest_base.329146:1 
exit 127 from 'oe-runcmake tests'
| ERROR: Function failed: do_compile_ptest_base (log file is located at 
/buildarea/build/tmp/work/core2-64-poky-linux/openscap/git-r0/temp/log.do_compile_ptest_base.329146)



//Yi


On 7/7/19 7:32 AM, Armin Kuster wrote:

Signed-off-by: Armin Kuster 
---
  .../recipes-openscap/openscap/openscap.inc| 11 +--
  .../recipes-openscap/openscap/openscap_1.3.1.bb   | 10 ++
  .../recipes-openscap/openscap/openscap_git.bb |  4 ++--
  3 files changed, 17 insertions(+), 8 deletions(-)
  create mode 100644 
meta-security-compliance/recipes-openscap/openscap/openscap_1.3.1.bb

diff --git a/meta-security-compliance/recipes-openscap/openscap/openscap.inc 
b/meta-security-compliance/recipes-openscap/openscap/openscap.inc
index 4c1f206..e5daaf8 100644
--- a/meta-security-compliance/recipes-openscap/openscap/openscap.inc
+++ b/meta-security-compliance/recipes-openscap/openscap/openscap.inc
@@ -10,10 +10,10 @@ DEPENDS = "autoconf-archive dbus acl bzip2 pkgconfig gconf 
procps curl libxml2 l
  
  DEPENDS_class-native = "autoconf-archive-native pkgconfig-native swig-native curl-native libxml2-native libxslt-native dpkg-native libgcrypt-native nss-native"
  
-inherit cmake pkgconfig python3native perlnative ptest

-
  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"
@@ -25,7 +25,6 @@ EXTRA_OECONF += "-DENABLE_PROBES_INDEPENDENT=yes 
-DENABLE_PROBES_LINUX=yes -DWIT
  -DENABLE_OSCAP_UTIL_DOCKER=no \
  "
  
-EXTRA_OECONF_class-native += "-DENABLE_PROBES=True"
  
  STAGING_OSCAP_DIR = "${TMPDIR}/work-shared/${MACHINE}/oscap-source"

  STAGING_OSCAP_BUILDDIR = 
"${TMPDIR}/work-shared/openscap/oscap-build-artifacts"
@@ -33,9 +32,9 @@ STAGING_OSCAP_BUILDDIR = 
"${TMPDIR}/work-shared/openscap/oscap-build-artifacts"
  EXTRANATIVEPATH += "chrpath-native"
  
  do_configure_append_class-native () {

-   sed -i 's:OSCAP_DEFAULT_CPE_PATH.*$:OSCAP_DEFAULT_CPE_PATH 
"${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/cpe":' ${S}/config.h
-   sed -i 's:OSCAP_DEFAULT_SCHEMA_PATH.*$:OSCAP_DEFAULT_SCHEMA_PATH 
"${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/schemas":' ${S}/config.h
-   sed -i 's:OSCAP_DEFAULT_XSLT_PATH.*$:OSCAP_DEFAULT_XSLT_PATH 
"${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/xsl":' ${S}/config.h
+   sed -i 's:OSCAP_DEFAULT_CPE_PATH.*$:OSCAP_DEFAULT_CPE_PATH 
"${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/cpe":' ${B}/config.h
+   sed -i 's:OSCAP_DEFAULT_SCHEMA_PATH.*$:OSCAP_DEFAULT_SCHEMA_PATH 
"${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/schemas":' ${B}/config.h
+   sed -i 's:OSCAP_DEFAULT_XSLT_PATH.*$:OSCAP_DEFAULT_XSLT_PATH 
"${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/xsl":' ${B}/config.h
  }
  
  do_clean[cleandirs] += " ${STAGING_OSCAP_BUILDDIR}"

diff --git 
a/meta-security-compliance/recipes-openscap/openscap/openscap_1.3.1.bb 
b/meta-security-compliance/recipes-openscap/openscap/openscap_1.3.1.bb
new file mode 100644
index 000..c29fd42
--- /dev/null
+++ b/meta-security-compliance/recipes-openscap/openscap/openscap_1.3.1.bb
@@ -0,0 +1,10 @@
+SUMARRY = "NIST Certified SCAP 1.2 toolkit"
+
+require openscap.inc
+
+SRCREV = "3a4c635691380fa990a226acc8558db35d7ebabc"
+SRC_URI = "git://github.com/OpenSCAP/openscap.git;branch=maint-1.3 \
+   file://run-ptest \
+"
+
+DEFAULT_PREFERENCE = "-1"
diff --git a/meta-security-compliance/recipes-openscap/openscap/openscap_git.bb 
b/meta-security-compliance/recipes-openscap/openscap/openscap_git.bb
index 3dfa99e..aded920 100644
--- a/meta-security-compliance/recipes-openscap/openscap/openscap_git.bb
+++ b/meta-security-compliance/recipes-openscap/openscap/openscap_git.bb
@@ -3,9 +3,9 @@
  
  SUMARRY = "NIST Certified SCAP 1.2 toolkit with OE changes"
  
+include openscap.inc

+
  SRCREV = "4bbdb46ff651f809d5b38ca08d769790c4bfff90"
  SRC_URI = "git://github.com/akuster/openscap.git;branch=oe-1.3 \
 file://run-ptest \
  "
-
-include openscap.inc

--
___

Re: [yocto] [meta-security-compliance][PATCH 2/4] openscap: add 1.3.1 recipes for upstream source

2019-07-22 Thread Akuster808 



> On Jul 23, 2019, at 02:51, Yi Zhao  wrote:
> 
> Hi Armin,
> 
> 
> I got the following error when build openscap:
> 
> ERROR: openscap-git-r0 do_compile_ptest_base: Function failed: 
> do_compile_ptest_base (log file is located at 
> /buildarea/build/tmp/work/core2-64-poky-linux/openscap/git-r0/temp/log.do_compile_ptest_base.329146)
> ERROR: Logfile of failure stored in: 
> /buildarea/build/tmp/work/core2-64-poky-linux/openscap/git-r0/temp/log.do_compile_ptest_base.329146
> Log data follows:
> | DEBUG: Executing shell function do_compile_ptest_base
> | 
> /buildarea/build/tmp/work/core2-64-poky-linux/openscap/git-r0/temp/run.do_compile_ptest_base.329146:
>  line 108: oe-runcmake: command not found
> | WARNING: 
> /buildarea/build/tmp/work/core2-64-poky-linux/openscap/git-r0/temp/run.do_compile_ptest_base.329146:1
>  exit 127 from 'oe-runcmake tests'
> | ERROR: Function failed: do_compile_ptest_base (log file is located at 
> /buildarea/build/tmp/work/core2-64-poky-linux/openscap/git-r0/temp/log.do_compile_ptest_base.329146)

Thats not good. Thought I had run though this code path.  

I am traveling the next  2 weeks so i am not sure how quickly I can address 
this issue.

Armin
> 
> 
> //Yi
> 
> 
>> On 7/7/19 7:32 AM, Armin Kuster wrote:
>> Signed-off-by: Armin Kuster 
>> ---
>>  .../recipes-openscap/openscap/openscap.inc| 11 +--
>>  .../recipes-openscap/openscap/openscap_1.3.1.bb   | 10 ++
>>  .../recipes-openscap/openscap/openscap_git.bb |  4 ++--
>>  3 files changed, 17 insertions(+), 8 deletions(-)
>>  create mode 100644 
>> meta-security-compliance/recipes-openscap/openscap/openscap_1.3.1.bb
>> 
>> diff --git a/meta-security-compliance/recipes-openscap/openscap/openscap.inc 
>> b/meta-security-compliance/recipes-openscap/openscap/openscap.inc
>> index 4c1f206..e5daaf8 100644
>> --- a/meta-security-compliance/recipes-openscap/openscap/openscap.inc
>> +++ b/meta-security-compliance/recipes-openscap/openscap/openscap.inc
>> @@ -10,10 +10,10 @@ DEPENDS = "autoconf-archive dbus acl bzip2 pkgconfig 
>> gconf procps curl libxml2 l
>>DEPENDS_class-native = "autoconf-archive-native pkgconfig-native 
>> swig-native curl-native libxml2-native libxslt-native dpkg-native 
>> libgcrypt-native nss-native"
>>  -inherit cmake pkgconfig python3native perlnative ptest
>> -
>>  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"
>> @@ -25,7 +25,6 @@ EXTRA_OECONF += "-DENABLE_PROBES_INDEPENDENT=yes 
>> -DENABLE_PROBES_LINUX=yes -DWIT
>>  -DENABLE_OSCAP_UTIL_DOCKER=no \
>>  "
>>  -EXTRA_OECONF_class-native += "-DENABLE_PROBES=True"
>>STAGING_OSCAP_DIR = "${TMPDIR}/work-shared/${MACHINE}/oscap-source"
>>  STAGING_OSCAP_BUILDDIR = 
>> "${TMPDIR}/work-shared/openscap/oscap-build-artifacts"
>> @@ -33,9 +32,9 @@ STAGING_OSCAP_BUILDDIR = 
>> "${TMPDIR}/work-shared/openscap/oscap-build-artifacts"
>>  EXTRANATIVEPATH += "chrpath-native"
>>do_configure_append_class-native () {
>> -sed -i 's:OSCAP_DEFAULT_CPE_PATH.*$:OSCAP_DEFAULT_CPE_PATH 
>> "${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/cpe":' ${S}/config.h
>> -sed -i 's:OSCAP_DEFAULT_SCHEMA_PATH.*$:OSCAP_DEFAULT_SCHEMA_PATH 
>> "${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/schemas":' ${S}/config.h
>> -sed -i 's:OSCAP_DEFAULT_XSLT_PATH.*$:OSCAP_DEFAULT_XSLT_PATH 
>> "${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/xsl":' ${S}/config.h
>> +sed -i 's:OSCAP_DEFAULT_CPE_PATH.*$:OSCAP_DEFAULT_CPE_PATH 
>> "${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/cpe":' ${B}/config.h
>> +sed -i 's:OSCAP_DEFAULT_SCHEMA_PATH.*$:OSCAP_DEFAULT_SCHEMA_PATH 
>> "${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/schemas":' ${B}/config.h
>> +sed -i 's:OSCAP_DEFAULT_XSLT_PATH.*$:OSCAP_DEFAULT_XSLT_PATH 
>> "${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/xsl":' ${B}/config.h
>>  }
>>do_clean[cleandirs] += " ${STAGING_OSCAP_BUILDDIR}"
>> diff --git 
>> a/meta-security-compliance/recipes-openscap/openscap/openscap_1.3.1.bb 
>> b/meta-security-compliance/recipes-openscap/openscap/openscap_1.3.1.bb
>> new file mode 100644
>> index 000..c29fd42
>> --- /dev/null
>> +++ b/meta-security-compliance/recipes-openscap/openscap/openscap_1.3.1.bb
>> @@ -0,0 +1,10 @@
>> +SUMARRY = "NIST Certified SCAP 1.2 toolkit"
>> +
>> +require openscap.inc
>> +
>> +SRCREV = "3a4c635691380fa990a226acc8558db35d7ebabc"
>> +SRC_URI = "git://github.com/OpenSCAP/openscap.git;branch=maint-1.3 \
>> +   file://run-ptest \
>> +"
>> +
>> +DEFAULT_PREFERENCE = "-1"
>> diff --git 
>> a/meta-security-compliance/recipes-openscap/openscap/openscap_git.bb 
>> b/meta-security-compliance/recipes-openscap/openscap/openscap_git.bb
>> index 3dfa99e..aded920 100644
>> --- a/meta-security-compliance

Re: [yocto] [meta-security-compliance][PATCH 2/4] openscap: add 1.3.1 recipes for upstream source

2019-07-22 Thread Yi Zhao 



On 7/23/19 2:38 PM, Akuster808 wrote:



On Jul 23, 2019, at 02:51, Yi Zhao  wrote:

Hi Armin,


I got the following error when build openscap:

ERROR: openscap-git-r0 do_compile_ptest_base: Function failed: 
do_compile_ptest_base (log file is located at 
/buildarea/build/tmp/work/core2-64-poky-linux/openscap/git-r0/temp/log.do_compile_ptest_base.329146)
ERROR: Logfile of failure stored in: 
/buildarea/build/tmp/work/core2-64-poky-linux/openscap/git-r0/temp/log.do_compile_ptest_base.329146
Log data follows:
| DEBUG: Executing shell function do_compile_ptest_base
| 
/buildarea/build/tmp/work/core2-64-poky-linux/openscap/git-r0/temp/run.do_compile_ptest_base.329146:
 line 108: oe-runcmake: command not found
| WARNING: 
/buildarea/build/tmp/work/core2-64-poky-linux/openscap/git-r0/temp/run.do_compile_ptest_base.329146:1
 exit 127 from 'oe-runcmake tests'
| ERROR: Function failed: do_compile_ptest_base (log file is located at 
/buildarea/build/tmp/work/core2-64-poky-linux/openscap/git-r0/temp/log.do_compile_ptest_base.329146)

Thats not good. Thought I had run though this code path.

I am traveling the next  2 weeks so i am not sure how quickly I can address 
this issue.



That's OK. Thanks.


//Yi



Armin


//Yi



On 7/7/19 7:32 AM, Armin Kuster wrote:
Signed-off-by: Armin Kuster 
---
  .../recipes-openscap/openscap/openscap.inc| 11 +--
  .../recipes-openscap/openscap/openscap_1.3.1.bb   | 10 ++
  .../recipes-openscap/openscap/openscap_git.bb |  4 ++--
  3 files changed, 17 insertions(+), 8 deletions(-)
  create mode 100644 
meta-security-compliance/recipes-openscap/openscap/openscap_1.3.1.bb

diff --git a/meta-security-compliance/recipes-openscap/openscap/openscap.inc 
b/meta-security-compliance/recipes-openscap/openscap/openscap.inc
index 4c1f206..e5daaf8 100644
--- a/meta-security-compliance/recipes-openscap/openscap/openscap.inc
+++ b/meta-security-compliance/recipes-openscap/openscap/openscap.inc
@@ -10,10 +10,10 @@ DEPENDS = "autoconf-archive dbus acl bzip2 pkgconfig gconf 
procps curl libxml2 l
DEPENDS_class-native = "autoconf-archive-native pkgconfig-native swig-native 
curl-native libxml2-native libxslt-native dpkg-native libgcrypt-native nss-native"
  -inherit cmake pkgconfig python3native perlnative ptest
-
  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"
@@ -25,7 +25,6 @@ EXTRA_OECONF += "-DENABLE_PROBES_INDEPENDENT=yes 
-DENABLE_PROBES_LINUX=yes -DWIT
  -DENABLE_OSCAP_UTIL_DOCKER=no \
  "
  -EXTRA_OECONF_class-native += "-DENABLE_PROBES=True"
STAGING_OSCAP_DIR = "${TMPDIR}/work-shared/${MACHINE}/oscap-source"
  STAGING_OSCAP_BUILDDIR = 
"${TMPDIR}/work-shared/openscap/oscap-build-artifacts"
@@ -33,9 +32,9 @@ STAGING_OSCAP_BUILDDIR = 
"${TMPDIR}/work-shared/openscap/oscap-build-artifacts"
  EXTRANATIVEPATH += "chrpath-native"
do_configure_append_class-native () {
-sed -i 's:OSCAP_DEFAULT_CPE_PATH.*$:OSCAP_DEFAULT_CPE_PATH 
"${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/cpe":' ${S}/config.h
-sed -i 's:OSCAP_DEFAULT_SCHEMA_PATH.*$:OSCAP_DEFAULT_SCHEMA_PATH 
"${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/schemas":' ${S}/config.h
-sed -i 's:OSCAP_DEFAULT_XSLT_PATH.*$:OSCAP_DEFAULT_XSLT_PATH 
"${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/xsl":' ${S}/config.h
+sed -i 's:OSCAP_DEFAULT_CPE_PATH.*$:OSCAP_DEFAULT_CPE_PATH 
"${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/cpe":' ${B}/config.h
+sed -i 's:OSCAP_DEFAULT_SCHEMA_PATH.*$:OSCAP_DEFAULT_SCHEMA_PATH 
"${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/schemas":' ${B}/config.h
+sed -i 's:OSCAP_DEFAULT_XSLT_PATH.*$:OSCAP_DEFAULT_XSLT_PATH 
"${STAGING_OSCAP_BUILDDIR}${datadir_native}/openscap/xsl":' ${B}/config.h
  }
do_clean[cleandirs] += " ${STAGING_OSCAP_BUILDDIR}"
diff --git 
a/meta-security-compliance/recipes-openscap/openscap/openscap_1.3.1.bb 
b/meta-security-compliance/recipes-openscap/openscap/openscap_1.3.1.bb
new file mode 100644
index 000..c29fd42
--- /dev/null
+++ b/meta-security-compliance/recipes-openscap/openscap/openscap_1.3.1.bb
@@ -0,0 +1,10 @@
+SUMARRY = "NIST Certified SCAP 1.2 toolkit"
+
+require openscap.inc
+
+SRCREV = "3a4c635691380fa990a226acc8558db35d7ebabc"
+SRC_URI = "git://github.com/OpenSCAP/openscap.git;branch=maint-1.3 \
+   file://run-ptest \
+"
+
+DEFAULT_PREFERENCE = "-1"
diff --git a/meta-security-compliance/recipes-openscap/openscap/openscap_git.bb 
b/meta-security-compliance/recipes-openscap/openscap/openscap_git.bb
index 3dfa99e..aded920 100644
--- a/meta-security-compliance/recipes-openscap/openscap/openscap_git.bb
+++ b/meta-security-compliance/recipes-openscap/openscap/openscap_git.bb
@@ -3,9 +3,9 @@
SUMARRY = "NIST Certified SCAP 1.2 toolkit with OE changes"