Re: [OE-core] configure error for glibc 2.25.2

> From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org] > On Wed, 2017-01-25 at 09:56 +, Andrew Goodbody wrote: > > > > > > From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org] > > > On Tue, 2017-01-24 at 18:08 +, Andrew Goodbody wrote: > > > > > > > > Thanks but

[OE-core] [PATCH] kmod: Fix handling of quotes in kernel command line

If a module parameter on the command line contains quotes, any spaces inside those quotes should be included as part of the parameter. Upstream-Status: Accepted Signed-off-by: James Minor --- meta/recipes-kernel/kmod/kmod.inc | 1 +

[OE-core] [PATCH] kernel.bbclass: Make symbol to vmlinuz.bin in boot directory

The changes committed with 6e58f54be103814b6b8a85b236510633c49e6832 did only consider the vmlinuz ELF kernel but some devices do reqire a raw vmlinuz.bin (as for example gcw0 in meta-handheld booted by ubiboot). Expand the above mentioned patch to consider this case. Signed-off-by: Andrea Adami

[OE-core] [oe-core][PATCH v3 1/1] gnutls: avoid accidentally using libseccomp

Specify whether to use libseccomp or not. Do not just let configure check for it. Signed-off-by: Joe Slater --- meta/recipes-support/gnutls/gnutls.inc |5 + 1 file changed, 5 insertions(+) diff --git a/meta/recipes-support/gnutls/gnutls.inc

[OE-core] rootfs build failure

I now get the following build failure from do_rootfs The stack trace of python calls that resulted in this exception/failure was: File: 'exec_python_func() autogenerated', lineno: 2, function: 0001: *** 0002:license_create_manifest(d) 0003: File:

[OE-core] [oe-core][PATCH v2 1/1] gnutls: account for ARM_EABI

Do not reference unavailable system calls when building for ARM_EABI. Signed-off-by: Joe Slater --- meta/recipes-support/gnutls/gnutls/arm_eabi.patch | 19 +++ meta/recipes-support/gnutls/gnutls_3.5.7.bb |1 + 2 files changed, 20 insertions(+)

[OE-core] [PATCH] oe-publish-sdk: add pyshtables.py to .gitignore

