[OE-core] [PATCH v2] groff: not ship /usr/bin/glilypond

From: Mingli Yu Not ship /usr/bin/glilypond and related files such as man file /usr/share/man/man1/glilypond.1 and other three files related to glilypond under /usr/lib/groff/glilypond in embedded system, it is because: - Remove the confusion about glilypond fails to

[OE-core] [PATCH] systemd_230.bb: Set journal RuntimeMaxSize to 64M as default

At this time systemd journald uses the /run tmpfs to store logs by default systemd uses 15% of available space [1] of the /run partition, when the space runs out journald starts to vaccum/store the logs into /var/log [1]. It causes two problems one of them is timeout dev-ttySN.device's when

[OE-core] [PATCH v2 3/3] runqemu: better handle running on a host with different paths

If the STAGING_*_NATIVE directories from the config file don't exist and we're in a sourced OE build directory try to extract the paths from `bitbake -e` Signed-off-by: Joshua Lock --- scripts/runqemu | 38 ++ 1 file changed, 38

[OE-core] [PATCH v2 2/3] runqemu: assume artefacts are relative to *.qemuboot.conf

When runqemu is started with a *.qemuboot.conf arg assume that image artefacts are relative to that file, rather than in whatever directory the DEPLOY_DIR_IMAGE variable in the conf file points to. Signed-off-by: Joshua Lock --- scripts/runqemu | 15 ++- 1

[OE-core] [PATCH v2 1/3] runqemu: fix typos

Remove a stray whitespace when accessing a member variable and fix a spelling mistake in an Exception message. Signed-off-by: Joshua Lock --- scripts/runqemu | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/runqemu b/scripts/runqemu index

[OE-core] [PATCH v2 0/3] Python3 runqemu

This small series against master-next (as the python3 runqemu hasn't made it to master yet) fixes the new runqemu for a workflow of mine where I build on a headless machine and copy images locally to test them with runqemu. Changes since v1: * drop a patch to replace an ls -t call with Python's

Re: [OE-core] [PATCH 1/2] u-boot: Factor out common bits

On Mon, Sep 5, 2016 at 4:47 PM, Marek Vasut wrote: > On 09/05/2016 09:33 PM, Richard Purdie wrote: >> On Mon, 2016-09-05 at 13:26 -0300, Otavio Salvador wrote: >>> On Mon, Sep 5, 2016 at 1:24 PM, Marek Vasut wrote: On 09/05/2016 06:22 PM, Otavio Salvador

Re: [OE-core] [PATCH 1/2] u-boot: Factor out common bits

On 09/05/2016 09:33 PM, Richard Purdie wrote: > On Mon, 2016-09-05 at 13:26 -0300, Otavio Salvador wrote: >> On Mon, Sep 5, 2016 at 1:24 PM, Marek Vasut wrote: >>> >>> On 09/05/2016 06:22 PM, Otavio Salvador wrote: On Mon, Sep 5, 2016 at 1:16 PM, Marek Vasut

Re: [OE-core] [PATCH 1/2] u-boot: Factor out common bits

On Mon, 2016-09-05 at 13:26 -0300, Otavio Salvador wrote: > On Mon, Sep 5, 2016 at 1:24 PM, Marek Vasut wrote: > > > > On 09/05/2016 06:22 PM, Otavio Salvador wrote: > > > > > > On Mon, Sep 5, 2016 at 1:16 PM, Marek Vasut > > > wrote: > > > I would love to see the

[OE-core] [PATCH] oeqa.buildperf: correct globalres time format

Always use two digits for (integer part of) seconds, i.e. show '1:02.34' instead of '1:2.34'. 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

[OE-core] [PATCH] oe-build-perf-test: fix log file path

The --log-file command line argument was slightly broken as {out_dir} string replacement was not working as expected. Signed-off-by: Markus Lehtonen --- scripts/oe-build-perf-test | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OE-core] [PATCH] lttng-modules: Do not fail if CONFIG_TRACEPOINTS is not enabled

The lttng-modules are being pulled by the tools-profile image feature, however, not every kernel has the CONFIG_TRACEPOINTS feature enabled. This change makes the build do not fail when CONFIG_TRACEPOINTS is not available, allowing it to be kept being pulled by default. Signed-off-by: Otavio

[OE-core] [PATCH] lttng-modules: Bump to 6e4fc6f3 revision

This moves the recipe to the tip of stable-2.8 branch which allows the use of Linux 4.8 while keep us on a stable release. Signed-off-by: Otavio Salvador --- meta/recipes-kernel/lttng/lttng-modules_git.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff

Re: [OE-core] [PATCH 1/2] u-boot: Factor out common bits

On Mon, Sep 5, 2016 at 1:24 PM, Marek Vasut wrote: > On 09/05/2016 06:22 PM, Otavio Salvador wrote: >> On Mon, Sep 5, 2016 at 1:16 PM, Marek Vasut wrote: >>> On 09/05/2016 03:51 PM, Otavio Salvador wrote: On Mon, Sep 5, 2016 at 8:04 AM, Marek Vasut

Re: [OE-core] [PATCH 1/2] u-boot: Factor out common bits

On 09/05/2016 06:22 PM, Otavio Salvador wrote: > On Mon, Sep 5, 2016 at 1:16 PM, Marek Vasut wrote: >> On 09/05/2016 03:51 PM, Otavio Salvador wrote: >>> On Mon, Sep 5, 2016 at 8:04 AM, Marek Vasut wrote: Wouldn't that break some BSPs ? I factored out code from

Re: [OE-core] [PATCH 1/2] u-boot: Factor out common bits

On Mon, Sep 5, 2016 at 1:16 PM, Marek Vasut wrote: > On 09/05/2016 03:51 PM, Otavio Salvador wrote: >> On Mon, Sep 5, 2016 at 8:04 AM, Marek Vasut wrote: >>> Wouldn't that break some BSPs ? I factored out code from the u-boot.inc >>> afterall. >> >> It will but I

Re: [OE-core] [PATCH 1/2] u-boot: Factor out common bits

On 09/05/2016 03:51 PM, Otavio Salvador wrote: > On Mon, Sep 5, 2016 at 8:04 AM, Marek Vasut wrote: >> On 09/05/2016 01:02 PM, Richard Purdie wrote: >>> On Mon, 2016-09-05 at 00:33 +0200, Marek Vasut wrote: On 09/05/2016 12:23 AM, Marek Vasut wrote: > On 09/05/2016 12:11

Re: [OE-core] [PATCH 2/4] runqemu: use glob rather than calling out to ls

On 5 September 2016 at 15:51, Robert Yang wrote: > > > On 09/05/2016 09:59 PM, Joshua Lock wrote: > >> Use the Python glob module to find files matching a pattern, rather >> than calling out to ls and parsing the output. >> >> Signed-off-by: Joshua Lock

Re: [OE-core] [PATCH 4/4] runqemu: get NATIVE dirs from env when in source OE build dir

On 5 September 2016 at 15:47, Robert Yang wrote: > Hi Josh, > > Thanks for fixing this, I got errors when test this patch: > > $ runqemu tmp/deploy/images/qemux86/ > runqemu - INFO - Running bitbake -e... > Traceback (most recent call last): > File

Re: [OE-core] [PATCH 2/4] runqemu: use glob rather than calling out to ls

On 09/05/2016 09:59 PM, Joshua Lock wrote: Use the Python glob module to find files matching a pattern, rather than calling out to ls and parsing the output. Signed-off-by: Joshua Lock --- scripts/runqemu | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-)

Re: [OE-core] [PATCH 4/4] runqemu: get NATIVE dirs from env when in source OE build dir

Hi Josh, Thanks for fixing this, I got errors when test this patch: $ runqemu tmp/deploy/images/qemux86/ runqemu - INFO - Running bitbake -e... Traceback (most recent call last): File "/buildarea/lyang1/poky/scripts/runqemu", line 864, in ret = main() File

Re: [OE-core] [PATCH] lttng-modules: Update 2.7.3 -> 2.8.0+master

On Mon, Sep 5, 2016 at 11:44 AM, Richard Purdie wrote: > On Mon, 2016-09-05 at 11:40 -0300, Otavio Salvador wrote: >> On Wed, Aug 31, 2016 at 7:32 AM, Richard Purdie >> wrote: >> > >> > We need master for the changes to work

Re: [OE-core] [PATCH] lttng-modules: Update 2.7.3 -> 2.8.0+master

On Mon, 2016-09-05 at 11:40 -0300, Otavio Salvador wrote: > On Wed, Aug 31, 2016 at 7:32 AM, Richard Purdie > wrote: > > > > We need master for the changes to work with 4.8 kernels. > > > > Signed-off-by: Richard Purdie >

Re: [OE-core] [PATCH] lttng-modules: Update 2.7.3 -> 2.8.0+master

On Wed, Aug 31, 2016 at 7:32 AM, Richard Purdie wrote: > We need master for the changes to work with 4.8 kernels. > > Signed-off-by: Richard Purdie This broken for kernels which does not enable CONFIG_TRACEPOINTS. Up to

[OE-core] [PATCH 3/4] runqemu: assume artefacts are relative to *.qemuboot.conf

When runqemu is started with a *.qemuboot.conf arg assume that image artefacts are relative to that file, rather than in whatever directory the DEPLOY_DIR_IMAGE variable in the conf file points to. Signed-off-by: Joshua Lock --- scripts/runqemu | 11 +++ 1 file

[OE-core] [PATCH 4/4] runqemu: get NATIVE dirs from env when in source OE build dir

When we're running from a sourced OE build directory parse the STAGING_* directories from the bitbake environment, rather than using those hard-coded in the conf file. Signed-off-by: Joshua Lock --- scripts/runqemu | 22 ++ 1 file changed, 22

[OE-core] [PATCH 2/4] runqemu: use glob rather than calling out to ls

Use the Python glob module to find files matching a pattern, rather than calling out to ls and parsing the output. Signed-off-by: Joshua Lock --- scripts/runqemu | 7 +++ 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/scripts/runqemu b/scripts/runqemu

[OE-core] [PATCH 1/4] runqemu: fix typos

Remove a stray whitespace when accessing a member variable and fix a spelling mistake in an Exception message. Signed-off-by: Joshua Lock --- scripts/runqemu | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/runqemu b/scripts/runqemu index

[OE-core] [PATCH 0/4] Python3 runqemu

This small series against master-next (as the python3 runqemu hasn't made it to master yet) fixes the new runqemu for a workflow of mine where I build on a headless machine and copy images locally to test them with runqemu. The following changes since commit

Re: [OE-core] [PATCH 1/2] u-boot: Factor out common bits

On Mon, Sep 5, 2016 at 8:04 AM, Marek Vasut wrote: > On 09/05/2016 01:02 PM, Richard Purdie wrote: >> On Mon, 2016-09-05 at 00:33 +0200, Marek Vasut wrote: >>> On 09/05/2016 12:23 AM, Marek Vasut wrote: On 09/05/2016 12:11 AM, Richard Purdie wrote: > On Sun, 2016-09-04 at

[OE-core] [PATCH 2/2] selftest/liboe: add a test for copyhardlinktree()

Add a simple test to validate that the number of files in the destination matches the number of files in the source after the copyhardlinktree() has been performed. Signed-off-by: Joshua Lock --- meta/lib/oeqa/selftest/liboe.py | 29 + 1 file

[OE-core] [PATCH 1/2] oe.path: fix copyhardlinktree()

The change to preserve extended attributes in copytree() and copyhardlinktree() (e591d69103a40ec4f76d1132a6039d9cb1555103) resulted in an incorrect cp invocation in copyhardlinktree() when the source directory contained hidden files. This was because the passed src was modified in place but some

[OE-core] [PATCH 0/2] Fix oe.path.copyhardlinktree()

My recent change to preserve extended attributes in oe.path resulted in a copyhardlinktree() being broken when the source contains hidden files. This series includes a fix for copyhardlinktree() and a simple selftest for copyhardlinktree() which ensures the source and destination have the same

[OE-core] State of bitbake world 2016-09-01

This time with complete QA log, I've also upgraded jenkins slaves running these builds from 14.04 to 16.04. == Number of issues - stats == {| class='wikitable' !|Date !!colspan='3'|Failed tasks !!colspan='6'|Failed depencencies!!|Signatures

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

On Fr, 2016-08-26 at 11:38 +0100, André Draszik wrote: > On Do, 2016-08-18 at 08:56 +0100, André Draszik wrote: > > > > In a situation where multiple external kernel modules are built > > from multiple independent recipes, we currently don't generate > > correct runtime dependencies of the

Re: [OE-core] [PATCH 1/2] u-boot: Factor out common bits

On 09/05/2016 01:02 PM, Richard Purdie wrote: > On Mon, 2016-09-05 at 00:33 +0200, Marek Vasut wrote: >> On 09/05/2016 12:23 AM, Marek Vasut wrote: >>> On 09/05/2016 12:11 AM, Richard Purdie wrote: On Sun, 2016-09-04 at 23:49 +0200, Marek Vasut wrote: > On 09/04/2016 11:28 PM, Richard

Re: [OE-core] [PATCH 1/2] u-boot: Factor out common bits

On Mon, 2016-09-05 at 00:33 +0200, Marek Vasut wrote: > On 09/05/2016 12:23 AM, Marek Vasut wrote: > > On 09/05/2016 12:11 AM, Richard Purdie wrote: > > > On Sun, 2016-09-04 at 23:49 +0200, Marek Vasut wrote: > > > > On 09/04/2016 11:28 PM, Richard Purdie wrote: > > > > > On Sun, 2016-09-04 at

Re: [OE-core] [PATCH 0/2] meta: fix gobject-introspection-native and coreutils-native

Sorry, please use the patch on oe-core-contrib: git://git.openembedded.org/openembedded-core-contrib rbt/2fixes http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=rbt/2fixes Robert Yang (2): coreutils: enable xattr for native gobject-introspection: set

[OE-core] [PATCH] image.bbclass: do not check size of the debugfs image

The debugfs is supposed to be used in addition to the normal image for debugging purposes, it doesn't make sense to artificially limit its maximum size. Signed-off-by: André Draszik --- meta/classes/image.bbclass | 6 ++ 1 file changed, 6 insertions(+) diff --git

[OE-core] [PATCH] image.bbclass: also mask debugfs versions of masked images

When IMAGE_GEN_DEBUGFS is enabled, and IMAGE_FSTYPES_DEBUGFS is left at its default (as suggested by local.conf.sample.extended), recipe parsing fails: bitbake kern-tools-native # or anything else for that matter ERROR: /meta/recipes-core/images/build-appliance-image_15.0.0.bb: No IMAGE_CMD

[OE-core] [PATCH 0/2] meta: fix gobject-introspection-native and coreutils-native

The following changes since commit 0a024bf2f2ed14be9b6e3e8e911e826969ff9b7e: poky: Update to linux-yocto 4.8 (2016-09-04 16:58:53 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib rbt/2fixes http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=rbt/2fixes

[OE-core] [PATCH 2/2] gobject-introspection: set GI_SCANNER_DISABLE_CACHE for native

The native recipe should not write files to $HOME/.cache as target, this can avoid problems when multi builds are running on the same host like: | File "./g-ir-scanner", line 66, in | sys.exit(scanner_main(sys.argv)) | File "../gobject-introspection-1.48.0/giscanner/scannermain.py", line

[OE-core] [PATCH 1/2] coreutils: enable xattr for native

The lib/oe/path.py requires xattr, fixed: Subprocess output: cp: cannot preserve extended attributes, cp is built without xattr support Signed-off-by: Robert Yang --- meta/recipes-core/coreutils/coreutils_8.25.bb | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)

Re: [OE-core] [PATCH 00/28] Enable gtk-doc

* Alexander Kanavin [160902 17:08]: > On 09/02/2016 12:59 AM, Randy MacLeod wrote: > > > Gtk-doc generation happens if 'api-documentation' distro feature is > > > enabled > > > (it is by default), and 'qemu-usermode' is in machine features. > > Should this