Re: [OE-core] systemd-getty-generator present but undesired

2020-07-29 Thread Khem Raj
On 7/28/20 6:33 AM, Mike Looijmans wrote: I had a hard time getting a serial attached bluetooth device to work, untilI discovered that systemd is running a "getty" on that port (which happens tobe "ttyS0"). The cause is that "systemd-getty-generator" detects that the port comes online

Re: [OE-core] [PATCH] meson: use the more specific cpu arch in cross file

2020-07-29 Thread Khem Raj
On 7/25/20 6:56 PM, Ruslan Babayev wrote: 'cpu' unlike 'cpu_family' must be a more specific subtype for the CPU. since mcpu/march should provide the right values already, do we need this additional logic in meson? dont we get needed settings to meson already? perhaps you can describe

Re: [OE-core] [PATCHv2] ltp: remove OOM tests from runtest/mm

2020-07-29 Thread Matthew
Khem Raj writes: > On Wed, Jul 29, 2020 at 8:27 PM Mingde (Matthew) Zeng > wrote: >> >> >> Khem Raj writes: >> >> > on master-next I am also seeing >> > >> > step1b: WARNING: ltp-20200515-r0 do_patch: QA Issue: Patch log >> > indicates that patches do not apply cleanly. [patch-fuzz] >> > >> >

[OE-core] [PATCHv3] ltp: remove OOM tests from runtest/mm

2020-07-29 Thread Matthew
[YOCTO #13802] Remove the OOM tests, since they might cause oeqa ssh connection lost. Signed-off-by: Mingde (Matthew) Zeng --- ...001-Remove-OOM-tests-from-runtest-mm.patch | 34 +++ meta/recipes-extended/ltp/ltp_20200515.bb | 1 + 2 files changed, 35 insertions(+) create

[OE-core][dunfell 00/17] Pull request (cover letter only)

2020-07-29 Thread Steve Sakoman
The following changes since commit ea886d57db917a41a0d106a15e1e96c72d6407b0: kernel-yocto: account for extracted defconfig in elements check (2020-07-23 04:07:37 -1000) are available in the Git repository at: git://git.openembedded.org/openembedded-core-contrib stable/dunfell-next

Re: [OE-core] [PATCHv2] ltp: remove OOM tests from runtest/mm

2020-07-29 Thread Khem Raj
On Wed, Jul 29, 2020 at 8:27 PM Mingde (Matthew) Zeng wrote: > > > Khem Raj writes: > > > on master-next I am also seeing > > > > step1b: WARNING: ltp-20200515-r0 do_patch: QA Issue: Patch log > > indicates that patches do not apply cleanly. [patch-fuzz] > > > > I wonder if its related to this

Re: [OE-core] [PATCHv2] ltp: remove OOM tests from runtest/mm

2020-07-29 Thread Matthew
Khem Raj writes: > on master-next I am also seeing > > step1b: WARNING: ltp-20200515-r0 do_patch: QA Issue: Patch log > indicates that patches do not apply cleanly. [patch-fuzz] > > I wonder if its related to this as well. My bad. Just a couple days ago ltp master introduced a commit directly

Re: [OE-core] [yocto] QA notification for completed autobuilder build (yocto-3.1.2.rc1)

2020-07-29 Thread Sangeeta Jain
Thanks, sangeeta > -Original Message- > From: akuster808 > Sent: Thursday, 30 July, 2020 7:51 AM > To: Jain, Sangeeta ; yo...@lists.yoctoproject.org; > openembedded-core > Cc: ota...@ossystems.com.br; yi.z...@windriver.com; Sangal, Apoorv > ; Yeoh, Ee Peng ; Chan, > Aaron Chun Yew ; >

Re: [OE-core] [poky][zeus][PATCH] libpcre: Add fix for CVE-2020-14155

2020-07-29 Thread Anuj Mittal
On Wed, 2020-07-29 at 18:25 +0530, saloni wrote: > From: Rahul Taya > > Added below patch in libpcre > CVE-2020-14155.patch > > This patch fixes below error: > PCRE could allow a remote attacker to execute arbitrary > code on the system, caused by an integer overflow in > libpcre via a large

Re: [OE-core] [yocto] QA notification for completed autobuilder build (yocto-3.1.2.rc1)

2020-07-29 Thread akuster
On 7/28/20 11:22 PM, Jain, Sangeeta wrote: > Hi All, > > This is the QA report for yocto-3.1.2.rc1: > https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults Is QA still having to perform the Manual test remotely? -armin > > === Summary

Re: [OE-core] [PATCHv2] ltp: remove OOM tests from runtest/mm

2020-07-29 Thread Khem Raj
on master-next I am also seeing step1b: WARNING: ltp-20200515-r0 do_patch: QA Issue: Patch log indicates that patches do not apply cleanly. [patch-fuzz] I wonder if its related to this as well. On Wed, Jul 29, 2020 at 6:43 AM Richard Purdie wrote: > > On Wed, 2020-07-29 at 09:41 -0400, Mingde

Re: [OE-core] Why disable NEON support in recipes if runtime detection works?

2020-07-29 Thread Andre McCurdy
On Wed, Jul 29, 2020 at 6:46 AM Tanu Kaskinen wrote: > > On Mon, 2020-07-27 at 13:45 -0700, Andre McCurdy wrote: > > On Sun, Jul 26, 2020 at 7:01 AM Khem Raj wrote: > > > On Sun, Jul 26, 2020 at 12:59 AM Tanu Kaskinen wrote: > > > > On Sun, 2020-07-26 at 09:27 +0300, Tanu Kaskinen wrote: > > >

Re: [OE-core] [PATCH] meson: use the more specific cpu arch in cross file

2020-07-29 Thread Ruslan Babayev
Hi Ross, What do you think of the patch? Any objections to merging it? Do you have any feedback? Thanks, Ruslan On Mon, Jul 27, 2020 at 12:03 PM Ruslan Babayev wrote: > Hi Ross, > > According to https://mesonbuild.com/Cross-compilation.html > > There are two different values for the CPU. The

Re: [OE-core] [meta-oe][PATCH 0/3] Log colorizer

2020-07-29 Thread Chris Laplante via lists.openembedded.org
Hi Richard, > This looks interesting. Could we add something to the manual about how to > use it and maybe a test for it as well please? Halfway through writing the tests, and I realized LOG_COLORIZER_SUPPRESS_COLORIZED_OUTPUT doesn’t quite work. I wrote a test recipe with a do_compile that

Re: [OE-core] [PATCH] qemumips: Use 34Kf CPU emulation

2020-07-29 Thread Khem Raj
On Wed, Jul 29, 2020 at 3:13 AM Richard Purdie wrote: > > On Wed, 2020-07-29 at 10:56 +0100, Richard Purdie via > lists.openembedded.org wrote: > > On Tue, 2020-07-28 at 19:28 -0700, Khem Raj wrote: > > > Few years ago we switched to using mips32r2 tunings for qemumips > > > however > > > the

Re: [OE-core] [poky][zeus][PATCH] libpcre: Add fix for CVE-2020-14155

2020-07-29 Thread Khem Raj
On Wed, Jul 29, 2020 at 5:56 AM Saloni Jain wrote: > > From: Rahul Taya > > Added below patch in libpcre > CVE-2020-14155.patch > > This patch fixes below error: > PCRE could allow a remote attacker to execute arbitrary > code on the system, caused by an integer overflow in > libpcre via a large

Re: [OE-core] [PATCH] kernel-fitimage: build configuration for image tree when dtb is not present

2020-07-29 Thread Usama Arif
On 28/07/2020 11:19, Usama Arif wrote: On 27/07/2020 11:56, Richard Purdie wrote: On Mon, 2020-07-20 at 18:21 +0100, Usama Arif wrote: On 20/07/2020 08:41, Richard Purdie via lists.openembedded.org wrote: On Fri, 2020-07-17 at 15:19 +0100, Usama Arif wrote: This patch adds support for

Re: [OE-core] [PATCH] oeqa/selftest/imagefeatures: Add testcase for fitImage

2020-07-29 Thread Usama Arif
On 29/07/2020 15:41, Usama Arif wrote: This testcase generates the Image Tree Source and the corresponding fitImage containing a kernel and a ramdisk. It then checks if the these files exist and if the right fields are present in the right order in the Image Tree Source. Tested with:

[OE-core] [PATCH] oeqa/selftest/imagefeatures: Add testcase for fitImage

2020-07-29 Thread Usama Arif
This testcase generates the Image Tree Source and the corresponding fitImage containing a kernel and a ramdisk. It then checks if the these files exist and if the right fields are present in the right order in the Image Tree Source. Tested with: oe-selftest -r

Re: [OE-core] [meta-oe][PATCH 0/3] Log colorizer

2020-07-29 Thread Chris Laplante via lists.openembedded.org
Hi Richard, > You can run these tests individually with "oe-selftest -r imagefeatures" to > run > that file or "oe-selftest -r imagefeatures.ImageFeatures.test_bmap" as an > example of a specific test. I'm developing the tests for log colorizer and I had a question about oe-selftest. Is there

[OE-core] ✗ patchtest: failure for boost: backport fix to make async_pipes work with asio

2020-07-29 Thread Patchwork
== Series Details == Series: boost: backport fix to make async_pipes work with asio Revision: 1 URL : https://patchwork.openembedded.org/series/25388/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests

Re: [OE-core] Why disable NEON support in recipes if runtime detection works?

2020-07-29 Thread Tanu Kaskinen
On Mon, 2020-07-27 at 13:45 -0700, Andre McCurdy wrote: > On Sun, Jul 26, 2020 at 7:01 AM Khem Raj wrote: > > On Sun, Jul 26, 2020 at 12:59 AM Tanu Kaskinen wrote: > > > On Sun, 2020-07-26 at 09:27 +0300, Tanu Kaskinen wrote: > > > > On Mon, 2020-07-20 at 15:26 -0700, Khem Raj wrote: > > > > >

Re: [OE-core] [PATCHv2] ltp: remove OOM tests from runtest/mm

2020-07-29 Thread Richard Purdie
On Wed, 2020-07-29 at 09:41 -0400, Mingde (Matthew) Zeng wrote: > Richard Purdie writes: > > > On Wed, 2020-07-29 at 09:09 -0400, Matthew wrote: > > > Fixes [YOCTO #13802] > > > > Thanks, we can reference the bug but I don't think we can yet claim > > it > > fixes it. > > Sure, would something

Re: [OE-core] [PATCHv2] ltp: remove OOM tests from runtest/mm

2020-07-29 Thread Matthew
Richard Purdie writes: > On Wed, 2020-07-29 at 09:09 -0400, Matthew wrote: >> Fixes [YOCTO #13802] > > Thanks, we can reference the bug but I don't think we can yet claim it > fixes it. Sure, would something like the following work? Reference [YOCTO #13802] > > The missing log issue happened

[OE-core] [dunfell][PATCH] boost: backport fix to make async_pipes work with asio

2020-07-29 Thread Viktor Rosendahl
From: Viktor Rosendahl async_pipe is missing the executor_type type, which is expected by asio in /usr/include/boost/asio/impl/read.hpp. Without this, it's not possible to even compile code that uses constructs such as: boost::asio::io_service foo; boost::process::async_pipe foopipe{

Re: [OE-core] [PATCHv2] ltp: remove OOM tests from runtest/mm

2020-07-29 Thread Richard Purdie
On Wed, 2020-07-29 at 09:09 -0400, Matthew wrote: > Fixes [YOCTO #13802] Thanks, we can reference the bug but I don't think we can yet claim it fixes it. The missing log issue happened again: https://autobuilder.yoctoproject.org/typhoon/#/builders/96/builds/908 so I think there are multiple

[OE-core] [PATCHv2] ltp: remove OOM tests from runtest/mm

2020-07-29 Thread Matthew
Fixes [YOCTO #13802] Remove the OOM tests, since they might cause oeqa ssh connection lost. Signed-off-by: Mingde (Matthew) Zeng --- ...001-Remove-OOM-tests-from-runtest-mm.patch | 33 +++ meta/recipes-extended/ltp/ltp_20200515.bb | 1 + 2 files changed, 34 insertions(+)

[OE-core] ✗ patchtest: failure for libpcre: Add fix for CVE-2020-14155

2020-07-29 Thread Patchwork
== Series Details == Series: libpcre: Add fix for CVE-2020-14155 Revision: 1 URL : https://patchwork.openembedded.org/series/25384/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed

Re: [OE-core] [PATCH] ltp: remove OOM tests from runtest/mm

2020-07-29 Thread Matthew
Error, please ignore. Matthew writes: > Fixes [YOCTO #13802] > > Temporarily remove the OOM tests, since they might cause oeqa ssh > connection lost. > > Let's wait for a week or two to see if the error stops occuring. > > Signed-off-by: Mingde (Matthew) Zeng > --- >

Re: [OE-core] recipes-devtools/gcc: gcc-Fix-argument-list-too-long-error.patch is buggy

2020-07-29 Thread Richard Purdie
On Sun, 2020-07-26 at 08:20 -0700, qiuguang@alibaba-inc.com wrote: > A few days ago, I tried to compile a gcc plugin with the toolchain from poky > sdk. > It failed with errors about missing header files such as backend.h etc. > > After investigation, I found that the problem was brought by

[OE-core] [poky][zeus][PATCH] libpcre: Add fix for CVE-2020-14155

2020-07-29 Thread saloni
From: Rahul Taya Added below patch in libpcre CVE-2020-14155.patch This patch fixes below error: PCRE could allow a remote attacker to execute arbitrary code on the system, caused by an integer overflow in libpcre via a large number after (?C substring. By sending a request with a large number,

[OE-core] [PATCH] ltp: remove OOM tests from runtest/mm

2020-07-29 Thread Matthew
Fixes [YOCTO #13802] Temporarily remove the OOM tests, since they might cause oeqa ssh connection lost. Let's wait for a week or two to see if the error stops occuring. Signed-off-by: Mingde (Matthew) Zeng --- ...001-Remove-OOM-tests-from-runtest-mm.patch | 33 +++ 1 file

Re: [OE-core] archiver.bbclass and GIT repositories

2020-07-29 Thread Christian Eggers
On Wednesday, 29 July 2020, 11:42:25 CEST, Paul Barker wrote: > On Tue, 28 Jul 2020 at 13:56, Christian Eggers wrote: > > ... > > So I have three questions: > > 1. Is it possible to archive the git project in a way, that the GIT > > history > > can be examined later? > > 2. If this is not

Re: [OE-core] [PATCH] qemumips: Use 34Kf CPU emulation

2020-07-29 Thread Richard Purdie
On Wed, 2020-07-29 at 10:56 +0100, Richard Purdie via lists.openembedded.org wrote: > On Tue, 2020-07-28 at 19:28 -0700, Khem Raj wrote: > > Few years ago we switched to using mips32r2 tunings for qemumips > > however > > the default CPU emulation still remained 24Kf which is not optimal > > for >

Re: [OE-core] [PATCH] qemumips: Use 34Kf CPU emulation

2020-07-29 Thread Richard Purdie
On Tue, 2020-07-28 at 19:28 -0700, Khem Raj wrote: > Few years ago we switched to using mips32r2 tunings for qemumips however > the default CPU emulation still remained 24Kf which is not optimal for > mips32r2 ISA for qemu [1], therefore switch to recommended 32Kf for CPU > emulation when running

Re: [OE-core] archiver.bbclass and GIT repositories

2020-07-29 Thread Paul Barker
On Tue, 28 Jul 2020 at 13:56, Christian Eggers wrote: > > In my project, the linux kernel (together with dozens of our changes) is kept > in a company internal GIT repository. The GPLv2 requires the following: > > > 2a) You must cause the modified files to carry prominent notices stating > > that

Re: [OE-core] [PATCH] ltp.py: remove mm from ltp_groups

2020-07-29 Thread Richard Purdie
On Tue, 2020-07-28 at 16:43 -0400, Matthew wrote: > Fixes [YOCTO #13802] > > Temporary disable mm test for a while, since it calls the OOM tests. > See ltp-git/runtest/mm: > oom01 oom01 > oom02 oom02 > oom03 oom03 > oom04 oom04 > oom05 oom05 > > Let's wait for a week or two

Re: [OE-core] sdk package_arch and yum

2020-07-29 Thread Richard Purdie
On Wed, 2020-07-29 at 14:33 +1200, Douglas via lists.openembedded.org wrote: > I was unable to install my nativesdk packages on CentOS using yum, as > the package architecture was set to "x86_64_nativesdk". My web- > digging revealed no work-around I could use for yum. This is not what the

[OE-core] [PATCH] libwpe: update to 1.7.1

2020-07-29 Thread Oleksandr Kravchuk
Signed-off-by: Oleksandr Kravchuk --- meta/recipes-sato/webkit/{libwpe_1.6.0.bb => libwpe_1.7.1.bb} | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) rename meta/recipes-sato/webkit/{libwpe_1.6.0.bb => libwpe_1.7.1.bb} (82%) diff --git a/meta/recipes-sato/webkit/libwpe_1.6.0.bb

[OE-core] [PATCH] nativesdk-rpm: adjust RPM_CONFIGDIR paths dynamically

2020-07-29 Thread hongxu
While installing/extracting SDK to a non-default dir(not /opt), run rpm failed: $ python3 -c "import rpm" |error: Unable to open /opt/windriver/wrlinux-graphics/20.31/sysroots/ x86_64-wrlinuxsdk-linux/usr/lib/rpm/rpmrc for reading: No such file or directory. This patch adds a flexible way to

[OE-core] [PATCH] pbzip2: extend for nativesdk

2020-07-29 Thread Yi Zhao
Make pzip2 available in nativesdk to speedup file compression. Signed-off-by: Yi Zhao --- meta/recipes-extended/pbzip2/pbzip2_1.1.13.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-extended/pbzip2/pbzip2_1.1.13.bb

Re: [OE-core] [yocto] QA notification for completed autobuilder build (yocto-3.1.2.rc1)

2020-07-29 Thread Sangeeta Jain
Hi All, This is the QA report for yocto-3.1.2.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults === Summary No high milestone defects. No new defects are found in this cycle. Thanks, Sangeeta > -Original Message-