Re: [OE-core] [PATCH] package.bbclass: improve permission handling

On Wed, 2016-04-13 at 16:17 -0600, Dan McGregor wrote: From: Dan McGregor > Change fs_link_table to be keyed by path, just like fs_perms_table. When a new entry is coming in for either table, remove any previous entry for that path. This way

[OE-core] Warnings from autotools_copy_aclocals()

Does anyone else see these type of warnings from autotools_copy_aclocals()? I don't remember exactly when they started (a few months ago at least, maybe more). WARNING: gmp-4.2.1-r0 do_configure: /.../build-dcx960-debug/tmp/sstate-control/manifest-dcx960-debug-glibc-initial.populate_sysroot not

Re: [OE-core] [PATCH v2] kernel-uimage: change target image to vmlinux

On 04/13/2016 08:17 PM, Ruslan Bilovol wrote: > Commit e69525: "kernel: Build uImage only when really > needed" hardcoded target kernel image to zImage for > case if uImage is generated by OpenEmbedded buildsystem. > > However not all kernel architectures support zImage > target, for example

Re: [OE-core] Over-pruning the sstate cache

On Thu, 2016-04-14 at 09:33 +1200, Paul Eggleton wrote: > On Wed, 13 Apr 2016 11:11:11 Otavio Salvador wrote: > > On Wed, Apr 13, 2016 at 11:01 AM, Mike Crowe > > wrote: > > > On Wednesday 13 April 2016 at 10:47:13 -0300, Otavio Salvador > > > wrote: > > > > Couldn't this to be

Re: [OE-core] Over-pruning the sstate cache

On Wed, 13 Apr 2016 11:11:11 Otavio Salvador wrote: > On Wed, Apr 13, 2016 at 11:01 AM, Mike Crowe wrote: > > On Wednesday 13 April 2016 at 10:47:13 -0300, Otavio Salvador wrote: > >> Couldn't this to be done, similar to the fetchall task? > > > > That's the sort of thing I was

Re: [OE-core] [PATCH] package.bbclass: handle links in sorted order

On 13 April 2016 at 11:40, Randle, William C wrote: > On Wed, 2016-04-13 at 11:30 -0600, Dan McGregor wrote: > > On 12 April 2016 at 10:51, Denys Dmytriyenko wrote: > > On Tue, Apr 12, 2016 at 08:22:21AM -0700, Bill Randle wrote: > > When processing

[OE-core] [PATCH v2] kernel-uimage: change target image to vmlinux

Commit e69525: "kernel: Build uImage only when really needed" hardcoded target kernel image to zImage for case if uImage is generated by OpenEmbedded buildsystem. However not all kernel architectures support zImage target, for example AArch64 doesn't, so building of kernel is failing on this

Re: [OE-core] [PATCH] package.bbclass: handle links in sorted order

On Wed, 2016-04-13 at 11:30 -0600, Dan McGregor wrote: On 12 April 2016 at 10:51, Denys Dmytriyenko > wrote: On Tue, Apr 12, 2016 at 08:22:21AM -0700, Bill Randle wrote: When processing links, the directories are processed in unsorted order which can

Re: [OE-core] [PATCH] package.bbclass: handle links in sorted order

On 12 April 2016 at 10:51, Denys Dmytriyenko wrote: > On Tue, Apr 12, 2016 at 08:22:21AM -0700, Bill Randle wrote: >> When processing links, the directories are processed in unsorted order >> which can result in cases like /var/lock -> /run/lock handled before >> /var/run -> /run

[OE-core] [PATCH] ext-sdk-prepare.py: exclude do_rm_work from unexpected output; create unit test

When installing the esdk with INHERIT += "rm_work", the script complains about do_rm_work as unexpected output from the bitbake run. This patch ignores any output lines with do_rm_work and further refactors the output comparison into its own function creates a new unit test to verify the fix. The

Re: [OE-core] Fwd: [PATCH] Access c_ispeed and c_ospeed via APIs

On Wed, Apr 13, 2016 at 10:15 AM, Bruce Ashfield wrote: > On 2016-04-13 11:57 AM, Khem Raj wrote: >> >> On Tue, Apr 12, 2016 at 3:33 PM, Khem Raj wrote: >>> >>> I think I see the problem now. The constant should be converted to use >>> Bnn >>>

Re: [OE-core] Fwd: [PATCH] Access c_ispeed and c_ospeed via APIs

On 2016-04-13 11:57 AM, Khem Raj wrote: On Tue, Apr 12, 2016 at 3:33 PM, Khem Raj wrote: I think I see the problem now. The constant should be converted to use Bnn values. When calling the baudrate apis. I will send a patch for you to test once I am close to computer I

