[OE-core] [oe-core][PATCH] uftrace: Add recipe

- Add recipe for uftrace v0.7. - Support x86_64, arm (v6 or later), and aarch64. - Disable for armv4 and armv5 in arm architecture which is only supported armv6 or later. - Attached 2 patches is merged to upstream. Signed-off-by: Changhyeok Bae --- .../0001-Makefile-Add-LDFLAGS-in-export.patch

[OE-core] how to check which package is installed for specific image, and whey it is installed?

Hello, I checked the 'taskexp', but can't get what I want. I want to know what package is installed, and why it is installed, indeed, for 'systemd-vconsole-setup'. Thanks! Yi Qingliang -- ___ Openembedded-core mailing list Openembedded-core@lists.ope

Re: [OE-core] [PATCH 3/6] linux-yocto/4.1: update to v4.1.41

On Thu, Jul 13, 2017 at 4:57 PM, Cal Sullivan < california.l.sulli...@intel.com> wrote: > It occurred with qemux86-64 rather than genericx86-64, so your new patch > for 4.1 should fix it. > that explains my confusion. I wonder if I wandered into the wrong autobuilder link .. I did have to browse

Re: [OE-core] [oe-core][PATCH 1/1] valgrind: allow version 3.12 to build under gcc7

On Thu, Jul 13, 2017 at 5:24 PM, Joe Slater wrote: > Building for powerpc64 fails because of erroneous assertions > that register r2 is clobbered. This has probably been fixed > in version 3.13. > there were patches for 3.13 posted. lets make that work for you. > Signed-off-by: Joe Slater > --

[OE-core] ✗ patchtest: failure for valgrind - gcc7 and powerpc64

== Series Details == Series: valgrind - gcc7 and powerpc64 Revision: 1 URL : https://patchwork.openembedded.org/series/7738/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the pr

[OE-core] [oe-core][PATCH 0/1] valgrind - gcc7 and powerpc64

This probably could do no harm since the actual code generated does not seem to have changed between gcc6 and gcc7, and is not affected by this patch except that without it, valgrind ppc64 won't compile. There must also be a gcc7 bug, since if it is ok to clobber r2 for ppc32 it is unlikely it is

[OE-core] [oe-core][PATCH 1/1] valgrind: allow version 3.12 to build under gcc7

Building for powerpc64 fails because of erroneous assertions that register r2 is clobbered. This has probably been fixed in version 3.13. Signed-off-by: Joe Slater --- .../valgrind/valgrind/wait-for-3.13.patch | 40 ++ meta/recipes-devtools/valgrind/valgrind_3.12.0.

[OE-core] ✗ patchtest: failure for python3: fix weakref spewing exceptions during interp finalization

== Series Details == Series: python3: fix weakref spewing exceptions during interp finalization Revision: 1 URL : https://patchwork.openembedded.org/series/7736/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Sever

Re: [OE-core] [PATCH 3/6] linux-yocto/4.1: update to v4.1.41

It occurred with qemux86-64 rather than genericx86-64, so your new patch for 4.1 should fix it. --- Cal On 07/13/2017 09:50 AM, Bruce Ashfield wrote: On 07/13/2017 12:40 PM, Burton, Ross wrote: On 13 July 2017 at 17:33, Bruce Ashfield mailto:bruce.ashfi...@windriver.com>> wrote: How

[OE-core] [PATCH] python3: fix weakref spewing exceptions during interp finalization

When py3 applications are exiting we often see errors similar to the following: Exception ignored in: .remove at 0x7fcb56b09400> Traceback (most recent call last): File "/usr/lib64/python3.5/weakref.py", line 117, in remove TypeError: 'NoneType' object is not callable After a quick search th

[OE-core] ✗ patchtest: failure for libgcrypt: fix CVE-2017-9526 (rev2)

== Series Details == Series: libgcrypt: fix CVE-2017-9526 (rev2) Revision: 2 URL : https://patchwork.openembedded.org/series/7732/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on

[OE-core] ✗ patchtest: failure for libgcrypt: fix CVE-2017-9526

== Series Details == Series: libgcrypt: fix CVE-2017-9526 Revision: 1 URL : https://patchwork.openembedded.org/series/7732/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been executed on the pro

[OE-core] [PATCH][pyro] libgcrypt: fix CVE-2017-9526

In libgcrypt before 1.7.7, an attacker who learns the EdDSA session key (from side-channel observation during the signing process) can easily recover the long-term secret key. 1.7.7 makes a cipher/ecc-eddsa.c change to store this session key in secure memory, to ensure that constant-time point oper

[OE-core] [PATCH] libgcrypt: upgrade to 1.7.7

Signed-off-by: Ross Burton --- meta/recipes-support/libgcrypt/libgcrypt_1.7.6.bb | 4 meta/recipes-support/libgcrypt/libgcrypt_1.7.7.bb | 4 2 files changed, 4 insertions(+), 4 deletions(-) delete mode 100644 meta/recipes-support/libgcrypt/libgcrypt_1.7.6.bb create mode 100644 meta/re

[OE-core] [PATCH][morty] libgcrypt: fix CVE-2017-9526

In libgcrypt before 1.7.7, an attacker who learns the EdDSA session key (from side-channel observation during the signing process) can easily recover the long-term secret key. 1.7.7 makes a cipher/ecc-eddsa.c change to store this session key in secure memory, to ensure that constant-time point oper

Re: [OE-core] [PATCH 3/6] linux-yocto/4.1: update to v4.1.41

On 07/13/2017 12:40 PM, Burton, Ross wrote: On 13 July 2017 at 17:33, Bruce Ashfield > wrote: How would you like the fix, a completely new patch, or an incremental fix on my branch ? Sent. Note: It says "v2", but I did change the shortlog to re

[OE-core] [v2 PATCH] linux-yocto/4.1: update to v4.1.42

Integrating the korg -stable update that comprises the following commits: 2ac51e21d8c5 Linux 4.1.42 dcda279dede7 mm: fix new crash in unmapped_area_topdown() 8b18c6b2a0dd mm: larger stack guard gap, between vmas 55e6060ddd5f alarmtimer: Rate limit periodic intervals cedbfb3dc38c MIP

Re: [OE-core] [PATCH 3/6] linux-yocto/4.1: update to v4.1.41

On 13 July 2017 at 17:33, Bruce Ashfield wrote: > How would you like the fix, a completely new patch, or an incremental > fix on my branch ? > A replacement patch please, it's not in master yet. Ross -- ___ Openembedded-core mailing list Openembedded

Re: [OE-core] [PATCH 3/6] linux-yocto/4.1: update to v4.1.41

On 07/12/2017 06:17 PM, Burton, Ross wrote: On 11 July 2017 at 16:04, Bruce Ashfield > wrote: > > Integrating the korg -stable update that comprises the following > commits: I'm guessing this is the cause of this failure with poky-lsb on qemux86-64. I

Re: [OE-core] [PATCHv2 00/29] oeqa core and oe-selftest threaded enablement

I found some other races in the test cases execution, i will send a v3. Cheers, Anibal On 07/12/2017 02:36 PM, Aníbal Limón wrote: > The v2 address comments did by Patrick about add better explanation > on the commit messages and some typos. > > Other interesting information to add is that with

Re: [OE-core] [PATCHv2 04/29] bb/tinfoil: run_command handle busy status in bitbake server

On 07/13/2017 10:20 AM, Christopher Larson wrote: > On Wed, Jul 12, 2017 at 12:36 PM, Aníbal Limón > wrote: > >> When tinfoil request a command to bitbake is handled in async >> manner [1], sometimes is this ends on return a Busy status. >> >> This is a workaround a needs to be fixed in proper m

Re: [OE-core] [PATCHv2 04/29] bb/tinfoil: run_command handle busy status in bitbake server

On Wed, Jul 12, 2017 at 12:36 PM, Aníbal Limón wrote: > When tinfoil request a command to bitbake is handled in async > manner [1], sometimes is this ends on return a Busy status. > > This is a workaround a needs to be fixed in proper manner > inside bitbake code. > I’m assuming you verified thi

Re: [OE-core] ✗ patchtest: failure for initramfs-framework: include install module in recipe for installation

On Thu, 2017-07-13 at 06:36 +, Ng, Wei Tee wrote: > The reason for this patchtest failure is because of this patch have a > dependency on another patch which is: > initramfs-framework: module to support boot live image > Here you go for the link of this patch: > http://lists.openembedde

Re: [OE-core] Reasons for reverting "openssl: prevent ABI break from earlier krogoth releases" ?

It was applied in fido, because fido was released with old version-script and upgrade to 1.0.2h changed the ABI. krogoth on the other hand was released with this new ABI, so applying this partial revert in krogoth would cause ABI changes in different revisions in krogoth branch. You can find a bi

Re: [OE-core] [oe] State of bitbake world, Failed tasks 2017-07-11

On Thu, Jul 13, 2017 at 3:14 AM, Martin Jansa wrote: > Shouldn't but one still slipped in: > http://errors.yoctoproject.org/Errors/Details/147438/ > I do not test with systemd regularly. But this patch should be applied to this recipe too http://git.openembedded.org/openembedded-core/commit/?id=

Re: [OE-core] [PATCH 6/6] libbsd: 0.8.3 -> 0.8.5

On Thu, Jul 13, 2017 at 4:10 AM, Robert Yang wrote: > > > On 07/13/2017 05:45 PM, Burton, Ross wrote: >> >> >> On 13 July 2017 at 10:40, Burton, Ross > > wrote: >> >> Determining if any of those can be applied always would be good. >> >> >> FWIW it looks like the

[OE-core] [PATCH] webkitgtk: Upgrade to 2.16.5

