[OE-core] [PATCH] adwaita-icon-theme: 3.18.0 -> 3.20

1) Upgrade adwaita-icon-theme from 3.18.0 to 3.20. 2) Delete DEPENDS, since intltool is not needed. Signed-off-by: Wang Xin --- .../{adwaita-icon-theme_3.18.0.bb => adwaita-icon-theme_3.20.bb} | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) rename meta/recipes-gnome/gnome/{adwait

[OE-core] [PATCH v3] adwaita-icon-theme: 3.18.0 -> 3.20

1) Upgrade adwaita-icon-theme from 3.18.0 to 3.20. 2) Delete DEPENDS, since intltool is not needed. Signed-off-by: Wang Xin --- .../{adwaita-icon-theme_3.18.0.bb => adwaita-icon-theme_3.20.bb} | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) rename meta/recipes-gnome/gnome/{adwait

Re: [OE-core] [PATCH] gdk-pixbuf: 2.34.0 -> 2.35.3

There is no 2.36.x, so stick with 2.34.x. From: Khem Raj [mailto:raj.k...@gmail.com] Sent: Friday, August 19, 2016 1:58 AM To: Burton, Ross Cc: Wang, Xin/王 鑫; OE-core Subject: Re: [OE-core] [PATCH] gdk-pixbuf: 2.34.0 -> 2.35.3 On Aug 18, 2016, at 4:33 AM, Burton, Ross mailto:ross.bur...@intel.c

Re: [OE-core] [PATCH V3 8/8] runqemu: refactor it and remove machine knowledge

On Fri, Aug 19, 2016 at 4:55 PM, Robert Yang wrote: > Previously, runqemu had hard coded machine knowledge, which limited its > usage, for example, qemu can boot genericx86, but runqemu can't, we need > edit runqemu/runqemu-internal a lot if we want to boot genericx86. > > Now bsp conf files can s

[OE-core] [PATCH 3/3] kmod: upgrade to 23

Signed-off-by: Chen Qi --- meta/recipes-kernel/kmod/kmod.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/recipes-kernel/kmod/kmod.inc b/meta/recipes-kernel/kmod/kmod.inc index 0bcdcf6..99c4a8f 100644 --- a/meta/recipes-kernel/kmod/kmod.inc +++ b/meta/recipes-kern

[OE-core] [PATCH 1/3] util-linux: upgrade to 2.28.1

Signed-off-by: Chen Qi --- .../util-linux/{util-linux_2.28.bb => util-linux_2.28.1.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-core/util-linux/{util-linux_2.28.bb => util-linux_2.28.1.bb} (86%) diff --git a/meta/recipes-core/util-linux/util-linux

[OE-core] [PATCH 2/3] diffutils: upgrade to 3.4

Signed-off-by: Chen Qi --- .../0001-Unset-need_charset_alias-when-building-for-musl.patch| 0 .../diffutils/{diffutils-3.3 => diffutils-3.4}/run-ptest | 0 .../recipes-extended/diffutils/{diffutils_3.3.bb => diffutils_3.4.bb} | 4 ++-- 3 files changed, 2 insertions(+), 2 dele

Re: [OE-core] [PATCH v2] bind: 9.10.3-P3 -> 9.11.0b2

I checked the build directory, and didn’t find those files that you refer to. I guess my configuration may be different with yours. Can I see your log.do_configure file, thanks. From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Thursday, August 18, 2016 10:00 PM To: Wang, Xin/王 鑫 Cc: OE-cor

[OE-core] [PATCH 0/3] Package Upgrade -- 20160819

The following changes since commit 5dca6cc2fcdb2799c19b1697f0647a16ce296290: systemd-compat-units: Only enable for systemd in DISTRO_FEATURES (2016-08-18 16:52:02 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib ChenQi/PU-20160819 http

Re: [OE-core] [PATCH V3 8/8] runqemu: refactor it and remove machine knowledge

On 08/19/2016 03:52 PM, Nathan Rossi wrote: On Fri, Aug 19, 2016 at 4:55 PM, Robert Yang wrote: Previously, runqemu had hard coded machine knowledge, which limited its usage, for example, qemu can boot genericx86, but runqemu can't, we need edit runqemu/runqemu-internal a lot if we want to bo

Re: [OE-core] [PATCH V3 8/8] runqemu: refactor it and remove machine knowledge

On Fri, Aug 19, 2016 at 6:20 PM, Robert Yang wrote: > > > On 08/19/2016 03:52 PM, Nathan Rossi wrote: >> >> On Fri, Aug 19, 2016 at 4:55 PM, Robert Yang >> wrote: >>> >>> Previously, runqemu had hard coded machine knowledge, which limited its >>> usage, for example, qemu can boot genericx86, but

Re: [OE-core] [PATCH v2] bind: 9.10.3-P3 -> 9.11.0b2

On 19 August 2016 at 11:00, Wang, Xin wrote: > I checked the build directory, and didn’t find those files that you refer > to. I guess my configuration may be different with yours. Can I see your > log.do_configure file, thanks. > > You should not need that. configure.in clearly enables/disables

[OE-core] [PATCH] bootchart2: Add ALTERNATIVE configuration for bootchartd

From: Ming Liu Since busybox also provides the bootchartd command use the update-alternatives mechanism to address this. Also let bootchartd-stop-initscript RDEPENDS on bootchart2, since /sbin/bootchartd is being called in that script. Ming Liu --- meta/recipes-devtools/bootchart2/bootchart2_

Re: [OE-core] [PATCH V3 8/8] runqemu: refactor it and remove machine knowledge

On 08/19/2016 04:52 PM, Nathan Rossi wrote: On Fri, Aug 19, 2016 at 6:20 PM, Robert Yang wrote: On 08/19/2016 03:52 PM, Nathan Rossi wrote: On Fri, Aug 19, 2016 at 4:55 PM, Robert Yang wrote: Previously, runqemu had hard coded machine knowledge, which limited its usage, for example, qe

[OE-core] Build of u-boot with gold is broken

Hi, It looks like the recent change to meta/recipes-bsp/u-boot/u-boot.inc to enable out of tree builds for u-boot does not work with gold. The sed at line 70 fails as it is being executed in an empty build directory and so there is no config.mk. Andrew -- __

Re: [OE-core] [RFT] gcc 6.2 RC1 update

On Tue, 2016-08-16 at 11:55 -0700, Khem Raj wrote: > Hi All > > I have put together recipe upgrade for upcoming gcc 6.2 release now > that it entered RC phase. With gcc 6.2 the recipes are using tarballs > instead of git fetcher as promised :) > Please help testing it out in your setups and report

Re: [OE-core] [PATCH] libnl: musl fixes

ping? A. On Do, 2016-08-11 at 15:06 +0100, André Draszik wrote: > The libnl+musl combination has two issues at the moment: > a) a public header file #include's an incorrect file >    (sys/poll.h instead of poll.h), which causes warnings and >    potentially errors (-Werror) in a musl based syste

[OE-core] [PATCH] libffi: fix a typo (mips)

While code elsewhere checks for MIPS_INSTRUCTION_SET == mips16e in order to decide how to compile, hence the typo doesn't affect behaviour, the intention was to set it to 'mips', as is done everywhere else. Fixing the typo also helps to avoid confusion. Signed-off-by: André Draszik --- meta/reci

[OE-core] [PATCH] openssl: fix add missing dependencies building for test directory

Regarding the last commit about missing dependencies, another issue was found. The problem was found, while ptest has been built with some set extra settings. It means, when ptest is going to be built, it is necessary to rebuild dependencies for test directory too. Signed-off-by: Andrej Valek Sig

[OE-core] [PATCH] asciidoc-native: add dependency on docbook-xml-dtd4-native

During the compilation phase asciidoc runs a2x for validation of some xmls which in turn invokes xmllint with --nonet parameter that requires DTDs to be available locally in order to succeed otherwise the do_compile fails. We now add a direct dependency on docbook-xml-dtd4 so the DTDs are always av

Re: [OE-core] [PATCH] gdk-pixbuf: 2.34.0 -> 2.35.3

On 08/18/2016 09:11 PM, Burton, Ross wrote: On 18 August 2016 at 18:58, Khem Raj mailto:raj.k...@gmail.com>> wrote: perhaps recipe updater script should account for such presets ? It does: http://recipes.yoctoproject.org/rrs/recipedetail/451/ says up-to-date as we have 2.34.0 despite the

Re: [OE-core] [PATCH 2/3] local.conf.sample: Disable ARM and PPC due to prelink test case failures

Just an FYI - I've investigated the ARM and PPC failures further. It looks like it may be a binutils problem. Both of the failed tests link applications using the arguments "-Wl,-z,nocopyreloc" Once this has been done, the executable will not run. (Aborts very early.) I'm currently verifying

[OE-core] [krogoth][master][PATCH] image-vm.bbclass: remove old images if RM_OLD_IMAGE is enabled

[YOCTO #10164] Signed-off-by: Jonathan Liu --- meta/classes/image-vm.bbclass | 13 +++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/meta/classes/image-vm.bbclass b/meta/classes/image-vm.bbclass index 72f7b4b..bf57e2c 100644 --- a/meta/classes/image-vm.bbclass +++ b/me

[OE-core] [PATCH 0/2] Fixes to oe-build-perf-test

Two patches to fix issues introduced in the previous conversion to Python unittest framework. The following changes since commit 5dca6cc2fcdb2799c19b1697f0647a16ce296290: systemd-compat-units: Only enable for systemd in DISTRO_FEATURES (2016-08-18 16:52:02 +0100) are available in the git repo

[OE-core] [PATCH 1/2] oe-build-perf-test: align log message format with testrunner output

The previous attempt on this was a bit erroneous, dropping time stamps completely although only the timestamp format should've been changed. Signed-off-by: Markus Lehtonen --- scripts/oe-build-perf-test | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/scripts/oe-build-pe

[OE-core] [PATCH 2/2] oeqa.buildperf: fix crash when creating globalres.log

Fix a bug that was introduced when converting to unittest framework. Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/buildperf/base.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/lib/oeqa/buildperf/base.py b/meta/lib/oeqa/buildperf/base.py index c1dc86e..30b8e47 100

Re: [OE-core] [RFT] gcc 6.2 RC1 update

> On Aug 19, 2016, at 3:14 AM, Richard Purdie > wrote: > > On Tue, 2016-08-16 at 11:55 -0700, Khem Raj wrote: >> Hi All >> >> I have put together recipe upgrade for upcoming gcc 6.2 release now >> that it entered RC phase. With gcc 6.2 the recipes are using tarballs >> instead of git fetcher a

Re: [OE-core] [RFT] gcc 6.2 RC1 update

On 2016-08-19 16:04, Gary Thomas wrote: On 2016-08-19 15:40, Khem Raj wrote: On Aug 19, 2016, at 3:14 AM, Richard Purdie wrote: On Tue, 2016-08-16 at 11:55 -0700, Khem Raj wrote: Hi All I have put together recipe upgrade for upcoming gcc 6.2 release now that it entered RC phase. With gcc

Re: [OE-core] [RFT] gcc 6.2 RC1 update

On 2016-08-19 15:40, Khem Raj wrote: On Aug 19, 2016, at 3:14 AM, Richard Purdie wrote: On Tue, 2016-08-16 at 11:55 -0700, Khem Raj wrote: Hi All I have put together recipe upgrade for upcoming gcc 6.2 release now that it entered RC phase. With gcc 6.2 the recipes are using tarballs instea

[OE-core] Why are verbose makefiles enabled by default in cmake bbclass ?

Hello, in a project, I'd like to disable verbose makefiles (the bbclass sets CMAKE_VERBOSE_MAKEFILE to 1), since the log output becomes very large, and finding compiler errors becomes more difficult. I think there is no problem in overriding the default in my recipe. However, I wonder if ther

[OE-core] [PATCH] image_types: use COMPRESSIONTYPES variable for backward compatibility

Recent renaming of COMPRESSIONTYPES variable can break recipes that still use it. Including value of COMPRESSIONTYPES variable into CONVERSIONTYPES should prevent this. Signed-off-by: Ed Bartosh --- meta/classes/image_types.bbclass | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) di

Re: [OE-core] Why are verbose makefiles enabled by default in cmake bbclass ?

On Fri, 2016-08-19 at 16:10 +0200, Carlos Rafael Giani wrote: > Hello, > > in a project, I'd like to disable verbose makefiles (the bbclass sets > CMAKE_VERBOSE_MAKEFILE to 1), since the log output becomes very > large, > and finding compiler errors becomes more difficult. I think there is > no

Re: [OE-core] [PATCH] image_types: use COMPRESSIONTYPES variable for backward compatibility

On Fri, 2016-08-19 at 17:35 +0300, Ed Bartosh wrote: > Recent renaming of COMPRESSIONTYPES variable can break recipes that > still use it. Including value of COMPRESSIONTYPES variable into > CONVERSIONTYPES should prevent this. > > Signed-off-by: Ed Bartosh > --- > meta/classes/image_types.bbcla

[OE-core] [PATCH] syslinux.bbclass: ensure creation of output directory

build_syslinux_cfg function creates syslinux configuration file. The code assumes that the output directory exists, which is not always the case. For example rm_work task removes rootfs directory structure and causes build_syslinux_cfg to fail with this error: Unable to open ../-/syslinux_vm.cfg M

Re: [OE-core] [PATCH 2/6] linux-yocto/4.1: bump to v4.1.29

On 2016-08-18 11:20 AM, Richard Purdie wrote: On Thu, 2016-08-18 at 11:16 -0400, Bruce Ashfield wrote: On 2016-08-18 11:15 AM, Richard Purdie wrote: On Mon, 2016-08-15 at 14:26 -0400, Bruce Ashfield wrote: Integrating the korg 4.1.29 -stable release Signed-off-by: Bruce Ashfield --- meta/re

Re: [OE-core] [RFT] gcc 6.2 RC1 update

This is a long standing assembler error. Which I never get to bottom of. Rwboorinf the build machine helps On Aug 19, 2016 7:06 AM, "Gary Thomas" wrote: > On 2016-08-19 16:04, Gary Thomas wrote: > >> On 2016-08-19 15:40, Khem Raj wrote: >> >>> >>> On Aug 19, 2016, at 3:14 AM, Richard Purdie < >>

Re: [OE-core] [RFT] gcc 6.2 RC1 update

On 2016-08-19 16:59, Khem Raj wrote: This is a long standing assembler error. Which I never get to bottom of. Rwboorinf the build machine helps ^ What does this mean? As I mentioned, it worked fine before you

[OE-core] [PATCH] sanity.bbclass: Ensure we expand BUILD_PREFIX

This likely used to work when we expanded python functions and broke when we stopped. Since it defaults to "", it never caused an issue but is incorrect usage so fix it. Signed-off-by: Richard Purdie diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass index 98345ce..202b5db 10

[OE-core] [PATCH] busybox: Add parallel make fix

We're seeing regular parallel make failures in applet headers in busybox. This adds a patch to try and avoid the issue, building upon a fix already backported from upstream. The patch has been sent to upstream. [YOCTO #10116] Signed-off-by: Richard Purdie diff --git a/meta/recipes-core/busybox/

[OE-core] [PATCH] parselogs: Ignore uvesafb timeouts

We're periodically seeing uvesafb timeouts on the autobuilder. Whitelist these errors as there is little it seems we can do about them and we therefore choose to ignore them rather than fail the builds. [YOCTO #8245] There is a better solution proposed in the bug with a -1 timeout however this av

[OE-core] [PATCH 2/5] security_flags: pass ssp-buffer-size param to stack protector

This tells the compiler to use a canary to protect any function which declares a character array of 4 or more bytes on its stack, rather than the default of 8 or more bytes. Signed-off-by: Joshua Lock --- meta/conf/distro/include/security_flags.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 de

[OE-core] [PATCH 0/5] security_flags: additions in line with common practice

This series tidies up the security_flags include to: * remove an invalid option * update the flags to be more in-line with the common options in use on major distros such as Ubuntu and Fedora This series has been tested on qemuarm, qemuarm64 and qemux86-64 building core-image-minimal, core-image

[OE-core] [PATCH 4/5] security_flags: update comment header

Embelish a little on the utility of the extra compiler and linker flags enabled by this include. Signed-off-by: Joshua Lock --- meta/conf/distro/include/security_flags.inc | 9 ++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/meta/conf/distro/include/security_flags.inc b/

[OE-core] [PATCH 5/5] security_flags: ensure changes to SHARED_OBJECTS cause recompile

Add the SHARED_OBJECTS variable to SECURITY_LDFLAGS vardeps so that changing SHARED_OBJECTS causes do_compile to re-run. Signed-off-by: Joshua Lock --- meta/conf/distro/include/security_flags.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/conf/distro/include/security_flags.inc b/m

[OE-core] [PATCH 1/5] security_flags: remove invalid linker option

-fstack-protector-* is a compiler option, not a linker option. [YOCTO #9948] Signed-off-by: Joshua Lock --- meta/conf/distro/include/security_flags.inc | 9 ++--- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/meta/conf/distro/include/security_flags.inc b/meta/conf/distro/in

[OE-core] [PATCH 3/5] security_flags: link position independent executables

Link non-shared objects with the -pie option to enable the kernel to make use of Address Space Layout Randomisation (ASLR) and harden against Return Oriented Programming (ROP) attacks. As this linker option isn't compatible with the -fPIC option used to build shared libraries any recipe which pro

Re: [OE-core] [PATCH] Fix S4U2Self KDC crash when anon is restricted

On Wed, 2016-08-17 at 13:26 +0300, Alexandru Moise wrote: > This is CVE-2016-3120 > > The validate_as_request function in kdc_util.c in the Key > Distribution > Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.13.6 and 1.4.x > before > 1.14.3, when restrict_anonymous_to_tgt is enabled, uses an i

Re: [OE-core] [RFT] gcc 6.2 RC1 update

> On Aug 19, 2016, at 8:05 AM, Gary Thomas wrote: > > On 2016-08-19 16:59, Khem Raj wrote: >> This is a long standing assembler error. Which I never get to bottom of. >> Rwboorinf the build machine helps > > ^ >

Re: [OE-core] [PATCH 5/5] security_flags: ensure changes to SHARED_OBJECTS cause recompile

On Fri, 2016-08-19 at 16:34 +0100, Joshua Lock wrote: > Add the SHARED_OBJECTS variable to SECURITY_LDFLAGS vardeps so that > changing SHARED_OBJECTS causes do_compile to re-run. > > Signed-off-by: Joshua Lock > --- > meta/conf/distro/include/security_flags.inc | 1 + > 1 file changed, 1 inserti

Re: [OE-core] [PATCH] libnl: musl fixes

OK this can be merged. > On Aug 19, 2016, at 3:31 AM, André Draszik wrote: > > ping? > > A. > > > On Do, 2016-08-11 at 15:06 +0100, André Draszik wrote: >> The libnl+musl combination has two issues at the moment: >> a) a public header file #include's an incorrect file >>(sys/poll.h instea

Re: [OE-core] [PATCH] gdk-pixbuf: 2.34.0 -> 2.35.3

> On Aug 19, 2016, at 5:41 AM, Alexander Kanavin > wrote: > > On 08/18/2016 09:11 PM, Burton, Ross wrote: >> >> On 18 August 2016 at 18:58, Khem Raj > > wrote: >> >>perhaps recipe updater script should account for such presets ? >> >> >> It does: http://recip

Re: [OE-core] [PATCH] asciidoc-native: add dependency on docbook-xml-dtd4-native

> On Aug 19, 2016, at 4:08 AM, Awais Belal wrote: > > During the compilation phase asciidoc runs a2x for validation > of some xmls which in turn invokes xmllint with --nonet > parameter that requires DTDs to be available locally in order > to succeed otherwise the do_compile fails. > We now add

Re: [OE-core] [PATCH 1/5] security_flags: remove invalid linker option

> On Aug 19, 2016, at 8:34 AM, Joshua Lock wrote: > > -fstack-protector-* is a compiler option, not a linker option. IIRC There are packages who do not use CFLAGS in linker cmdline which case this fails what issues do you see with this option appearing in ldflags ? This should be tested with

Re: [OE-core] [PATCH 2/5] security_flags: pass ssp-buffer-size param to stack protector

> On Aug 19, 2016, at 8:34 AM, Joshua Lock wrote: > > This tells the compiler to use a canary to protect any function which > declares a character array of 4 or more bytes on its stack, rather > than the default of 8 or more bytes. Thats fine, however, it slows down the code, strong option was

Re: [OE-core] [PATCH 5/5] security_flags: ensure changes to SHARED_OBJECTS cause recompile

> On Aug 19, 2016, at 9:02 AM, Richard Purdie > wrote: > > On Fri, 2016-08-19 at 16:34 +0100, Joshua Lock wrote: >> Add the SHARED_OBJECTS variable to SECURITY_LDFLAGS vardeps so that >> changing SHARED_OBJECTS causes do_compile to re-run. >> >> Signed-off-by: Joshua Lock >> --- >> meta/conf/

Re: [OE-core] [PATCH 5/5] security_flags: ensure changes to SHARED_OBJECTS cause recompile

On Fri, 2016-08-19 at 17:02 +0100, Richard Purdie wrote: > On Fri, 2016-08-19 at 16:34 +0100, Joshua Lock wrote: > > > > Add the SHARED_OBJECTS variable to SECURITY_LDFLAGS vardeps so that > > changing SHARED_OBJECTS causes do_compile to re-run. > > > > Signed-off-by: Joshua Lock > > --- > >  me

Re: [OE-core] [PATCH 5/5] security_flags: ensure changes to SHARED_OBJECTS cause recompile

On Fri, 2016-08-19 at 10:11 -0700, Khem Raj wrote: > > > > On Aug 19, 2016, at 9:02 AM, Richard Purdie > undation.org> wrote: > > > > On Fri, 2016-08-19 at 16:34 +0100, Joshua Lock wrote: > > > > > > Add the SHARED_OBJECTS variable to SECURITY_LDFLAGS vardeps so > > > that > > > changing SHARED

Re: [OE-core] [PATCH 1/5] security_flags: remove invalid linker option

On Fri, 2016-08-19 at 10:05 -0700, Khem Raj wrote: > > > > On Aug 19, 2016, at 8:34 AM, Joshua Lock > > wrote: > > > > -fstack-protector-* is a compiler option, not a linker option. > > IIRC There are packages > who do not use CFLAGS in linker cmdline which case this fails > > what issues do y

Re: [OE-core] [PATCH] image_types: use COMPRESSIONTYPES variable for backward compatibility

Hi, On Fri, Aug 19, 2016 at 5:45 PM, Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > On Fri, 2016-08-19 at 17:35 +0300, Ed Bartosh wrote: > > Recent renaming of COMPRESSIONTYPES variable can break recipes that > > still use it. Including value of COMPRESSIONTYPES variable into > > C

Re: [OE-core] [PATCH 2/5] security_flags: pass ssp-buffer-size param to stack protector

On Fri, 2016-08-19 at 10:07 -0700, Khem Raj wrote: > > > > On Aug 19, 2016, at 8:34 AM, Joshua Lock > > wrote: > > > > This tells the compiler to use a canary to protect any function > > which > > declares a character array of 4 or more bytes on its stack, rather > > than the default of 8 or mor

Re: [OE-core] [OE-Core][PATCH 2/2] python3-native: Extend python3-native rproviders

ping? On Tue, Aug 16, 2016 at 3:47 PM, Fabio Berton wrote: > Add the following modules to RPROVIDES: > > - python3-email-native > - python3-io-native > - python3-json-native > - python3-lang-native > - python3-misc-native > - python3-netclient-native > - python3-netserver-native >

Re: [OE-core] [OE-Core][PATCH 1/2] python3-native: Change code style for rprovides

ping? On Tue, Aug 16, 2016 at 3:47 PM, Fabio Berton wrote: > Use a more readable code style for RPROVIDES and sort recipes > alphabetically. > > Signed-off-by: Fabio Berton > Signed-off-by: Otavio Salvador > --- > meta/recipes-devtools/python/python3-native_3.5.2.bb | 9 - > 1 file ch

Re: [OE-core] [PATCH] parselogs: Ignore uvesafb timeouts

> On Aug 19, 2016, at 8:29 AM, Richard Purdie > wrote: > > We're periodically seeing uvesafb timeouts on the autobuilder. Whitelist these > errors as there is little it seems we can do about them and we therefore > choose to ignore them rather than fail the builds. > > [YOCTO #8245] > > There

Re: [OE-core] how can i add u-boot-fw-utils to my build without u-boot being part of the build?

On Thu, Aug 18, 2016 at 12:41:25PM -0400, Robert P. J. Day wrote: > not sure if i asked this once, but i'm still trying to figure it > out. > > i want to add the u-boot-fw-utils recipe to my current build, but > u-boot is *not* part of the relevant BSP layer -- u-boot is being > configured an

Re: [OE-core] [PATCH] kexec-tools: 2.0.12 -> 2.0.13

On Thu, 2016-08-18 at 10:08 +0800, Dai Caiyun wrote: > Upgrade kexec-tools from 2.0.12 to 2.0.13. Sadly this doesn't build on arm: https://autobuilder.yoctoproject.org/main/builders/nightly-arm/builds/924/steps/BuildImages/logs/stdio https://autobuilder.yoctoproject.org/main/builders/nightly-arm

Re: [OE-core] [PATCH 2/2] oeqa/selftest Adds eSDK test cases to devtool verification.

On Wed, 2016-08-17 at 17:31 -0500, Francisco Pedraza wrote: > The covered functions are, install libraries headers, image > generation binary feeds and > sdk update devtool. > > Signed-off-by: Francisco Pedraza < > francisco.j.pedraza.gonza...@intel.com> > --- > meta/lib/oeqa/selftest/eSDK.py | 1

Re: [OE-core] [PATCH 2/2] oeqa/selftest Adds eSDK test cases to devtool verification.

On Fri, 2016-08-19 at 23:13 +0100, Richard Purdie wrote: > On Wed, 2016-08-17 at 17:31 -0500, Francisco Pedraza wrote: > > The covered functions are, install libraries headers, image > > generation binary feeds and > > sdk update devtool. > > > > Signed-off-by: Francisco Pedraza < > > francisco.j.

[OE-core] [PATCH 0/1] Fix corrupted path in startup.nsh for iso image

Hi, startup.nsh for iso image has corrupted text because of echo command. This patch switches to printf similar to the one submitted by Christopher Larson for non-iso image. Regards, Pranav Pranav Tipnis (1): grub-efi.bbclass: Fix path in startup.nsh for iso image. meta/classes/grub-efi.bbcl

[OE-core] [PATCH 1/1] grub-efi.bbclass: Fix path in startup.nsh for iso image.

The path in startup.nsh for iso image is corrupted as follows: fs0:\EFI\BOOT^Hootx64.efi Using printf will emit correct path which is: fs0:\EFI\BOOT\bootx64.efi This happens because of echo command. Switching to printf like the one used in efi_populate() function. Signed-off-by: Pranav Tipnis -

[OE-core] [PATCH 2/2] Revert "local.conf.sample: Disable ARM and PPC due to prelink test case failures"

This reverts commit d3e5c1d17f80b3dd7a6d85e07b5c0c516f09ae93. The problem is not in prelink, but in binutils. Any programs compiled with the option will be broken and prelink will not make it worse. See Yocto Project bug 10168 for more information. Signed-off-by: Mark Hatle --- meta/conf/loca

[OE-core] [PATCH 1/2] glibc: Fix scope resolution in glibc to be breadth first.

The ELF specification indicates symbol resolution should be breadth first, not depth first. The dl-deps.c: dl_build_locale_scope function is processing in a depth first mode. This is causes certain symbols to be incorrectly reported when LD_TRACE_PRELINKING=1 is enabled. See glibc BZ #20488 for

[OE-core] [PATCH 0/2] prelink changes

Re-enable prelink on ARM and PPC. The detected failures are not related to anything inside of prelink, the binaries failed to execute before prelinking. The other patch fixes the IFUNC resolution problem inside of glibc itself. The scope was being resolved depth first, not breadth first as indica

Re: [OE-core] [PATCH 1/2] glibc: Fix scope resolution in glibc to be breadth first.

On 8/19/16 8:44 PM, Mark Hatle wrote: > The ELF specification indicates symbol resolution should be breadth first, not > depth first. > > The dl-deps.c: dl_build_locale_scope function is processing in a depth first > mode. This is causes certain symbols to be incorrectly reported when > LD_TRACE_

[OE-core] [PATCH 2/2] linux-yocto/4.4: fix configuration warnings

Integrating the following commits to address configuration warnings for intel-corei7-64 and intel-core2-32: features: Fix dependencies and =m vs =y discrepancies for corei7 intel-core2-32.cfg: Explicitly disable CONFIG_64BIT Signed-off-by: California Sullivan Signed-off-by: Bruce Ashfield -

[OE-core] [PATCH 1/2] linux-yocto/4.1/4.4: -stable updates and configuration changes

Updating the 4.4 kernel to v4.4.18 and the 4.1 kernel to v4.1.30. We also tweak the configuration with the following commits to remove warnings being generated from the 4.4 kernel (due to options being dropped from the final .config): features: Create mfd-intel-lpss feature and use where approp

[OE-core] [PATCH 0/2] linux-yocto/4.1/4.4: -stable and configuration updates

Hi all, Here are the next set of -stable updates for the linux-yocto kernels. These contain some CVE fixes that folks have been asking about, so I've queued and sent them right away. I built and ran qemuppc against 4.1.30 and wasn't able to see any instability, but will continue to run stress tes