Re: [OE-core] [PATCHv2 1/1] Revert "useradd.bbclass: remove user/group created by the package in clean* task"

On Wed, 2016-04-13 at 15:14 +, Peter Kjellerstedt wrote: > > -Original Message- > > From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org] > > Sent: den 13 april 2016 13:05 > > To: Peter Kjellerstedt; Otavio Salvador > > Cc: OE Core (openembedded-core@lists.openembedded.org)

[OE-core] [PATCH] devtool: don't copy .git when building the eSDK

When creating an eSDK ensure that any .git directories are not included. [ YOCTO #9426 ] Signed-off-by: Stephano Cetola --- meta/lib/oe/copy_buildsystem.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/lib/oe/copy_buildsystem.py

[OE-core] [PATCH 3/5] linux-yocto/4.4: BXT enablement

ASoC HDMI audio backports + mmc fixes backports + misc enablement changes (all backports): db28bb1e7a68 async: export current_is_async() e89355d51cc4 PM / runtime: Add new helper for conditional usage count incrementation dcf8de0931b1 ALSA: hda - hdmi defer to register acomp eld notifier

[OE-core] [PATCH 5/5] linux-yocto: make aufs4 optional

An always on configuration of aufs4 crept into the default kernel configuration blocks. With this change, aufs-enable.scc can be used to turn on aufs via a KERNEL_FEATURES entry. We can now have co-existing unionfs solutions and can update them without breaking builds that haven't opted-in.

[OE-core] [PATCH 1/5] linux-yocto/4.4: gpio-pca953x: fix the "drive" property cannot read/write

The gpio_drive_show/store use incorrect gpio_desc, this causes the drive sysfs property cannot be used, This patch fixes this issue Upstream-status: Inappropriate, custom code for legacy userspace Signed-off-by: Yong Li Signed-off-by: Bruce Ashfield

[OE-core] [PATCH 4/5] linux-yocto: tiny and pin ctrl config updates

Merging the following two commits: ab0d998117cc ktypes/tiny/tiny.cfg: support /proc/sys 349e9ce59f7b features: enable pinctrl driver for Broxton Signed-off-by: Bruce Ashfield --- meta/recipes-kernel/linux/linux-yocto-rt_4.1.bb | 2 +-

[OE-core] [PATCH 2/5] linux-yocto/4.1: mainline SPI backports

Backporting SPI changes for the Broxton and Apollo lake: 91f62d4a0a31 spi: pxa2xx: derive struct chip_data from struct drv_data a9ed63a84921 spi: pxa2xx: Remove CONFIG_SPI_PXA2XX_DMA f218d99d91ad spi: pxa2xx: Remove redundant call to lpss_ssp_setup() in probe c02fa78f26b3 spi: pxa2xx: Rework

[OE-core] [PATCH 0/5] linux-yocto: consolidated pull request

Hi all, This series contains some changes that I've been gathering over the past week. Nothing serious, just BSP mainline backports, configuration tweaks to tiny (for usability) and a change to make aufs4 opt-in (versus always on). I've built and booted this for qemu* (standard and -rt).

Re: [OE-core] [PATCHv2 1/1] Revert "useradd.bbclass: remove user/group created by the package in clean* task"

Hi Peter, On Wed, Apr 13, 2016 at 03:14:09PM +, Peter Kjellerstedt wrote: > > -Original Message- > > From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org] > > Sent: den 13 april 2016 13:05 > > To: Peter Kjellerstedt; Otavio Salvador > > Cc: OE Core

Re: [OE-core] Fwd: [PATCH] Access c_ispeed and c_ospeed via APIs

On 2016-04-13 11:57 AM, Khem Raj wrote: On Tue, Apr 12, 2016 at 3:33 PM, Khem Raj wrote: I think I see the problem now. The constant should be converted to use Bnn values. When calling the baudrate apis. I will send a patch for you to test once I am close to computer I

Re: [OE-core] Fwd: [PATCH] Access c_ispeed and c_ospeed via APIs

On Tue, Apr 12, 2016 at 3:33 PM, Khem Raj wrote: > I think I see the problem now. The constant should be converted to use Bnn > values. When calling the baudrate apis. I will send a patch for you to test > once I am close to computer I have sent a potential patch.

[OE-core] [PATCH] socat: Use c_ispeed and c_ospeed based upon libc

musl calls them __c_ispeed and __c_ospeed and we can not use get/set APIs because the get APIs will return the value from iflags and not from *speed element from termios struct Signed-off-by: Khem Raj --- ...001-Access-c_ispeed-and-c_ospeed-via-APIs.patch | 53

[OE-core] [PATCH] site: Cache config vars for ccache