Adjust some dependencies: libgcrypt is now required (instead of gnutls) and the following build deps where missing: gettext-native, glib-2.0 and glib-2.0-native. Also the CMake argument ENABLE_CREDENTIAL_STORAGE has been renamed to USE_LIBSECRET. This new upstream release (2.16.4 actually) includ

[OE-core] Reasons for reverting "openssl: prevent ABI break from earlier krogoth releases" ?

Back on the Krogoth branch, there was a changed applied briefly last year to smooth over some symbol-versioning breakage that occurred when OpenSSL got upgraded past version 1.0.2g: openssl: prevent ABI break from earlier krogoth releases The backported upgrade to 1.0.2h included an updat

Re: [OE-core] [PATCH 4/6] git: 2.11.1 -> 2.13.2

On 07/12/2017 09:55 PM, Robert Yang wrote: > > > On 07/12/2017 11:38 PM, Leonardo Sandoval wrote: >> for some reason git did not detect (as other patches in this series) >> the renaming (delete/create), make it easier to review. >> > > By default, git format-patch handles similarity > 50% as rena

[OE-core] ✗ patchtest: failure for openssh: Atomically generate host keys (rev10)

== Series Details == Series: openssh: Atomically generate host keys (rev10) Revision: 10 URL : https://patchwork.openembedded.org/series/6626/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been

[OE-core] [PATCH v10] openssh: Atomically generate host keys

Generating the host keys atomically prevents power interruptions during the first boot from leaving the key files incomplete, which often prevents users from being able to ssh into the device. [YOCTO #11671] Signed-off-by: Joshua Watt --- .../openssh/openssh/sshd_check_keys| 42

Re: [OE-core] [PATCH 6/6] libbsd: 0.8.3 -> 0.8.5

On 07/13/2017 05:45 PM, Burton, Ross wrote: On 13 July 2017 at 10:40, Burton, Ross mailto:ross.bur...@intel.com>> wrote: Determining if any of those can be applied always would be good. FWIW it looks like the __BEGIN_DECLS patch still isn't upstream, but the other two may have been reso

Re: [OE-core] [oe] State of bitbake world, Failed tasks 2017-07-11

Shouldn't but one still slipped in: http://errors.yoctoproject.org/Errors/Details/147438/ Thanks again for great work preparing the new toolchain. On Wed, Jul 12, 2017 at 6:34 PM, Khem Raj wrote: > On Wed, Jul 12, 2017 at 1:57 AM, Martin Jansa > wrote: > > http://www.openembedded.org/wiki/Bitb

Re: [OE-core] [PATCH 2/6] cryptodev: 1.8 -> 1.9

On 07/13/2017 05:50 PM, Burton, Ross wrote: On 13 July 2017 at 03:51, Robert Yang mailto:liezhi.y...@windriver.com>> wrote: BTW, I sent a meta-gplv2 patch to p...@yoctoproject.org two days ago, but I didn't find it in p...@yoctoproject.org

Re: [OE-core] [PATCH 2/6] cryptodev: 1.8 -> 1.9

On 13 July 2017 at 03:51, Robert Yang wrote: > BTW, I sent a meta-gplv2 patch to p...@yoctoproject.org two days ago, but > I didn't find it in p...@yoctoproject.org, Ross, did you see it, please ? > Maybe I should send it again. > The list is yo...@yoctoproject.org. Please resend to the list.

Re: [OE-core] [PATCH 6/6] libbsd: 0.8.3 -> 0.8.5

On 13 July 2017 at 10:40, Burton, Ross wrote: > Determining if any of those can be applied always would be good. > FWIW it looks like the __BEGIN_DECLS patch still isn't upstream, but the other two may have been resolved. Ross -- ___ Openembedded-cor

Re: [OE-core] [PATCH 6/6] libbsd: 0.8.3 -> 0.8.5

On 12 July 2017 at 11:15, Robert Yang wrote: > * The LIC_FILES_CHKSUM is changed becauses the files updated the date, and > added > a BSD-3-clause-John-Birrell for man/timeradd.3bsd, this license is > already > there for other files. > The musl-specific patches don't apply: Applying patch 0

[OE-core] [PATCH] apr: 1.5.2 -> 1.6.2

Update apr from 1.5.2 to 1.6.2 Signed-off-by: Fan Xin --- meta/recipes-support/apr/{apr_1.5.2.bb => apr_1.6.2.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-support/apr/{apr_1.5.2.bb => apr_1.6.2.bb} (96%) diff --git a/meta/recipes-support/apr/apr_1.5.2.bb b

Re: [OE-core] [PATCH 1/3] pkgconf: add recipe

Hi Ross, On Wed, Jul 12, 2017 at 11:13:58PM +0100, Burton, Ross wrote: >>On 11 July 2017 at 13:58, Maxin B. John wrote: >> Move pkgconf recipe to oe-core from meta-pkgconf: >>https://github.com/kergoth/meta-kergoth-wip/tree/master/meta-pkgconf > >Fails under mingw, which is a regression compared