poky/bitbake/lib/bb/pysh/pyshtables.py should be ignored by git as it is generated. If kept in the repo, causes subsequent runs of sdk-update to fail. [ YOCTO #10963 ] Signed-off-by: Andrea Galbusera --- scripts/oe-publish-sdk | 4 ++-- 1 file changed, 2 insertions(+), 2

[OE-core] [PATCH 0/1] runqemu: disable network

Not all QEMU machines support network hardware emulation. Those machines cannot be run by "runqemu", as network hardware is implicitly always assumed. Trying to run them using "runqemu" would end up in raise Exception('Failed to run %s' % cmd) There is no way to disable network setup using

[OE-core] [PATCH 1/1] runqemu: allow bypassing of network setup

At present it is silently assumed all QEMU machines support networking. As a consequence, one cannot run QEMUs without network emulation using "runqemu". This patch allows bypassing any network setup providing the qemuboot.conf file contains: qb_net = none [YOCTO#10661] Signed-off-by: Juro

[OE-core] New warnings in default linux-yocto-4.9 builds

Few more in default build of latest 4.9.3 for qemux86. Probably caused by last linux-yocto changes. WARNING: linux-yocto-4.9.3+gitAUTOINC+03a2d3f7f9_881cba95ae-r0 do_kernel_configcheck: [kernel config]: specified values did not make it into the kernel's final configuration: --

[OE-core] [PATCH 2/3] runtime/cases/smart.py: Check for IMAGE_PKGTYPE instead of PACKAGE_CLASSES

From: Mariano Lopez smart test requires to build the image using rpm packages, this check was included, but it checked for PACKAGE_CLASSES=='package_rpm', and this is not true when building packages for rpm and deb/ipk. So this would check IMAGE_PKGTYPE instead.

[OE-core] [PATCH 0/3] Fix bugs found within runtime testing

From: Mariano Lopez This will fix some bugs found in testimage when executing tests from images downloaded from the autobuilders. The following changes since commit aa7e2717d33c2d754ec486e9148f446c1d6a3b14: ref-manual: remove core-image-directfb reference

[OE-core] [PATCH 1/3] runtime/cases/connman.py: Stop using oeRuntimeTest

From: Mariano Lopez oeRuntimeTest class is not used anymore as part of runtime migration, this particular case was missed, so fix it. [YOCTO #10964] Signed-off-by: Mariano Lopez --- meta/lib/oeqa/runtime/cases/connman.py | 2 +- 1

[OE-core] [PATCH 3/3] testimage.bbclass: Allow to run tests on autobuilder's images

From: Mariano Lopez With the change to the new framework data store dependecy was removed, instead a new file is generated and used in testimage. When testing builds from the autobuilders the test data values are from the autobuilder, including the paths. Some

[OE-core] [PATCH v2] ccache: update to 3.3.3

Release note available at this location: https://ccache.samba.org/releasenotes.html#_ccache_3_3_3 Moving to tarball source as git.samba.org is not used anymore. License checksum change is due to an update in URL, now refering to "https" protocol instead of "http", line 32:

Re: [OE-core] [PATCH 1/2] go: Add recipes for golang compilers and tools

On Wed, Jan 25, 2017 at 11:40 AM, Maciej Borzęcki wrote: > On Mon, Dec 12, 2016 at 7:02 PM, Khem Raj wrote: >> >> On Dec 12, 2016, at 4:36 AM, Gary Thomas wrote: >> >> Looking at these recipes and they seem like a good starting

Re: [OE-core] [PATCH 1/2] go: Add recipes for golang compilers and tools

On Mon, Dec 12, 2016 at 7:02 PM, Khem Raj wrote: > > On Dec 12, 2016, at 4:36 AM, Gary Thomas wrote: > > Looking at these recipes and they seem like a good starting point. > I did have some issues though: > > * bitbake go - didn't create any target

Re: [OE-core] configure error for glibc 2.25.2

> From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org] > On Tue, 2017-01-24 at 18:08 +, Andrew Goodbody wrote: > > > > > > From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org] > > > I'm running out of time to write this up and post properly but the > > > patch I think

Re: [OE-core] [PATCH] ccache: update to 3.3.3

2017-01-25 15:25 GMT+01:00 Burton, Ross : > > On 25 January 2017 at 09:18, Yannick Gicquel > wrote: >> >> -SRC_URI = "git://git.samba.org/ccache.git" >> +SRC_URI = "git://github.com/ccache/ccache.git" > > > Why don't we just use the tarballs? Ok to

[OE-core] ✗ patchtest: failure for wic: change location of .env files (rev3)

== Series Details == Series: wic: change location of .env files (rev3) Revision: 3 URL : https://patchwork.openembedded.org/series/4976/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been

[OE-core] [PATCH v3] wic: change location of .env files

Current location of .env files $STAGING_DIR/imagedata. It doesn't depend on machine and be rewritten by the builds for different machines. Changed location to $STAGING_DIR/$MACHINE/imagedata to avoid .env files to be rewritten. Signed-off-by: Ed Bartosh ---

[OE-core] ✗ patchtest: failure for wic: change location of .env files (rev2)

== Series Details == Series: wic: change location of .env files (rev2) Revision: 2 URL : https://patchwork.openembedded.org/series/4976/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have been

[OE-core] [PATCH v2] wic: change location of .env files

Current location of .env files $STAGING_DIR/imagedata. It doesn't depend on machine and be rewritten by the builds for different machines. Changed location to $STAGING_DIR/$MACHINE/imagedata to avoid .env files to be rewritten. Signed-off-by: Ed Bartosh ---

[OE-core] [PATCH] package_deb: handle allarch when mapping tune to dpkg architectures

It was discovered that buildtools-tarball can't be built with Debian packaging: E: Unable to locate package nativesdk-buildtools-perl-dummy The package exists but dpkg doesn't see it because the Architecture field isn't valid: for this package the Architecture field is 'allarch' which isn't in

Re: [OE-core] [PATCH 1/4] screen: Upgrade 4.4.0 -> 4.5.0

On Mon, Jan 23, 2017 at 11:58:57AM +0200, Maxin B. John wrote: > Removed the following Backported patches: > 1. 0001-fix-for-multijob-build.patch > 2. 0002-comm.h-now-depends-on-term.h.patch Maybe it's worth waiting a bit with this upgrade until this is resolved:

[OE-core] [PATCH v1] oeqa/sdk: Updates sanity tests for minimal eSDK

Updates sanity tests to cope with minimal eSDK installer 1. Skips the validation of sanity if packagegroup-cross-canadian is in host package. 2. Skips if SDK does not include toolchain at cases/devtool.py This should fix [YOCTO #10794] Signed-off-by: Francisco Pedraza

[OE-core] [PATCH] wic: change location of .env files

Current location of .env files $STAGING_DIR/imagedata. It doesn't depend on machine and be rewritten by the builds for different machines. Changed location to $STAGING_DIR/$MACHINE/imagedata to avoid .env files to be rewritten. Signed-off-by: Ed Bartosh ---

[OE-core] [PATCH] distrodata: add DATETIME to vardepsexclude for do_distro_check.

This task uses DATETIME so add it to vardepsexclude so bitbake doesn't refuse to execute the task when the time changes between the controller and the worker calculating the hash. [ YOCTO #10960 ] Signed-off-by: Ross Burton --- meta/classes/distrodata.bbclass | 3 +-- 1

Re: [OE-core] ✗ patchtest: failure for cryptodev: Fix changed mm interface in Kernel 4.9

On 25 January 2017 at 15:38, Daniel Schultz wrote: > I have backported this patch and I won't add the signed-off by myself. > The patch header should also contain your signed-off-by (so in the future we know who was responsible for bringing this patch into OE) and an

[OE-core] [PATCH] externalsrc: Hide created symlinks with .git/info/exclude

Add created symlinks to the exclude file. This will both make them less distracting and hide them from the srctree_hash_files function. Signed-off-by: Ola x Nilsson --- meta/classes/externalsrc.bbclass | 17 - 1 file changed, 16 insertions(+), 1 deletion(-)

Re: [OE-core] ✗ patchtest: failure for cryptodev: Fix changed mm interface in Kernel 4.9

I have backported this patch and I won't add the signed-off by myself. How should I proceed? Am 25.01.2017 um 16:23 schrieb Patchwork: == Series Details == Series: cryptodev: Fix changed mm interface in Kernel 4.9 Revision: 1 URL : https://patchwork.openembedded.org/series/4970/ State :

[OE-core] ✗ patchtest: failure for cryptodev: Fix changed mm interface in Kernel 4.9

== Series Details == Series: cryptodev: Fix changed mm interface in Kernel 4.9 Revision: 1 URL : https://patchwork.openembedded.org/series/4970/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several tests have

[OE-core] [PATCH] cryptodev: Fix changed mm interface in Kernel 4.9

The memory management interface has changed in Kernel 4.9. This patch adds a patch which fixes the paramter of the function call. Backport from https://github.com/cryptodev-linux/cryptodev-linux Based on commit f126e4837e6334d0464540995df7426fedf6b175 Signed-off-by: Daniel Schultz

Re: [OE-core] [PATCH 2/2] python3: make readline, gdbm, and db support conditional.

On 25 January 2017 at 13:03, Ismo Puustinen wrote: > +PACKAGECONFIG ??= "readline gdbm db" > +PACKAGECONFIG[readline] = ",,readline" > +PACKAGECONFIG[gdbm] = ",,gdbm" > +PACKAGECONFIG[db] = ",,db" > Whilst recipe-specific-sysroots makes this mostly moot, if the

[OE-core] State of bitbake world, Failed tasks 2017-01-20

== Number of issues - stats == {| class='wikitable' !|Date !!colspan='3'|Failed tasks !!colspan='6'|Failed depencencies!!|Signatures !!colspan='12'|QA !!Comment |- || ||qemuarm ||qemux86 ||qemux86_64

[OE-core] [PATCH] sstate: Make SSTATE_SCAN_CMD vars configurable using weak defaults.

For this we move them out of the python section so they can be overridden on a per-recipe basis. The motivation for this change is that not all tool chains need the path modifications provided by the command, and these will provide alternative or empty commands. The Go compiler is such an

Re: [OE-core] [PATCH] sstatesig: don't squash dependencies of useradd packages

Hi RP, On Mon, Jan 23, 2017 at 03:59:31PM +, Richard Purdie wrote: > On Mon, 2017-01-23 at 16:55 +0200, Maxin B. John wrote: > > Ping. > > This never merged as I was never 100% convinced this was the correct > way to solve this problem. I'd be interested to understand if the > sstatesig

Re: [OE-core] ✗ patchtest: failure for Make SSTATE_SCAN_CMD vars configurable using weak defaults.

On Wed, 2017-01-25 at 15:34 +0100, Kristian Amlie wrote: > Sorry I forgot the right patch format, but let me know if you agree > with the patch first, and I'll repost. Yes, I'm ok with it. The sdk class is long gone. Cheers, Richard -- ___

Re: [OE-core] ✗ patchtest: failure for Make SSTATE_SCAN_CMD vars configurable using weak defaults.

Sorry I forgot the right patch format, but let me know if you agree with the patch first, and I'll repost. -- Kristian On 25/01/17 15:23, Patchwork wrote: > == Series Details == > > Series: Make SSTATE_SCAN_CMD vars configurable using weak defaults. > Revision: 1 > URL :

Re: [OE-core] [oe-core][PATCH v2 1/1] gnutls: avoid accidentally using libseccomp

On 24 January 2017 at 23:56, Joe Slater wrote: > --- a/meta/recipes-support/gnutls/gnutls/arm_eabi.patch > +++ b/meta/recipes-support/gnutls/gnutls/arm_eabi.patch > @@ -1,7 +1,7 @@ > Certain syscall's are not availabe for arm-eabi, so we eliminate > reference to them. >

Re: [OE-core] [oe-core][PATCH 1/1] gnutls: avoid accidentally using libseccomp

On 24 January 2017 at 20:52, Andre McCurdy wrote: > A configure option is not a requirement for using PACKAGECONFIG. e.g. > Yes, this. Please rewrite to use a PACKAGECONFIG. Ross -- ___ Openembedded-core mailing list

Re: [OE-core] [PATCH] ccache: update to 3.3.3

On 25 January 2017 at 09:18, Yannick Gicquel wrote: > -SRC_URI = "git://git.samba.org/ccache.git" > +SRC_URI = "git://github.com/ccache/ccache.git" > Why don't we just use the tarballs? -LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=b8a4fa173ed91c1a5204ea4f9c9ead > c3" >

[OE-core] ✗ patchtest: failure for Make SSTATE_SCAN_CMD vars configurable using weak defaults.

== Series Details == Series: Make SSTATE_SCAN_CMD vars configurable using weak defaults. Revision: 1 URL : https://patchwork.openembedded.org/series/4967/ State : failure == Summary == Thank you for submitting this patch series to OpenEmbedded Core. This is an automated response. Several

Re: [OE-core] Overriding fixmepath

>> Take a look at the attached file, to me the inclusion of .a files in >> the >> fixmepath file seems wrong, so I can start with that, unless you have >> better idea. > > I think this is a very good lead. The code searches for replacements to > make with: "grep -Irl" (see sstate.bbclass) and it

[OE-core] [PATCH] Make SSTATE_SCAN_CMD vars configurable using weak defaults.

For this we move them out of the python section so they can be overridden on a per-recipe basis. The motivation for this change is that not all tool chains need the path modifications provided by the command, and these will provide alternative or empty commands. The Go compiler is such an

[OE-core] [PATCH] toolchain-shar-extract: compare SDK and host gcc versions

If ext sdk is built by gcc version higher than host gcc version and host gcc version is 4.8 or 4.9 the installation is known to fail due to the way uninative sstate package is built. It's a known issue and we don't have a way to fix it for above mentioned combinations of build and host gcc

[OE-core] [PATCH] cross: Update MULTIMACH_TARGET_SYS to reflect modern recipes

Mixing PACKAGE_ARCH with BUILD_* has always seemed somewhat odd. This comes into play when building different SDKMACHINES as the PN space for the recipes did once overlap. With the modern build process we use, this overlap is a thing of the past since PN has SDK_SYS appended to it. cross.bbclass

[OE-core] [PATCH 2/2] python3: make readline, gdbm, and db support conditional.

The three libraries' (readline, gdbm, and db) licenses belong to the GPLv3 family. Add them to to PACKAGECONFIG so they can be switched off if the licensing doesn't allow using them. Python build system autodetects the dependencies but doesn't allow them to be explicitly disabled, so just deal

[OE-core] [PATCH 1/2] bluez5: make readline support conditional.

Add readline support to PACKAGECONFIG. If readline needs if left out of compilation, the bluez utilities which depend on readline are not included in build or packages. The defaults in PACKAGECONFIG are the same as before, so there should be no change to current users. Signed-off-by: Ismo

[OE-core] [PATCH][morty] classes: Fix alternatives and rc.d ordering

From: David Vincent When using an alternative as an initscript, the ordering between update-rc.d and update-alternatives tasks during prerm and postinst tasks must always be the following in order to work: * prerm: - stop daemon - remove alternative *

[OE-core] [PATCH RFC 10/10] python-pgo-image: enable sstate for do_profile

There are caveats however, basically because of the circular dependency between python-pgo-image and python (python is a build dep of python-pgo-image, and at the same time, depends on the profile data generated by python-pgo-image). In practice the sstate data is only used when no profile data is

[OE-core] [PATCH RFC 07/10] python-pgo-image: exclude tests from the default profile target

Exclue tests that are segfaulting or otherwise failing (on qemux86 target), and thus, causing the profile task to fail. Also, disable tests that are taking very long to execute. In qemux86 target on my i7-3770K: test_lib2to3: 1908.8s test_io: 1278.4s test_itertools: 436.4s [YOCTO #9338]

[OE-core] [PATCH RFC 08/10] python: add python-tools subpackage

Useful in developing Python, e.g. in benchmarking. [YOCTO #9338] Signed-off-by: Markus Lehtonen --- meta/recipes-devtools/python/python-2.7-manifest.inc | 8 +--- meta/recipes-devtools/python/python_2.7.12.bb| 5 + 2 files changed, 10

[OE-core] [PATCH RFC 02/10] python: add python-profile-opt recipe

This patch adds a new recipe that builds a special version of python that produces profile data for profile guided optimization. It will install under /opt in order to prevent clash with the "normal" python. The new recipe directly includes the base python recipe so that they are build in as

[OE-core] [PATCH RFC 01/10] python-native: support profile optimized build

Make it possible to build python-native with profile directed optimization enabled. The feature is enabled by setting PYTHON_NATIVE_PROFILE_OPT = "1" in local.conf. The profile task to run may be specified with PYTHON_NATIVE_PROFILE_TASK variable in local.conf, e.g. PYTHON_NATIVE_PROFILE_TASK =

[OE-core] [PATCH RFC 09/10] python-pgo-image: switch python default profile task to pybench

Switch to pybench in order to reduce the time taken by profiling. [YOCTO #9338] Signed-off-by: Markus Lehtonen --- meta/recipes-devtools/images/python-pgo-image.bb | 16 +--- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git

[OE-core] [PATCH RFC 06/10] python: make profile-optimized build possible

This patch makes it possible to build python with profile directed optimization. That is, feed python build process with profile data to guide optimization. This is the third (and the last) step in profile directed optimization for Python. In order to do a profile-optimized build you need to set

[OE-core] [PATCH RFC 04/10] python-profile-opt: rename libpython

The python library needs to be renamed so that the automatic dependency generation/checking mechanism in bitbake does not get confused. Otherwise python-profile-opt will depend on libpython from the "normal" python package. [YOCTO #9338] Signed-off-by: Markus Lehtonen

[OE-core] [PATCH RFC 05/10] devtools/images: add python-pgo-image

This is a special image for profiling Python in order to utilize profile-guided-optimization. Profile data can be obtained by by running bitbake python-pgo-image -c profile. It will be located in the directory pointed by ${PYTHON_PROFILE_DIR}. The profile task that is run can be altered by

[OE-core] [PATCH RFC 03/10] python: remove path hack from setup.py

There should be no need to hack the library and include dirs in setup.py. The script detects them from compiler output. We need to remove this is because python-profile-opt recipe is built with a non-standard prefix setting (i.e. /opt) and the hack breaks the discovery of system libraries and

[OE-core] [PATCH RFC 00/10] python: support profile-optimized build

This patchset makes it possible to enable profile-guided-optimization (PGO) for Python 2.7 - both native and target recipes. Enabling PGO for python-native is simple, one patch, basically just changing the make target if PGO is enabled in build conf. However, the target version requires a lot

Re: [OE-core] Overriding fixmepath

On Wed, 2017-01-25 at 13:22 +0100, Kristian Amlie wrote: > On 25/01/17 12:24, Richard Purdie wrote: > > > > On Wed, 2017-01-25 at 11:43 +0100, Kristian Amlie wrote: > > Does this still work if you remove the > > /home/jenkins/workspace/yoctobuild/build-qemu/tmp/sysroots- > >

Re: [OE-core] Overriding fixmepath

On 25/01/17 12:24, Richard Purdie wrote: > On Wed, 2017-01-25 at 11:43 +0100, Kristian Amlie wrote: >> After the new recipe sysroots were introduced we've been having >> trouble >> compiling Go. I've narrowed it down to the path replacement mechanism >> that goes on using fixmepath. >> >> For

Re: [OE-core] [PATCH] openssh: Security Advisory - openssh - CVE-2016-10010

On 01/25/2017 07:19 AM, Li Zhou wrote: sshd in OpenSSH before 7.4, when privilege separation is not used, creates forwarded Unix-domain sockets as root, which might allow local users to gain privileges via unspecified vectors, related to serverloop.c. Porting patch from

Re: [OE-core] configure error for glibc 2.25.2

> From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org] > Sorry, yes, you're totally right. I hadn't remembered there were two > places we were making this assumption! That does look like the right > fix although I might rework that code slightly. Feel free. I'm off to fix all the

Re: [OE-core] [PATCH 1/1] package_ipk.bbclass: Add check for empty lines in DESCRIPTION

On Tue, 2017-01-24 at 11:52 -0700, Christopher Larson wrote: > > On Tue, Jan 24, 2017 at 1:37 AM, > wrote: > > From: Mariano Lopez > > > > opkg uses empty lines as separator for next package and if an ipk > > file was packaged with

[OE-core] [PATCH 4/4] gcc: Clean up unnecessary variable confusion

SDKPKGSUFFIX could only really be "nativesdk" and TARGET_SYS never contains that so the code manipulating TARGET_SYS is pointless. I suspect this once worked against MULTIMACH_TARGET_SYS which would be a different question but it no longer does. Its been cut and pasted everywhere. This patch

[OE-core] [PATCH 1/4] staging: Remove hardcoded PACKAGE_ARCHS from the class

The code was making an assumption that the only PACKAGE_ARCH in use was TUNE_PKGARCH. This is incorrect so iterate over the list from PACKAGE_EXTRA_ARCH instead. [Thanks to Andrew Goodbody for testing/fixing] Signed-off-by: Richard Purdie

[OE-core] [PATCH 2/4] gcc: Split builddir saving into its own sstate task

When we stashed the gcc build directory for use in generating the various runtimes we were being lazy and just used the staging directory. With recipe specific sysroots this means we're copying a large chunk of data around with the cross compiler which we don't really need in most cases.

[OE-core] [PATCH 3/4] gcc/gcc-source: Move libcc1 manipulation into gcc-source

Currently there is a race where if you build -cross-canadian without building gcc (target) you see QA errors about RPATHS. I've tracked this down to this manipulation where the target gcc recipe changes libcc1 in the shared sources directory. As long as you build things in the right order, the

[OE-core] [PATCH] initscripts: Populate volatile from existing file

In some cases, it may be useful to populate a volatile file from an existing one, e.g. a file in a read-only rootfs that may be edited in a read-write destination. To provide this behavior, creation of volatile files has been updated to copy a file which has been given in the field. If set to

Re: [OE-core] Overriding fixmepath

On Wed, 2017-01-25 at 11:43 +0100, Kristian Amlie wrote: > After the new recipe sysroots were introduced we've been having > trouble > compiling Go. I've narrowed it down to the path replacement mechanism > that goes on using fixmepath. > > For example, this does not work: > >   bitbake -c

[OE-core] [PATCH] watchdog: Add RCONFLICTS to watchdog-keepalive and split RDEPENDS

watchdog-keepalive is a simplified version of the watchdog daemon and can't be installed along with watchdog daemon, we need to choose which daemon install. Signed-off-by: Fabio Berton --- meta/recipes-extended/watchdog/watchdog_5.15.bb | 9 + 1 file

[OE-core] [PATCH v2] image_types.bbclass: rebuild .wks file when .wks.in changes

WKS_FILE(S) can refer to .wks.in files which get expanded during the build by do_write_wks_template. The actual content of the .wks.in file gets added to the recipe meta data during parsing, and thus we need to ensure that the recipe gets re-parsed when the file changes. This fixes two related

[OE-core] [PATCH] image_types.bbclass: rebuild .wks file when .wks.in changes

WKS_FILE(S) can refer to .wks.in files which get expanded during the build by do_write_wks_template. The actual content of the .wks.in file gets added to the recipe meta data during parsing, and thus we need to ensure that the recipe gets re-parsed when the file changes. This fixes two related

Re: [OE-core] configure error for glibc 2.25.2

On Wed, 2017-01-25 at 11:00 +, Andrew Goodbody wrote: > > > > From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org] > > On Wed, 2017-01-25 at 09:56 +, Andrew Goodbody wrote: > > > > > > > > > > > > > > > From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org > > > >

[OE-core] Overriding fixmepath

After the new recipe sysroots were introduced we've been having trouble compiling Go. I've narrowed it down to the path replacement mechanism that goes on using fixmepath. For example, this does not work: bitbake -c cleansstate go-cross bitbake go-cross But this does: bitbake -c

Re: [OE-core] configure error for glibc 2.25.2

On Wed, 2017-01-25 at 09:56 +, Andrew Goodbody wrote: > > > > From: Richard Purdie [mailto:richard.pur...@linuxfoundation.org] > > On Tue, 2017-01-24 at 18:08 +, Andrew Goodbody wrote: > > >  > > > Thanks but unfortunately that did not work for me. > > > > > > I did a cleanall on glibc

[OE-core] [PATCH] libtiff: Security Advisory - libtiff - CVE-2017-5225

Libtiff is vulnerable to a heap buffer overflow in the tools/tiffcp resulting in DoS or code execution via a crafted BitsPerSample value. Porting patch from to solve CVE-2017-5225. Signed-off-by: Li Zhou

[OE-core] [PATCH] ccache: update to 3.3.3

Release note available at this location: https://ccache.samba.org/releasenotes.html#_ccache_3_3_3 Signed-off-by: Yannick Gicquel --- meta/recipes-devtools/ccache/ccache.inc | 2 +- meta/recipes-devtools/ccache/{ccache_3.2.5.bb =>

Re: [OE-core] [PATCH v2 1/3] ccache.bbclass: enable max size setup for ccache dir

2017-01-24 0:20 GMT+01:00 Andre McCurdy : > On Fri, Jan 20, 2017 at 8:47 AM, Yannick GICQUEL > wrote: >> 2017-01-20 17:23 GMT+01:00 Yannick GICQUEL : >>> 2017-01-19 20:02 GMT+01:00 Andre McCurdy : On

[OE-core] [PATCH] scripts/buildstats-diff: simplify timestamp handling

Simply use floats instead of datetime and timedelta objects for handling timestamps. Signed-off-by: Markus Lehtonen --- scripts/buildstats-diff | 34 +++--- 1 file changed, 3 insertions(+), 31 deletions(-) diff --git