ccache's configure tries to do a runtime test to determine hw_cv_func_snprintf_c99 and hw_cv_func_vsnprintf_c99 which wont work in OE. c99 versions of these functions are provided on all supported libc implementations in OE-Core Signed-off-by: Khem Raj ---

Re: [OE-core] Over-pruning the sstate cache

On Wednesday 13 April 2016 at 11:11:11 -0300, Otavio Salvador wrote: > On Wed, Apr 13, 2016 at 11:01 AM, Mike Crowe wrote: > > On Wednesday 13 April 2016 at 10:47:13 -0300, Otavio Salvador wrote: > >> Couldn't this to be done, similar to the fetchall task? > > > > That's the sort

Re: [OE-core] [PATCHv2 1/1] Revert "useradd.bbclass: remove user/group created by the package in clean* task"

> -Original Message- > From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org] > Sent: den 13 april 2016 13:05 > To: Peter Kjellerstedt; Otavio Salvador > Cc: OE Core (openembedded-core@lists.openembedded.org) > Subject: Re: [OE-core] [PATCHv2 1/1] Revert "useradd.bbclass: remove

[OE-core] [PATCH] rpm: more verbose errors in rpmTempFile

This patch adds better error logging inside the rpm tempfile function in order to be able to better analyze a rare and very hard-to-reproduce failure in oe-selftest for rpm signing. [YOCTO #9416] Signed-off-by: Markus Lehtonen ---

Re: [OE-core] [PATCH] matchbox-keyboard: Hide desktop launcher

On 13 April 2016 at 13:42, Gary Thomas wrote: > Wow, what an assumption! Anyway, adding the correct machconfig for > my target fixes the problem. > As the author, I decided that the choice of keyboard or not by default is pretty much a coin toss, but I suspect the

Re: [OE-core] Over-pruning the sstate cache

On Wed, Apr 13, 2016 at 11:01 AM, Mike Crowe wrote: > On Wednesday 13 April 2016 at 10:47:13 -0300, Otavio Salvador wrote: >> Couldn't this to be done, similar to the fetchall task? > > That's the sort of thing I was thinking of with my "all_populate_sysroot" > task in my

Re: [OE-core] Over-pruning the sstate cache

On Wednesday 13 April 2016 at 10:47:13 -0300, Otavio Salvador wrote: > On Tue, Apr 12, 2016 at 5:50 PM, Richard Purdie > wrote: > > On Tue, 2016-04-12 at 19:51 +0100, Mike Crowe wrote: > >> On Tuesday 29 March 2016 at 15:11:10 +0100, Richard Purdie wrote: > >>

Re: [OE-core] Over-pruning the sstate cache

On Tue, Apr 12, 2016 at 5:50 PM, Richard Purdie wrote: > On Tue, 2016-04-12 at 19:51 +0100, Mike Crowe wrote: >> On Tuesday 29 March 2016 at 15:11:10 +0100, Richard Purdie wrote: >> > On Tue, 2016-03-29 at 13:56 +0100, Mike Crowe wrote: >> > >

Re: [OE-core] [PATCH] matchbox-keyboard: Hide desktop launcher

On 2016-04-13 14:24, Maxin B. John wrote: Hi, On Wed, Apr 13, 2016 at 02:13:43PM +0200, Gary Thomas wrote: On 2016-04-13 14:08, Jussi Kukkonen wrote: On 13 April 2016 at 14:35, Gary Thomas > wrote: Have you checked that your

Re: [OE-core] [PATCH] matchbox-keyboard: Hide desktop launcher

Hi, On Wed, Apr 13, 2016 at 02:13:43PM +0200, Gary Thomas wrote: > On 2016-04-13 14:08, Jussi Kukkonen wrote: > >On 13 April 2016 at 14:35, Gary Thomas >> wrote: > > > >Have you checked that your /etc/formfactor/machconfig contains >

Re: [OE-core] [PATCH] matchbox-keyboard: Hide desktop launcher

On 2016-04-13 14:08, Jussi Kukkonen wrote: On 13 April 2016 at 14:35, Gary Thomas > wrote: On 2016-04-12 10:14, Jussi Kukkonen wrote: Add patch that hides the keyboard desktop launcher, remove patch that tries and fails to make

Re: [OE-core] [PATCH] matchbox-keyboard: Hide desktop launcher

On 13 April 2016 at 14:35, Gary Thomas wrote: > On 2016-04-12 10:14, Jussi Kukkonen wrote: > >> Add patch that hides the keyboard desktop launcher, remove patch that >> tries and fails to make the keyboard a single-instance application. >> >> The desktop launcher of

Re: [OE-core] [PATCH] matchbox-keyboard: Hide desktop launcher

On 2016-04-12 10:14, Jussi Kukkonen wrote: Add patch that hides the keyboard desktop launcher, remove patch that tries and fails to make the keyboard a single-instance application. The desktop launcher of matchbox-keyboard is a source of far more problems than solutions: As an example there's

Re: [OE-core] userdel_sysroot_sstate failed when try to remove group

On Fri, 2016-04-08 at 14:19 -0300, Fabio Berton wrote: > I'm getting this error when building recipe meta-networking/recipes > -daemons/cyrus-sasl/cyrus-sasl_2.1.26.bb > from meta-openembedded: > > DEBUG: Executing shell function userdel_sysroot_sstate > NOTE: cyrus-sasl: Performing userdel with

[OE-core] [PATCH] rootfs-postcommands: handle broken links when writing manifest

If the manifest link is broken then os.path.exists() returns False so the link isn't removed, resulting in the os.symlink() call failing as the file already exists. Prevent this by using os.path.lexists to check that the symlink itself exists, not the target. Signed-off-by: Ross Burton

Re: [OE-core] [PATCHv2 1/1] Revert "useradd.bbclass: remove user/group created by the package in clean* task"

I am pretty frustrated with this thread. The reasons are perhaps not immediately obvious though. The issue is that there are only a limited number of people who actually dive in and try and fix some of the underlying "core architecture" bugs. There is what I believe to be a pretty good patch here

[OE-core] [wic][PATCH] wic: fix bug in handling fsoptions

Partitions specifying --fsoptions were silently skipped by wic due to the old bug introduced when removing code related to subvolume handling: - if mountpoint == "/" or not fsopts or fsopts.find("subvol=") == -1 + if mountpoint == "/" or not fsopts: [YOCTO #9396] Signed-off-by: Ed Bartosh

Re: [OE-core] Build failures due to libtdb racing with libbsd

On Wed, Apr 13, 2016 at 11:34 AM, Burton, Ross wrote: > > On 13 April 2016 at 10:07, Ulf Magnusson wrote: >> >> The problem seems to be a race with building libbsd (and unlucky >> timing in my build). Adding libbsd to DEPENDS fixes the problem. >> >>

Re: [OE-core] Build failures due to libtdb racing with libbsd

On 13 April 2016 at 10:07, Ulf Magnusson wrote: > The problem seems to be a race with building libbsd (and unlucky > timing in my build). Adding libbsd to DEPENDS fixes the problem. > > For some added context, libtdb uses a nonstandard ./configure from the > Samba project

Re: [OE-core] [PATCH] devtool: sdk-update fails on remote hosts

Hi Stephano, On 12 April 2016 at 23:08, Stephano Cetola wrote: > This fixes bug #9426: > https://bugzilla.yoctoproject.org/show_bug.cgi?id=9426 > > Skip .git folders when copying the build system. > The shortlog mentions remote hosts but I don't see how that is

Re: [OE-core] Build failures due to libtdb racing with libbsd

On Wed, Apr 13, 2016 at 11:07 AM, Ulf Magnusson wrote: > Hello, > > I get libtdb build failures like the following. The failing file > varies between runs. > > ERROR: oe_runmake failed > ERROR: Function failed: do_compile > Log data follows: > | DEBUG: Executing shell

[OE-core] [PATCH 1/1] buildtools-tarball.bb: set TOOLCHAIN_NEED_CONFIGSITE_CACHE to null

buildtools-tarball doesn't need config site, set TOOLCHAIN_NEED_CONFIGSITE_CACHE to null so that no target recipes will be built when bitbake buildtools-tarball. Signed-off-by: Robert Yang --- meta/recipes-core/meta/buildtools-tarball.bb | 3 +++ 1 file changed, 3

[OE-core] [PATCH 0/1] buildtools-tarball.bb: set TOOLCHAIN_NEED_CONFIGSITE_CACHE to null

The following changes since commit b3afe7d9bd25a943e947de3ec064ea245173c5a8: archiver: Ensure sstate-inputdir directory is created (2016-04-12 22:46:48 +0100) are available in the git repository at: git://git.openembedded.org/openembedded-core-contrib rbt/bt

[OE-core] Build failures due to libtdb racing with libbsd

Hello, I get libtdb build failures like the following. The failing file varies between runs. ERROR: oe_runmake failed ERROR: Function failed: do_compile Log data follows: | DEBUG: Executing shell function do_compile | NOTE: make -j 16 -e MAKEFLAGS= | WAF_MAKE=1

[OE-core] [PATCH v2] bind: CVE-2016-1285 CVE-2016-1286

Fixes following vulnerabilities: CVE-2016-1285 bind: malformed packet sent to rndc can trigger assertion failure CVE-2016-1286 bind: malformed signature records for DNAME records can trigger assertion failure [YOCTO #9400] External References: