[OE-core] [PATCH] libgcc: remove duplicate configure options

The original fix [1] was made redundant by the followup [2]. [1] http://git.openembedded.org/openembedded-core/commit/?id=d774bb2d10f2c05900f87dcc53f073433ca02121 [2] http://git.openembedded.org/openembedded-core/commit/?id=d7799a17d5e802db3f8d16bdc824aae81538e675 Signed-off-by: Andre

Re: [OE-core] [PATCHv2 0/2] Support template files for wic

On Fri, Jul 1, 2016 at 2:27 PM, Christopher Larson wrote: > From: Christopher Larson > > This adds support for .wks.in files as WKS_FILE. > > This is a re-send of the RFC PATCH series as a regular PATCH series, to > attempt to get the feature merged.

Re: [OE-core] [PATCHv2] gcc-cross: remove --with-linker-hash-style

On Fri, Jul 1, 2016 at 2:19 PM, Khem Raj wrote: > On Fri, Jul 1, 2016 at 1:44 PM, Christopher Larson > wrote: > > From: Christopher Larson > > > > We explicitly set the hash style to gnu in our LDFLAGS. Setting the > default to >

[OE-core] [PATCHv2 1/2] image_types.bbclass: add intermediate var for WKS_FILE_CHECKSUM

From: Christopher Larson This is a bit nicer to work with, and easier to override. Signed-off-by: Christopher Larson --- meta/classes/image_types.bbclass | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[OE-core] [PATCHv2 2/2] image_types.bbclass: support template .wks.in files for wic

From: Christopher Larson These files are treated as the contents of a bitbake variable, so usual bitbake variable references are supported. I considered using another templating mechanism, for example the one used by yocto-layer, but then we'd end up largely mapping

Re: [OE-core] [PATCHv2] gcc-cross: remove --with-linker-hash-style

On Fri, Jul 1, 2016 at 1:44 PM, Christopher Larson wrote: > From: Christopher Larson > > We explicitly set the hash style to gnu in our LDFLAGS. Setting the default to > this in the toolchain, while convenient, actually hides bugs, as a failure to >

[OE-core] [PATCHv2 0/2] Support template files for wic

From: Christopher Larson This adds support for .wks.in files as WKS_FILE. This is a re-send of the RFC PATCH series as a regular PATCH series, to attempt to get the feature merged. There's a clear value-add, there were no major objections to the RFC series, and further

[OE-core] [PATCH] service: obey CFLAGS, LDFLAGS

From: Christopher Larson Signed-off-by: Christopher Larson --- meta-skeleton/recipes-skeleton/service/service_0.1.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-skeleton/recipes-skeleton/service/service_0.1.bb

Re: [OE-core] [PATCHv2] gcc-cross: remove --with-linker-hash-style

On Fri, Jul 1, 2016 at 1:44 PM, Christopher Larson wrote: > From: Christopher Larson > > We explicitly set the hash style to gnu in our LDFLAGS. Setting the > default to > this in the toolchain, while convenient, actually hides bugs, as a failure > to

[OE-core] [PATCHv2] gcc-cross: remove --with-linker-hash-style

From: Christopher Larson We explicitly set the hash style to gnu in our LDFLAGS. Setting the default to this in the toolchain, while convenient, actually hides bugs, as a failure to obey LDFLAGS isn't noticed. By removing this, it's not dissimilar to how we poison the

Re: [OE-core] [PATCHv2] buildstats-summary: round the floating point percentage

On Fri, Jul 1, 2016 at 1:39 PM, Christopher Larson wrote: > From: Christopher Larson > > This was rounded in python 2, but python 3 changed the default behavior of > /. > We could switch to the same behavior as previous by switching to // rather >

[OE-core] [PATCHv2] buildstats-summary: round the floating point percentage

From: Christopher Larson This was rounded in python 2, but python 3 changed the default behavior of /. We could switch to the same behavior as previous by switching to // rather than /, but there's value in keeping at least one decimal point, to avoid the misleading case

[OE-core] [PATCHv2] buildstats-summary: round the floating point percentage

From: Christopher Larson This was rounded in python 2, but python 3 changed the default behavior of /. We could switch to the same behavior as previous by switching to // rather than /, but there's value in keeping at least one decimal point, to avoid the misleading case

[OE-core] [PATCH 1/2] pseudo: drop recipe for old 1.6.7 version

Signed-off-by: Joshua Lock --- meta/recipes-devtools/pseudo/pseudo_1.6.7.bb | 19 --- 1 file changed, 19 deletions(-) delete mode 100644 meta/recipes-devtools/pseudo/pseudo_1.6.7.bb diff --git a/meta/recipes-devtools/pseudo/pseudo_1.6.7.bb

[OE-core] [PATCH 2/2] pseudo: upgrade to 1.8.0

* drop patches where the changes exist upstream * fetch from git as no tarball is available for 1.8.0 Signed-off-by: Joshua Lock --- .../pseudo/files/handle-remove-xattr.patch | 36 - .../pseudo/pseudo/obey-ldflags.patch | 50 -

[OE-core] [PATCH] glibc: Upgrade to latest tip of master

Stepping towards 2.24 release Signed-off-by: Khem Raj --- meta/recipes-core/glibc/cross-localedef-native_2.24.bb | 2 +- meta/recipes-core/glibc/glibc_2.24.bb | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [OE-core] [PATCH 1/2] meta-ostro-fixes: initramfs-framework: add retry loop for slow boot devices (like USB)

On Fri, Jul 1, 2016 at 10:53 AM, Patrick Ohly wrote: > On some hardware platforms (Gigabyte, qemu), detection of USB devices > by the kernel is slow enough such that it happens only after the first > attempt to mount the rootfs. We need to keep trying for a while >

[OE-core] [PATCH] lib/oe/path: remove oe.path.check_output

This was a copy-and-paste of subprocess.check_output() from when we supported Python <2.7, so simply delete it and use subprocess.check_output() instead. Signed-off-by: Ross Burton --- meta/lib/oe/path.py | 49 - 1 file

Re: [OE-core] [PATCH 3/6] default-distrovars.inc: remove directfb from GTK2DISTROFEATURES

On 1 July 2016 at 12:13, Maxin B. John wrote: > -GTK2DISTROFEATURES = "directfb x11" > +GTK2DISTROFEATURES = "x11" > I think we should keep this, for people who want to use their own directfb recipe. Ross -- ___

[OE-core] [PATCH] scripts: Fixed typo in parameter that was causing exception

There is a typo in the logging parameters, "filname" is being used instead of "filename" for yocto-kernel, yocto-layer and wic scripts. This didn't cause issues before since python 2 didn't validate unused parameters but with python >= 3.4.3 an exception is thrown. This patch fixes this

Re: [OE-core] Building Perl-5.22.1-r0 on Arch Linux fails with QA Issue

keep in mind that using gcc6 based build hosts may not work for OE older than master On Fri, Jul 1, 2016 at 1:16 AM, Daniel Kriesten wrote: > Hi Ross, > > I found the time to do the x86qemu build with jethro, which gives the QA > Issue. > > -- >8 -- >

Re: [OE-core] [oe] Patchwork upgrade tonight

On Fri, Jul 1, 2016 at 12:37 AM, Michael Halstead wrote: > The new patchwork is in place at https://patchwork.openembedded.org/. > The performance changes appear to be working well. Please e-mail if you > notice any problems. Thanks for doing this. I think i would

Re: [OE-core] [PATCH 1/2] gcc: remove unused patch

oops, seems my .gitignore has become too greedy. Thanks for fixing it. On Fri, Jul 1, 2016 at 5:28 AM, Ross Burton wrote: > Signed-off-by: Ross Burton > --- > ...-Symlink-c-header-in-target_triplet-for-S.patch | 49 > -- > 1

Re: [OE-core] [oe] Patchwork upgrade tonight

Perhaps it is worth mentioning that the new instance has a REST API, so you can send requests directly or use the more friendly tool git-pw. http://patchwork-freedesktop.readthedocs.io/en/latest/manual.html#git-pw With it, so can easily fetch, merge, etc. patch series coming from patchwork.

[OE-core] [PATCH 2/2] meta-ostro-fixes: initramfs-framework: Add support for PartUUIDs

From: Igor Stoppa The rootfs can be addressed also by referring to the PartUUID value from the GPT. This patch enables such type of reference. Signed-off-by: Igor Stoppa Signed-off-by: Patrick Ohly ---

[OE-core] [PATCH 1/2] meta-ostro-fixes: initramfs-framework: add retry loop for slow boot devices (like USB)

