[OE-core] [PATCH v2 1/3] devtool: second fix for running from a different directory

From: Markus Lehtonen Do not change change current working directory permanently, but, only for the duration of tinfoil initialization instead. The previous fix caused very unintuitive behavior where using relative paths were solved with respect to the builddir

[OE-core] [PATCH v2 3/3] devtool: upgrade: use shutil.move instead of os.rename

From: Markus Lehtonen Rename fails over filesystem boundaries. Signed-off-by: Markus Lehtonen Signed-off-by: Paul Eggleton --- scripts/lib/devtool/upgrade.py | 2 +- 1 file changed, 1

[OE-core] [PATCH v2 0/3] devtool fixes

A couple of patches Markus previously sent rebased on top of master (also applicable on top of poky master-next) to fix some minor issues in devtool, plus one minor optimisation from me. The following changes since commit 2ad7308ee7166641eff99f3b9fe6794de143f6bc: oeqa/utils/qemurunner.py:

Re: [OE-core] State of bitbake world, Failed tasks 2015-09-13

On Fri, Sep 18, 2015 at 01:54:58PM +0200, Martin Jansa wrote: > On Wed, Aug 26, 2015 at 03:56:04PM +0200, Martin Jansa wrote: > > Time for even more PNBLACKLISTs.. > > And it got even worse. > > This run was built without sstate, so QA issues should be more complete. > I need to update the

[OE-core] [PATCH v2 2/3] devtool: runqemu: avoid recipe parse

We only need the base configuration to get the variable values we want to get here, there's no need to parse recipes / load the cache. Signed-off-by: Paul Eggleton --- scripts/lib/devtool/runqemu.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [OE-core] Error building gdk-pixbuf-native

On 22 September 2015 at 16:28, Gary Thomas wrote: > | g_module_open() failed for > /home/local/rpi2_2015-03-05/tmp/sysroots/i686-linux/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: > libharfbuzz.so.0: cannot open shared object file: No such file or directory >

[OE-core] [PATCHv2 1/2] oeqa/oetest: Remove bb as requirement for oetest.

In order for the test export runner to work oetest needs to be separated from bitbake environment. There is no need to use bb import here so we can use a logger instead. Signed-off-by: Lucian Musat --- meta/lib/oeqa/oetest.py | 29 + 1 file

Re: [OE-core] [PATCH v2 1/3] devtool: second fix for running from a different directory

On Wed, Sep 23, 2015 at 3:05 AM, Paul Eggleton < paul.eggle...@linux.intel.com> wrote: > -def setup_tinfoil(config_only=False): > +def setup_tinfoil(config_only=False, basepath=None): > """Initialize tinfoil api from bitbake""" > import scriptpath > +orig_cwd =

[OE-core] [PATCH] gcc-5.2: disable isl

We presently don't package isl. Unfortunately, if the host is already using gcc-5.2 (as is presently the case on Arch Linux), configure will autodetect the host's libisl, and do_compile will break because the system isl headers aren't pulled in. In lieu of packaging isl, disable it for now.

Re: [OE-core] [PATCH 2/2] oeqa/runexported: Removed DEPLOY_DIR as mandatory.

On Wed, Sep 23, 2015 at 2:02 AM, Lucian Musat wrote: > We don't need DEPLOY_DIR for every runtime test so there is no > need for it to be mandatory. > > Signed-off-by: Lucian Musat > --- > meta/lib/oeqa/runexported.py | 2 +- > 1 file

Re: [OE-core] [PATCH 2/2] oeqa/runexported: Removed DEPLOY_DIR as mandatory.

From: kerg...@gmail.com [mailto:kerg...@gmail.com] On Behalf Of Christopher Larson Sent: Wednesday, September 23, 2015 6:12 PM To: Musat, George L Cc: Patches and discussions about the oe-core layer Subject: Re: [OE-core] [PATCH 2/2] oeqa/runexported: Removed DEPLOY_DIR as mandatory. Sorry,

Re: [OE-core] [PATCH] gcc-5.2: disable isl

This is ok On Sep 23, 2015 7:36 AM, "Richard Tollerton" wrote: > We presently don't package isl. Unfortunately, if the host is already > using gcc-5.2 (as is presently the case on Arch Linux), configure will > autodetect the host's libisl, and do_compile will break because

[OE-core] [PATCHv2 2/2] oeqa/runexported: Removed DEPLOY_DIR as mandatory.

We don't need DEPLOY_DIR for every runtime test so there is no need for it to be mandatory. Signed-off-by: Lucian Musat --- meta/lib/oeqa/runexported.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/lib/oeqa/runexported.py

[OE-core] [PATCH] sanity.bbclass: show warning when chmod fails

From: Alex Franco * for some reason this part of: http://patchwork.openembedded.org/patch/102561/ wasn't ever merged. [YOCTO #7669] Signed-off-by: Alex Franco Signed-off-by: Martin Jansa ---

Re: [OE-core] [PATCH v2 1/3] devtool: second fix for running from a different directory

On Wednesday 23 September 2015 08:09:37 Christopher Larson wrote: > On Wed, Sep 23, 2015 at 3:05 AM, Paul Eggleton < > > paul.eggle...@linux.intel.com> wrote: > > -def setup_tinfoil(config_only=False): > > > > +def setup_tinfoil(config_only=False, basepath=None): > > """Initialize tinfoil

Re: [OE-core] [oe-commits] Ross Burton : Revert "systemd: disable problematic GCC 5.2 optimizations"

On Wed, Sep 23, 2015 at 09:46:27PM +, g...@git.openembedded.org wrote: > Module: openembedded-core.git > Branch: master-next > Commit: e5e69130c3cf20a95bab1561716d7e54db0fe1ee > URL: > http://git.openembedded.org/?p=openembedded-core.git=commit;h=e5e69130c3cf20a95bab1561716d7e54db0fe1ee >

[OE-core] [PATCH 2/3] oe.scriptutils: add logger_setup_filters

From: Christopher Larson This function sets up the default bb.msg formatter and log filters, which by default sends ERROR messages to stderr rather than stdout. Signed-off-by: Christopher Larson --- scripts/lib/scriptutils.py | 15

[OE-core] [PATCH 1/3] oe.scriptutils: enable color in a more flexible way

From: Christopher Larson Rather than recreating handlers and forcing them, iterate over the handlers and enable color on ones we can handle. This makes it easier to handle color properly when we introduce the bb.msg default log filters. Signed-off-by: Christopher Larson

[OE-core] [PATCH 3/3] recipetool, devtool: set up the logging filters

From: Christopher Larson We want errors going to stderr, the way they do in bitbake itself. Signed-off-by: Christopher Larson --- scripts/devtool| 1 + scripts/recipetool | 1 + 2 files changed, 2 insertions(+) diff --git

[OE-core] [PATCH 0/3] recipetool/devtool: send errors to stderr

From: Christopher Larson This aligns with the behavior of bitbake proper. There is a bit of code duplication between knotty and scriptutils, but that's not new -- that was the case before as well. We should consider moving these logger configuration functions into

[OE-core] [PATCH v2 1/1] gmp: Use __gnu_inline__ attribute in 4.2.1

gcc 5 defaults to C11 rules about "extern inline": this breaks any code that includes gmp.h header from gmp 4.2.1 with 'multiple definition' errors. disable-stdc patch is no longer required because of this. Signed-off-by: Jussi Kukkonen --- Changes since v1: I was

[OE-core] [PATCH] guile: cleanup buildpaths and add RDEPENDS on pkgconfig

From: Jackie Huang * fix the path for "define %pkg-config-program" in guile-config * clean the --sysroot in guile-snarf * add RDEPENDS on pkgconfig Signed-off-by: Jackie Huang --- meta/recipes-devtools/guile/guile_2.0.11.bb | 12

[OE-core] [PATCH 2/2] oeqa/runexported: Removed DEPLOY_DIR as mandatory.

We don't need DEPLOY_DIR for every runtime test so there is no need for it to be mandatory. Signed-off-by: Lucian Musat --- meta/lib/oeqa/runexported.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/lib/oeqa/runexported.py

[OE-core] [PATCH 1/2] oeqa/oetest: Remove bb as requirement for oetest.

In order for the test export runner to work oetest needs to be separated from bitbake environment. There is no need to use bb import here so we can use a logger instead. Signed-off-by: Lucian Musat --- meta/lib/oeqa/oetest.py | 12 +++- 1 file changed, 7

Re: [OE-core] [PATCH] hand the TEMPLATECONF local over to setup-builddir

Hello Lee, wow, thanks for clearing testing this; actually, to trigger my personal need for a patch, variant # A was used. Cheers, Marcus On 22.09.2015 22:25, Lee Nipper wrote: > On Tue, Sep 22, 2015 at 1:45 PM, Marcus Müller > > wrote:

[OE-core] [PATCH 1/1] p11-kit: configure without trust-paths

From: Kai Kang Configure option --with-trust-paths is only used for test scripts trust/test-extract which is not packaged by default. If the option is not provided, it checks 4 files on build machine. If the files don't exist, configure fails. Add configure option

[OE-core] [PATCH 0/1] Configure p11-kit without trust-paths

From: Kai Kang The following changes since commit 7b86c771c80d0759c2ca0e57c46c4c966f89c49e: bitbake: bitbake: bb.fetch2.git: Import errno module (2015-09-19 22:38:44 +0100) are available in the git repository at: git://git.pokylinux.org/poky-contrib kangkai/p11

[OE-core] [PATCH] gcc-shared-source: Set empty SRC_URI

gcc-source is the only gcc recipe meant to handle the fetch/unpack/patch tasks, the other gcc recipes then depend on this. This approach has been creating some confusion for tools like the archiver. The simplest way to signal to these processes that there is no source is to empty SRC_URI at the

Re: [OE-core] [PATCH 0/6] Fixes for mutilib SDK

On Tue, 2015-09-22 at 10:45 +0800, Robert Yang wrote: > Hi RP and Ross, > > These patches are required by multilib's do_rootfs and do_populate_sdk, > otherwise they are broken or partly broken. These patches don't affect > do_rootfs or do_populate_sdk without multilib are to be installed. Thanks

Re: [OE-core] [PATCH] systemd: fix tmpfiles location when multilib in use

On 23 September 2015 at 22:20, Chatre, Reinette wrote: > [Reinette] At the moment the rest of this recipe uses ${exec_prefix}/lib > instead of the new ${nonarch_libdir}. I chose to use ${exec_prefix}/lib to > remain consistent with the rest of the recipe since doing so

[OE-core] [PATCH 1/2] oeqa/runtime/parselogs.py: Fix dmesg log retrieve in sato

Sato uses busybox that fails to write log using echo "" because dmesg output can contain special characters. [YOCTO #8377] Signed-off-by: Aníbal Limón --- meta/lib/oeqa/runtime/parselogs.py | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

[OE-core] [PATCH 2/2] kmod: Change SRCREV to fix return code in error path

Systemd is failing trying to load kdbus [1] because kmod have an error in return code when try to insert module [2]. This change of SRCREV is a MINOR one only include the fix described. [YOCTO #8377] [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=8377#c0 [2]

[OE-core] [PATCH] archiver: stamp-base is dead, remove it

stamp-base was only ever used by the shared workdir code in gcc. This turned out to be problematic and has been replaced by other approaches which don't need specialist bitbake knowledge. stamp-base will likely get removed from bitbake but for now, remove it from archiver to simplfy the code

Re: [OE-core] [PATCH] systemd: fix tmpfiles location when multilib in use

From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Wednesday, September 23, 2015 2:08 PM To: Chatre, Reinette Cc: OE-core Subject: Re: [OE-core] [PATCH] systemd: fix tmpfiles location when multilib in use On 23 September 2015 at 21:49, Reinette Chatre

Re: [OE-core] Error building gdk-pixbuf-native

On Tue, 2015-09-22 at 21:28 -0300, Otavio Salvador wrote: > On Tue, Sep 22, 2015 at 8:30 PM, Khem Raj wrote: > > > >> On Sep 22, 2015, at 4:28 PM, Otavio Salvador > >> wrote: > >> > >> On Tue, Sep 22, 2015 at 8:23 PM, Khem Raj

Re: [OE-core] [PATCH] sanity.bbclass: show warning when chmod fails

On Wed, Sep 23, 2015 at 9:13 AM, Martin Jansa wrote: > From: Alex Franco > > * for some reason this part of: > http://patchwork.openembedded.org/patch/102561/ > wasn't ever merged. > > [YOCTO #7669] > > Signed-off-by: Alex Franco

[OE-core] [PATCH] systemd: fix tmpfiles location when multilib in use

Systemd's configuration files for creation, deletion and cleaning of volatile and temporary files are installed in /usr/lib even when multilib is in use (when /usr/lib64 is available). In this check the systemd.conf file will not be found if libdir is /usr/lib64 so we fix the path to match this

Re: [OE-core] [PATCH] systemd: fix tmpfiles location when multilib in use

On 23 September 2015 at 21:49, Reinette Chatre wrote: > ${exec_prefix}/lib > For neatness in master there's a variable for this - ${nonarch_libdir}. Can you change the patch to use that variable instead? Thanks Ross -- ___

[OE-core] [PATCH] gdk-pixbuf: Avoid rebuild failures

If gdkpixbuf-native rebuilds and there are stale (broken) modules lying around, it can fail to run the postinst. E.g. svg links to harfbuzz and if harfbuzz is removed from the sysroot but the svg loader isn't, we get a symbol linking issue. The reproducer is along the lines of build

Re: [OE-core] [PATCH] gdk-pixbuf: Avoid rebuild failures

On 2015-09-23 16:32, Richard Purdie wrote: If gdkpixbuf-native rebuilds and there are stale (broken) modules lying around, it can fail to run the postinst. E.g. svg links to harfbuzz and if harfbuzz is removed from the sysroot but the svg loader isn't, we get a symbol linking issue. The

[OE-core] Including machine specific mesa-driver

hi, in the qemu reference machine we see this pattern: XSERVER = "xserver-xorg \ ${@bb.utils.contains('DISTRO_FEATURES', 'opengl', 'mesa-driver-swrast', '', d)} \ Which is what I had done for my BSP layer as well. However this doesn't take into account non X11 based graphics