[OE-core] [PATCH V2 1/1] systemd: split systemd-container

Split container/vm related units into a new package, systemd-container. The split mainly references Fedora 24, with a few differences. Apart from the bash and zsh completion files, the differences include adding systemd-spawn@.service into the systemd-container package. [YOCTO #9835]

[OE-core] [PATCH V2 0/1] systemd: split systemd-container

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/systemd-container

Re: [OE-core] [PATCH 1/1] systemd: split systemd-container

On 08/02/2016 10:55 PM, Joshua G Lock wrote: On Thu, 2016-07-14 at 11:25 +0800, Chen Qi wrote: Split container/vm related units into a new package, systemd- container. The split mainly references Fedora 24, with a few differences. Apart from the bash and zsh completion files, the differences

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

On 08/19/2016 09:45 AM, Mark Hatle wrote: On 8/18/16 8:06 PM, Robert Yang wrote: On 08/19/2016 05:47 AM, Mark Hatle wrote: General comment on the patch set. I do like what this change is trying to accomplish. However, I think putting QEMU knowledge into the 'arch' is a bad idea -- unless

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

On 8/18/16 8:06 PM, Robert Yang wrote: > > > On 08/19/2016 05:47 AM, Mark Hatle wrote: >> General comment on the patch set. >> >> I do like what this change is trying to accomplish. However, I think putting >> QEMU knowledge into the 'arch' is a bad idea -- unless it's being used to run >> the

[OE-core] [PATCH 1/1] kbd: remove PARALLEL_MAKEINST = ""

There isn't anything wrong when looked into its Makefile, I guess that it had been fixed during ugprade, and I've applied this patch locally for more than 2 months, there isn't anything wrong. Signed-off-by: Robert Yang --- meta/recipes-core/kbd/kbd_2.0.3.bb | 1 - 1

[OE-core] [PATCH 0/1] kbd: remove PARALLEL_MAKEINST = ""

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 rbt/kbd

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

On 08/19/2016 05:47 AM, Mark Hatle wrote: General comment on the patch set. I do like what this change is trying to accomplish. However, I think putting QEMU knowledge into the 'arch' is a bad idea -- unless it's being used to run the emulator for build-time work. The arch could very well

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

General comment on the patch set. I do like what this change is trying to accomplish. However, I think putting QEMU knowledge into the 'arch' is a bad idea -- unless it's being used to run the emulator for build-time work. The arch could very well be used by kernels that simply can't run in

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

On Thu, Aug 18, 2016 at 2:36 PM, Alistair Francis wrote: > On Wed, Aug 17, 2016 at 11:15 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 0/8] runqemu: refactor it and remove machine knowledge

On Wed, Aug 17, 2016 at 11:15 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.

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

This produces: WARNING: adwaita-icon-theme-3.20-r0 do_configure: QA Issue: adwaita-icon-theme depends on intltool but doesn't use it [redundant-intltool] Please remove the dependency on intltool and verify the build still works with a clean sysroot. Roos On 17 August 2016 at 10:05, Wang Xin

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

On 18 August 2016 at 18:58, Khem Raj 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 there being 2.35.3. These upgrades have been done

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

> On Aug 18, 2016, at 4:33 AM, Burton, Ross wrote: > > > On 18 August 2016 at 06:48, Wang Xin > wrote: > Upgrade gdk-pixbuf from 2.34.0 to 2.35.3. > > 2.35.x is a development release, so stick

Re: [OE-core] [PATCH] Specify extra paths

> On Aug 18, 2016, at 10:08 AM, Martin Jansa wrote: > > On Thu, Aug 18, 2016 at 04:41:01PM +, Khem Raj wrote: >> Some layers have gstreamer plugin recipes which include >> the .inc files from OE-Core but they do not get to find >> the patch that is being forced by

Re: [OE-core] [PATCH] Specify extra paths

On Thu, Aug 18, 2016 at 04:41:01PM +, Khem Raj wrote: > Some layers have gstreamer plugin recipes which include > the .inc files from OE-Core but they do not get to find > the patch that is being forced by the .inc file and > ends up with errors like > > WARNING: >

[OE-core] [PATCH 3/3] Revert "local.conf.sample: Disable prelink by default"

This reverts commit 300f858ba07c938427ccd05a3d7220027a03d461. Reenable prelink Signed-off-by: Mark Hatle --- meta/conf/local.conf.sample | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/meta/conf/local.conf.sample b/meta/conf/local.conf.sample

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

Internal prelink test cases reloc8 and reloc9 are failing on both ARM and PPC systems. Disable them by removing the prelink from the IMAGE_CLASSES setting. Signed-off-by: Mark Hatle --- meta/conf/local.conf.sample | 9 + 1 file changed, 9 insertions(+) diff

[OE-core] [PATCH 1/3] prelink: Move to latest version of prelink

* Uprev rtld emulation to glibc-2.23 * Fix compilation warnings * Add additional debug scopes * Change rtld build_local_scope to be breadth-first * Fix LD_PRELOAD emulation * Change function reordering to work with latest binutils Signed-off-by: Mark Hatle ---

[OE-core] [PATCH 0/3] Re-enable prelink for IA32 and MIPS

*** BLURB HERE *** The following changes since commit ecc8d346223030ee06aa6d83427f757982e948e4: sanity: Require bitbake 1.31.1 for multi-config changes (2016-08-18 10:07:18 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib mhatle/prelink

Re: [OE-core] [PATCH] insane.bbclass: handle INSANE_SKIP for license-checksum

On Thu, 2016-08-18 at 17:37 +0500, Awais Belal wrote: > The function populate_lic_qa_checksum() is used to do the > QA test for license-checksum but it does not handle the > scenario where a package adds license-checksum to its > INSANE_SKIP and hence fails in such condition. > This patch adds

Re: [OE-core] [PATCH] Specify extra paths

> On Aug 18, 2016, at 9:47 AM, Burton, Ross wrote: > > > On 18 August 2016 at 17:41, Khem Raj > wrote: > Some layers have gstreamer plugin recipes which include > the .inc files from OE-Core but they do not get to find >

Re: [OE-core] [PATCH] insane.bbclass: handle INSANE_SKIP for license-checksum

On 18 August 2016 at 13:37, Awais Belal wrote: > The function populate_lic_qa_checksum() is used to do the > QA test for license-checksum but it does not handle the > scenario where a package adds license-checksum to its > INSANE_SKIP and hence fails in such condition. >

Re: [OE-core] [PATCH] libunwind: Fix build race conflict with gcc and musl

> On Aug 18, 2016, at 9:43 AM, Khem Raj wrote: > > >> On Aug 18, 2016, at 6:46 AM, Richard Purdie >> wrote: >> >> Building libunwind, then gcc-runtime causes build failures. This is hard >> to fix since gcc-runtime wants the internal

Re: [OE-core] [PATCH] Specify extra paths

On 18 August 2016 at 17:41, Khem Raj wrote: > Some layers have gstreamer plugin recipes which include > the .inc files from OE-Core but they do not get to find > the patch that is being forced by the .inc file and > ends up with errors like > Bad commit message as you don't

Re: [OE-core] [PATCH] libunwind: Fix build race conflict with gcc and musl

> On Aug 18, 2016, at 6:46 AM, Richard Purdie > wrote: > > Building libunwind, then gcc-runtime causes build failures. This is hard > to fix since gcc-runtime wants the internal gcc unwind.h header but libunwind > wants to provide this. There are differences

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

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 and built elsewhere, and that's not changing for the foreseeable future. the

[OE-core] [PATCH] Specify extra paths

Some layers have gstreamer plugin recipes which include the .inc files from OE-Core but they do not get to find the patch that is being forced by the .inc file and ends up with errors like WARNING: /mnt/oe/meta-qcom/recipes-multimedia/gstreamer/gstreamer1.0-plugins-v4l2.bb: Unable to get

Re: [OE-core] [PATCH 4/4] gettext_0.16.1: whitespace changes to align with v0.19.8.1

On Thu, 18 Aug 2016, André Draszik wrote: > +LDFLAGS_prepend_libc-uclibc = " -lrt -lpthread " i'm not a big fan of doing the above; that is, adding *both* leading and trailing space to a string, just to play it safe. i know it doesn't hurt, but it's sloppy and might actually conceal incorrect

[OE-core] [PATCH 4/4] gettext_0.16.1: whitespace changes to align with v0.19.8.1

This further aligns this recipe with the GPLv3 version to make it easier to spot differences between the two recipes. Signed-off-by: André Draszik --- meta/recipes-core/gettext/gettext_0.16.1.bb | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git

[OE-core] [PATCH 3/4] gettext_0.16.1: align configure options with v0.19.8.1 recipe

It doesn't look like we need any of those features, so let's disable them explicitly. Signed-off-by: André Draszik --- meta/recipes-core/gettext/gettext_0.16.1.bb | 3 +++ 1 file changed, 3 insertions(+) diff --git a/meta/recipes-core/gettext/gettext_0.16.1.bb

[OE-core] [PATCH 1/4] gettext_0.16.1: use musl gettext implementation

gettext uses internal symbols to detect whether the implementation is compatible with GNU gettext. However, these symbols don't are not part of the public API, they are specific to glibc. While musl implements the GNU gettext *API* version 1 and 2 http://www.openwall.com/lists/musl/2015/04/16/3

[OE-core] [PATCH 2/4] gettext_0.16.1: fix lispdir configure option

The option is called --with(out)-lispdir, not --with(out)-lisp Signed-off-by: André Draszik --- meta/recipes-core/gettext/gettext_0.16.1.bb | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/meta/recipes-core/gettext/gettext_0.16.1.bb

Re: [OE-core] [PATCH 1/3] linux-dtb.inc: Support for .dtbo files for dtb overlays

Armin Can this be back ported to krogoth please? > On Jul 29, 2016, at 3:27 PM, Khem Raj wrote: > > From: Herve Jourdain > > Signed-off-by: Herve Jourdain > Signed-off-by: Khem Raj > --- >

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

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 > > > --- > > >

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

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/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 6 +++---

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

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/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 6 +++--- > meta/recipes-kernel/linux/linux-yocto-tiny_4.1.bb | 6 +++--- >

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

On 17 August 2016 at 11:01, Wang Xin wrote: > 4) Modify do_install_append(), since the dnssec-coverage file and > dnssec-checkds file do not exist. > When I build bind this happens: ERROR: bind-9.11.0b2-r0 do_package: QA Issue: bind: Files/directories were

[OE-core] [PATCH] libunwind: Fix build race conflict with gcc and musl

Building libunwind, then gcc-runtime causes build failures. This is hard to fix since gcc-runtime wants the internal gcc unwind.h header but libunwind wants to provide this. There are differences in include behaviour between gcc and glibc which are by design. This patch hacks around the issue by

[OE-core] [PATCH] systemd-compat-units: Only enable for systemd in DISTRO_FEATURES

This recipe only makes sense when systemd is enabled and otherwise causes world build failures. Signed-off-by: Richard Purdie diff --git a/meta/recipes-core/systemd/systemd-compat-units.bb b/meta/recipes-core/systemd/systemd-compat-units.bb index

Re: [OE-core] what means IMAGE_ROOTFS_EXTRA_SPACE_append += "+ 3000000"?

On 18 August 2016 at 14:15, Robert P. J. Day wrote: > i think you misunderstood, i was curious about the "+" *inside" the > string, but it's pretty clear that it's just adding to the current > value of that variable somewhere > I meant the content of the variable, but I

Re: [OE-core] what means IMAGE_ROOTFS_EXTRA_SPACE_append += "+ 3000000"?

On Thu, 18 Aug 2016, Burton, Ross wrote: > > On 17 August 2016 at 15:01, Robert P. J. Day wrote: > > recipes-extended/images/core-image-kernel-dev.bb:IMAGE_ROOTFS_EXTRA_SPACE_append > += "+ 300" > > > I'm guessing that's a mistake, it doesn't need a +. i

[OE-core] [PATCH] insane.bbclass: handle INSANE_SKIP for license-checksum

The function populate_lic_qa_checksum() is used to do the QA test for license-checksum but it does not handle the scenario where a package adds license-checksum to its INSANE_SKIP and hence fails in such condition. This patch adds handling of INSANE_SKIP to the populate_lic_qa_checksum() function

[OE-core] [PATCH] lib/oe/terminal.py: use an absolute path to execute oe-gnome-terminal-phonehome

From: Ming Liu A flaw was found on my Ubuntu 14.04.5 LTS, on which that gnome-terminal is the default terminal, when I run any of the tasks: bitbake busybox -c menuconfig/devshell/devpyshell bitbake virtual/kernel -c menuconfig/devshell/devpyshell I got a

Re: [OE-core] what means IMAGE_ROOTFS_EXTRA_SPACE_append += "+ 3000000"?

On 17 August 2016 at 15:01, Robert P. J. Day wrote: > recipes-extended/images/core-image-kernel-dev.bb:IMAGE_ROOTFS_EXTRA_SPACE_append > += "+ 300" > I'm guessing that's a mistake, it doesn't need a +. Ross -- ___

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

On 18 August 2016 at 06:48, Wang Xin wrote: > Upgrade gdk-pixbuf from 2.34.0 to 2.35.3. > 2.35.x is a development release, so stick with 2.34.x until 2.36.0 is available. Ross -- ___ Openembedded-core mailing list

Re: [OE-core] [oe-commits] [openembedded-core] 15/20: image.bbclass: rename COMPRESS(ION) to CONVERSION

On Thu, Aug 18, 2016 at 08:28:45AM +, g...@git.openembedded.org wrote: > rpurdie pushed a commit to branch master > in repository openembedded-core. > > commit 9d68c024790850cab72ead1e3372a5fcec4ef7b0 > Author: Patrick Ohly > AuthorDate: Fri Jul 29 17:58:52 2016 +0300

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

Hi, Here is V2, mainly fix RP's comments: (talked via IRC) * Remove a kvm commit message since qemu-kvm can only run target when its arch is the same as the host arch: The kvm support is not limited on x86 or x86_64 * Fix a typo in commit message: qemu-boot.bbclass -> qemuboot.bbclass,

[OE-core] [PATCH] core-image-kernel-dev.bb: Standardize use of _append and leading space.

Signed-off-by: Robert P. J. Day --- Tweak that line to use the same format as all other examples involving that variable, for consistency. diff --git a/meta/recipes-extended/images/core-image-kernel-dev.bb b/meta/recipes-extended/images/core-image-kernel-dev.bb index

[OE-core] [PATCH v2 3/3] kernel-module-split.bbclass: no need for running depmod

With the recent changes, executing depmod is not needed anymore. This simplifies and removes a lot of unnecessary code. Signed-off-by: André Draszik --- meta/classes/kernel-module-split.bbclass | 73 +--- 1 file changed, 1 insertion(+), 72

[OE-core] [PATCH v2 2/3] kernel-module-split.bbclass: generate dependencies across recipes

The information retrieved via depmod is incomplete with regards to kernel modules that are dependencies, in particular where two kernel modules are built from different source trees / recipes, which leads to incomplete dependency information for packages created. So far, our packages created

[OE-core] [PATCH v2 0/3] fixing kernel module cross-recipe dependency

Hi, In a situation where multiple external kernel modules are built from multiple independent recipes, we currently don't generate correct runtime dependencies of the packages created. This (small) series of patches attempts to address this. It's working well for me but there'll likely be cases

[OE-core] [PATCH v2 1/3] module.bbclass: use Module.symvers for dependants

When compiling multiple external kernel modules, where one depends on the other, there are two problems at the moment: 1) we get compile time warnings from the kernel build system due to missing symbols (from modpost). 2) Any modules generated are missing dependency information (in the

[OE-core] [PATCH 0/1] packagefeed-stability.bbclass: cleansstate should remove pkgs from deploy dir

The following changes since commit c86bf80abd87acb0da5860806822c64ec9dee089: oeqa.buildperf: use oe.path.remove() (2016-08-17 10:35:27 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rt/feed

[OE-core] [PATCH 1/1] packagefeed-stability.bbclass: cleansstate should remove pkgs from deploy dir

"bitbake recipe -ccleansstate" should remove binary pkgs from deploy dir as normal cleansstate does without packagefeed-stability.bbclass. Signed-off-by: Robert Yang --- meta/classes/packagefeed-stability.bbclass | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)

[OE-core] [PATCH 7/8] qemuboot.bbclass: add it for runqemu

It saves vars in ${DEPLOY_DIR_IMAGE}/qemuboot.py, and runqemu will import it. The bsp which can be boot by runqemu will inherit it. Signed-off-by: Robert Yang --- meta/classes/qemuboot.bbclass | 59 +++ 1 file changed, 59

[OE-core] [PATCH 1/8] qemu.inc: inherit qemu-boot.bbclass

All qemu boards should be able to boot by runqemu. Signed-off-by: Robert Yang --- meta/conf/machine/include/qemu.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/conf/machine/include/qemu.inc b/meta/conf/machine/include/qemu.inc index f44dbe6..2bc4dc2

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

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 set vars to make it can be boot by runqemu, and

[OE-core] [PATCH 6/8] qemuppc.conf: set vars for runqemu

Signed-off-by: Robert Yang --- meta/conf/machine/qemuppc.conf | 6 ++ 1 file changed, 6 insertions(+) diff --git a/meta/conf/machine/qemuppc.conf b/meta/conf/machine/qemuppc.conf index bf0038d..dbadf5a 100644 --- a/meta/conf/machine/qemuppc.conf +++

[OE-core] [PATCH 5/8] arch-mips.inc: set vars for runqemu

Both qemumips and qemumips64 can use these info to boot, so set these info in arch-mips.inc. Signed-off-by: Robert Yang --- meta/conf/machine/include/mips/arch-mips.inc | 6 ++ 1 file changed, 6 insertions(+) diff --git

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

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 set vars to make it can be boot by runqemu, and

[OE-core] [PATCH 2/8] arm: set vars for runqemu

These info are from old runqemu. Signed-off-by: Robert Yang --- meta/conf/machine/include/tune-cortexa8.inc | 4 meta/conf/machine/qemuarm.conf | 5 + 2 files changed, 9 insertions(+) diff --git a/meta/conf/machine/include/tune-cortexa8.inc

[OE-core] [PATCH 4/8] arch-x86.inc: set vars for runqemu

These vars will be used by qemuboot.class, all the x86 and x86-64 bsps can be boot by runqemu in theory, so add the settings to arch-x86.inc. Signed-off-by: Robert Yang --- meta/conf/machine/include/x86/arch-x86.inc | 15 +++ 1 file changed, 15

[OE-core] [PATCH 3/8] qemuarm64.conf: set vars for runqemu

Signed-off-by: Robert Yang --- meta/conf/machine/qemuarm64.conf | 9 + 1 file changed, 9 insertions(+) diff --git a/meta/conf/machine/qemuarm64.conf b/meta/conf/machine/qemuarm64.conf index f59fb15..fd73583 100644 --- a/meta/conf/machine/qemuarm64.conf +++