On some hardware platforms (Gigabyte, qemu), detection of USB devices by the kernel is slow enough such that it happens only after the first attempt to mount the rootfs. We need to keep trying for a while (default: 5s seconds, controlled by roottimeout=) and sleep between each attempt (default:

[OE-core] [PATCH 0/2] initramfs-framework enhancements

These are two enhancements that we've used for a while now in Ostro OS: - a retry loop that we found necessary for some slow USB hardware - finding the root partition by partition UUID (only filesystem UUID supported before) The following changes since commit

[OE-core] [PATCH 1/2] gcc: remove unused patch

Signed-off-by: Ross Burton --- ...-Symlink-c-header-in-target_triplet-for-S.patch | 49 -- 1 file changed, 49 deletions(-) delete mode 100644 meta/recipes-devtools/gcc/0001-gcc-runtime-Symlink-c-header-in-target_triplet-for-S.patch diff --git

[OE-core] [PATCH 5/6] buildoptions.py: remove directfb image build test

removing this test since we move directfb out of oe-core Signed-off-by: Maxin B. John --- meta/lib/oeqa/selftest/buildoptions.py | 13 - 1 file changed, 13 deletions(-) diff --git a/meta/lib/oeqa/selftest/buildoptions.py

[OE-core] [PATCH 1/6] remove packagegroup-core-directfb.bb

remove packagegroup-core-directfb.bb as part of moving directfb from oe-core Signed-off-by: Maxin B. John --- .../packagegroups/packagegroup-core-directfb.bb | 15 --- 1 file changed, 15 deletions(-) delete mode 100644

[OE-core] [PATCH 2/6] remove core-image-directfb.bb

remove core-image-directfb.bb as part of moving directfb from oe-core Signed-off-by: Maxin B. John --- meta/recipes-graphics/images/core-image-directfb.bb | 13 - 1 file changed, 13 deletions(-) delete mode 100644

[OE-core] [PATCH 4/6] distro_alias.inc: remove directfb related references

remove directfb related references from distro_alias.inc as part of moving directfb from oe-core Signed-off-by: Maxin B. John --- meta/conf/distro/include/distro_alias.inc | 3 --- 1 file changed, 3 deletions(-) diff --git a/meta/conf/distro/include/distro_alias.inc

[OE-core] [PATCH 6/6] move directfb from oe-core

Remove the directfb recipe as we are moving directfb out of oe-core [YOCTO #8489] Signed-off-by: Maxin B. John --- .../configure.in-Fix-string-argument-syntax.patch | 28 - .../directfb/directfb-examples_1.7.0.bb| 21

[OE-core] [PATCH 3/6] default-distrovars.inc: remove directfb from GTK2DISTROFEATURES

remove directfb from GTK2DISTROFEATURES as part of moving directfb from oe-core Signed-off-by: Maxin B. John --- meta/conf/distro/include/default-distrovars.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OE-core] [PATCH 0/6] move directfb from oe-core

directfb.org has been down for about a year now. Our attempts to locate a trustworthy source from Github has failed to provide a definite answer. https://github.com/deniskropp/DirectFB/issues/2#issuecomment-226316231 Remove directfb recipe from oe-core and submit it to meta-oe. [YOCTO #8489]

[OE-core] [PATCH] rt-tests: move ptest to python3

convert python2 based ptest of rt-tests package to python3 Signed-off-by: Maxin B. John --- meta/recipes-rt/rt-tests/files/rt_bmark.py | 26 +- meta/recipes-rt/rt-tests/files/run-ptest | 2 +- meta/recipes-rt/rt-tests/rt-tests_2.0.bb | 2 +- 3

Re: [OE-core] Building Perl-5.22.1-r0 on Arch Linux fails with QA Issue

Hi Ross, I found the time to do the x86qemu build with jethro, which gives the QA Issue. -- >8 -- jethro u= $ bitbake core-image-base WARNING: Host distribution "Arch-rolling" has not been validated with this version of the build system; you may possibly experience unexpected

[OE-core] [krogoth][wic][PATCH] wic: rawcopy: make source filenames unique

Rawcopy plugin copies source files to build folder before using them to assemble result image. After assembling the image wic renames source files to .p. If the same source file is used in multiple partitions wic breaks trying to rename file that doesn't exist. Added suffix to the files when

Re: [OE-core] [oe] Patchwork upgrade tonight

The new patchwork is in place at https://patchwork.openembedded.org/. The performance changes appear to be working well. Please e-mail if you notice any problems. On 06/30/2016 04:11 PM, Khem Raj wrote: > On Thu, Jun 30, 2016 at 4:03 PM, Michael Halstead > wrote: