Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.4.rc2)

2019-10-17 Thread Jain, Sangeeta
Hello All, Intel and WR YP QA is planning for QA execution for YP build yocto-2.6.4.rc2. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1. OE-Core 2. BSP-hw 3. BSP-Qemu Runtime auto test for following platforms: 1. MinnowTurbot 32-bit 2.

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.4.rc2)

2019-10-17 Thread akuster808
On 10/17/19 7:01 PM, Jain, Sangeeta wrote: > > >> -Original Message- >> From: yocto-boun...@yoctoproject.org On >> Behalf Of akuster >> Sent: Friday, 18 October, 2019 6:53 AM >> To: yocto@yoctoproject.org >> Cc: akuster...@gmail.com; Chan, Aaron Chun Yew >> ; ota...@ossystems.com.br >>

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.4.rc2)

2019-10-17 Thread Jain, Sangeeta
>-Original Message- >From: yocto-boun...@yoctoproject.org On >Behalf Of akuster >Sent: Friday, 18 October, 2019 6:53 AM >To: yocto@yoctoproject.org >Cc: akuster...@gmail.com; Chan, Aaron Chun Yew >; ota...@ossystems.com.br >Subject: Re: [yocto] QA notification for completed

Re: [yocto] QA notification for completed autobuilder build (yocto-2.6.4.rc2)

2019-10-17 Thread akuster
Can we get 2.6.4-rc2 in a QA queue for the next dot release? - armin On 10/17/19 2:17 PM, Poky Build User wrote: > A build flagged for QA (yocto-2.6.4.rc2) was completed on the autobuilder and > is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-2.6.4.rc2 > > > Build

[yocto] QA notification for completed autobuilder build (yocto-2.6.4.rc2)

2019-10-17 Thread Poky Build User
A build flagged for QA (yocto-2.6.4.rc2) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-2.6.4.rc2 Build hash information: bitbake: 6b045e074c6fea97d4e305a5a3c8bf82135d95eb meta-gplv2: aabc30f3bd03f97326fb8596910b94639fea7575

[yocto] [meta-security][v3][PATCH] apparmor: ptest fail to build on arm

2019-10-17 Thread Armin Kuster
exclude arm and aarch64 ptest tasks [v2&3] Sent before committing. Signed-off-by: Armin Kuster --- recipes-mac/AppArmor/apparmor_2.13.3.bb | 18 ++ 1 file changed, 18 insertions(+) diff --git a/recipes-mac/AppArmor/apparmor_2.13.3.bb b/recipes-mac/AppArmor/apparmor_2.13.3.bb

[yocto] [meta-security][v2][PATCH] apparmor: ptest fail to build on arm

2019-10-17 Thread Armin Kuster
exclude arm and aarch64 ptest tasks Signed-off-by: Armin Kuster --- recipes-mac/AppArmor/apparmor_2.13.3.bb | 22 ++ 1 file changed, 22 insertions(+) diff --git a/recipes-mac/AppArmor/apparmor_2.13.3.bb b/recipes-mac/AppArmor/apparmor_2.13.3.bb index d434fd3..ba7065b

[yocto] [meta-security][PATCH] apparmor: ptest fail to build on arm

2019-10-17 Thread Armin Kuster
exclude arm and aarch64 ptest tasks Signed-off-by: Armin Kuster --- recipes-mac/AppArmor/apparmor_2.13.3.bb | 22 ++ 1 file changed, 22 insertions(+) diff --git a/recipes-mac/AppArmor/apparmor_2.13.3.bb b/recipes-mac/AppArmor/apparmor_2.13.3.bb index d434fd3..ba7065b

[yocto] qmlimportscanner missing from sdk

2019-10-17 Thread Gurnett, Bjorn
When I build an sdk using do_populate_sdk with a static built meta-qt5, I do not end up with athe qmlimportscanner in my sdk in the usr/bin folder. What am I missing? Qmake is correctly built. Thanks for any help -- ___ yocto mailing list

Re: [yocto] trouble with rootfs generation with mxnet package

2019-10-17 Thread karthik poduval
Hi Ross, Thanks a lot, your analysis was spot on, I followed the recommendation from that wiki you pointed to and it fixed my issue. Really appreciate the quick response. -- Regards, Karthik Poduval On Thu, Oct 17, 2019 at 2:28 AM Ross Burton wrote: > > On 17/10/2019 03:45, karthik poduval

Re: [yocto] meta-selinux | meson-enable-selinux breaks

2019-10-17 Thread Vincent Prince
See patch here https://patchwork.openembedded.org/series/20519/# Le jeu. 17 oct. 2019 à 17:19, Itay Sperling a écrit : > Hi, > I just built Yocto (warrior) with meta-selinux and got this error: > >> meson.build:1:0: ERROR: Value disabled is not boolean (true or false). > > > It appears the

[yocto] [meta-selinux] [Warrior] [PATCH] Revert glib-2.0: fix configure error for meson build

2019-10-17 Thread Vincent Prince
On Warrior branch, glib-2.0 is in version 2.58.3 so we need to revert commit [bb0c9c3abcb] until then. Signed-off-by: Vincent Prince --- classes/meson-enable-selinux.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/classes/meson-enable-selinux.bbclass

[yocto] [meta-selinux] Warrior branch glib/meson problem

2019-10-17 Thread Vincent Prince
Hi Team, I have a problem with meta-selinux layer on warrior branch, especially building glib-2.0 with meson. This commit introduces enabled/disabled flags instead of true/false: http://git.yoctoproject.org/cgit/cgit.cgi/meta-selinux/commit/?h=warrior=bb0c9c3abcb935e4b362eb57985e1ee7fec0bfe0 But

[yocto] meta-selinux | meson-enable-selinux breaks

2019-10-17 Thread Itay Sperling
Hi, I just built Yocto (warrior) with meta-selinux and got this error: > meson.build:1:0: ERROR: Value disabled is not boolean (true or false). It appears the file *classes/meson-enable-selinux.bbclass* has incorrect values. Attached a patch that fixes the problem. Itay [image: Argus Logo]

[yocto] [meta-selinux][PATCH] layer.conf: Add zeus to compat layer

2019-10-17 Thread C.r. Guo
From: Chunrong Guo Signed-off-by: Chunrong Guo --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index 89b9468..30b0518 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -21,7 +21,7 @@ BBFILE_PRIORITY_selinux = "5" #

[yocto] [PATCH] layer.conf: Add zeus to compat layer

2019-10-17 Thread C.r. Guo
From: Chunrong Guo Signed-off-by: Chunrong Guo --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index 89b9468..30b0518 100644 --- a/conf/layer.conf +++ b/conf/layer.conf @@ -21,7 +21,7 @@ BBFILE_PRIORITY_selinux = "5" #

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

2019-10-17 Thread pokybuild
A build flagged for QA (yocto-2.6.4.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-2.6.4.rc1 Build hash information: bitbake: 6b045e074c6fea97d4e305a5a3c8bf82135d95eb meta-gplv2: aabc30f3bd03f97326fb8596910b94639fea7575

[linux-yocto] [PATCH 1/1] xilinx-zynqmp: add kernel options for ZynqMP PL Programming

2019-10-17 Thread quanyang.wang
From: Quanyang Wang Add kernel options for zynqmp FPGA programming. Signed-off-by: Quanyang Wang --- bsp/xilinx-zynqmp/xilinx-zynqmp.cfg | 4 1 file changed, 4 insertions(+) diff --git a/bsp/xilinx-zynqmp/xilinx-zynqmp.cfg b/bsp/xilinx-zynqmp/xilinx-zynqmp.cfg index fe8ae24d..b87c2892

[linux-yocto] [kernel-cache][PATCH 0/1] xilinx-zynqmp: add kernel options for ZynqMP PL Programming

2019-10-17 Thread quanyang.wang
From: Quanyang Wang Hi Bruce, Michal, Would you please help review and merge this patch to yocto-kernel-cache's branch yocto-5.2 and master? Thanks, Quanyang Quanyang Wang (1): xilinx-zynqmp: add kernel options for ZynqMP PL Programming bsp/xilinx-zynqmp/xilinx-zynqmp.cfg | 4 1 file

[yocto] Help needed add own variable to toolchain environment

2019-10-17 Thread Johann Obermayr
Hello, i have trouble to add a own variable to the toolchain environment I see that environment-setup-i586-poky-linx script calls all files in sysroot//environment-setup.d/* But what is the simples and correct way to add follow line (export KSRC...) do_something() { mkdir -p

[yocto] [meta-selinux] [Warrior] [PATCH] Revert glib-2.0: fix configure error for meson build

2019-10-17 Thread Vincent Prince
On Warrior branch, glib-2.0 is in version 2.58.3 so we need to revert commit [bb0c9c3abcb] until then. Signed-off-by: Vincent Prince --- classes/meson-enable-selinux.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/classes/meson-enable-selinux.bbclass

Re: [yocto] trouble with rootfs generation with mxnet package

2019-10-17 Thread Ross Burton
On 17/10/2019 03:45, karthik poduval wrote: Upon looking at the build/tmp/work/aarch64-xilinx-linux/mxnet/1.5.0-r0/packages-split directory I find that the mxnet sub directory is empty, mxnet-dev, mxnet-staticdev have libmxnet.so and libmxnet.a respectively under usr/lib. Don't set PACKAGES,