[OE-core] [PATCH] acl: Fix re pattern in test cases

From: He Zhe ls adds a '.' at the end of the permission field list on SELinux machines, filter this out so root tests work on SELinux machines. And backport one patch for other tests. Signed-off-by: He Zhe --- meta/recipes-support/attr/acl.inc

Re: [OE-core] [PATCH][master][Drown] openssl: Security fix Drown via 1.0.1g update

On Wed, Mar 2, 2016 at 12:06 PM, Andre McCurdy wrote: > On Wed, Mar 2, 2016 at 11:14 AM, akuster wrote: >> >> On 03/02/2016 10:06 AM, Andre McCurdy wrote: >>> On Tue, Mar 1, 2016 at 11:38 PM, Armin Kuster wrote: From: Armin

Re: [OE-core] [PATCH] gcc-runtime.inc: disable libitm for little endian MIPS too

On Wed, Mar 2, 2016 at 10:24 PM, Khem Raj wrote: > On Wed, Mar 2, 2016 at 10:04 PM, Mark Hatle wrote: >> On 3/2/16 11:07 PM, Andre McCurdy wrote: >>> libitm is already disabled for big endian MIPS, but needs to be >>> disabled for little endian MIPS

Re: [OE-core] [PATCH] gcc-runtime.inc: disable libitm for little endian MIPS too

On Wed, Mar 2, 2016 at 10:04 PM, Mark Hatle wrote: > On 3/2/16 11:07 PM, Andre McCurdy wrote: >> libitm is already disabled for big endian MIPS, but needs to be >> disabled for little endian MIPS targets too. > > No objection to the patch, but do we have any little

Re: [OE-core] [PATCH] gcc-runtime.inc: disable libitm for little endian MIPS too

On 3/2/16 11:07 PM, Andre McCurdy wrote: > libitm is already disabled for big endian MIPS, but needs to be > disabled for little endian MIPS targets too. No objection to the patch, but do we have any little endian MIPS currently defined or buildable to test? All of the samples I've seen are all

[OE-core] [PATCH] gcc-runtime.inc: disable libitm for little endian MIPS too

libitm is already disabled for big endian MIPS, but needs to be disabled for little endian MIPS targets too. Signed-off-by: Andre McCurdy --- meta/recipes-devtools/gcc/gcc-runtime.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git

[OE-core] [PATCH] eudev: recipe formatting improvements

Formatting improvements only, no functional changes. Signed-off-by: Andre McCurdy --- meta/recipes-core/udev/eudev_3.1.5.bb | 124 -- 1 file changed, 60 insertions(+), 64 deletions(-) diff --git a/meta/recipes-core/udev/eudev_3.1.5.bb

Re: [OE-core] [PATCH][master][Drown] openssl: Security fix Drown via 1.0.1g update

On Wed, Mar 2, 2016 at 11:14 AM, akuster wrote: > > On 03/02/2016 10:06 AM, Andre McCurdy wrote: >> On Tue, Mar 1, 2016 at 11:38 PM, Armin Kuster wrote: >>> From: Armin Kuster >>> >>> CVE-2016-0800 >>> CVE-2016-0705 >>> CVE-2016-0798

[OE-core] [PATCH 2/2] sdk_update.py: Enable local sdk-update tests

Testing of local sdk updates was commented out. Local sdk updates are functional now, so the tests should be re-enabled. Signed-off-by: Juro Bystricky --- meta/lib/oeqa/sdkext/sdk_update.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[OE-core] [PATCH 1/2] sdk.py: Fix undefined variable

"sdk_update" uses a variable newsdk_path, which was never declared. This would cause the command: devtool sdk-update to fail with an error: NameError: global name 'newsdk_path' is not defined The remedy is to declare newsdk_path as it was no doubt intended, corresponding to the argument

Re: [OE-core] [PATCH 1/1] yocto-bsp: Set linux-yocto-4.1 as default for x86-64

On 3/2/2016 11:37 AM, Saul Wold wrote: On Wed, 2016-03-02 at 08:14 +, mariano.lo...@linux.intel.com wrote: From: Mariano Lopez Setting default kernel to linux-yocto-4.1 now that 3.19 bbappend is no longer in the tree. This should default to 4.4 for 2.1,

Re: [OE-core] [PATCH][master][Drown] openssl: Security fix Drown via 1.0.1g update

On Tue, Mar 1, 2016 at 11:38 PM, Armin Kuster wrote: > From: Armin Kuster > > CVE-2016-0800 > CVE-2016-0705 > CVE-2016-0798 > CVE-2016-0797 > CVE-2016-0799 > CVE-2016-0702 > CVE-2016-0703 > CVE-2016-0704 > >

Re: [OE-core] [PATCH 1/1] yocto-bsp: Set linux-yocto-4.1 as default for x86-64

On Wed, 2016-03-02 at 08:14 +, mariano.lo...@linux.intel.com wrote: > From: Mariano Lopez > > Setting default kernel to linux-yocto-4.1 now that > 3.19 bbappend is no longer in the tree. > This should default to 4.4 for 2.1, correct? 4.1 is the LSB/LTS kernel

[OE-core] [PATCH 1/1] yocto-bsp: Set linux-yocto-4.1 as default for x86-64

From: Mariano Lopez Setting default kernel to linux-yocto-4.1 now that 3.19 bbappend is no longer in the tree. [YOCTO #9047] Signed-off-by: Mariano Lopez --- .../target/arch/x86_64/recipes-kernel/linux/kernel-list.noinstall

Re: [OE-core] [PATCH 04/19] nspr: update to 4.12

On Wed, Mar 02, 2016 at 03:23:25PM +, Richard Purdie wrote: > On Wed, 2016-03-02 at 06:30 -0800, Khem Raj wrote: > > On Wed, Mar 2, 2016 at 6:18 AM, Alexander Kanavin > > wrote: > > > his probably could be however OE-Core supports musl and poky > > > > -tiny

Re: [OE-core] [PATCHv2] Add tune for 32-bit ARMv8-a

On Wed, Mar 2, 2016 at 11:35 AM, Dragomir Daniel < daniel.drago...@windriver.com> wrote: > Hi Andrei, > > > On 03/02/2016 02:17 AM, Andrei Gherzan wrote: > > Hi Daniel, > > On Sat, Feb 27, 2016 at 1:44 PM, Daniel Dragomir < > daniel.drago...@windriver.com> wrote: >

Re: [OE-core] [PATCH 04/19] nspr: update to 4.12

On Wed, 2016-03-02 at 06:30 -0800, Khem Raj wrote: > On Wed, Mar 2, 2016 at 6:18 AM, Alexander Kanavin > wrote: > > his probably could be however OE-Core supports musl and poky > > > -tiny > > > defaults to it. It will be good to test > > > changes for it when

[OE-core] [PATCH v7 1/5] gpg_sign: add local ipk package signing functionality

Implement ipk signing inside the sign_ipk bbclass using the gpg_sign module and configure signing similar to how rpm does it. sign_ipk uses gpg_sign's detach_sign because its functionality is identical to package feed signing. IPK signing process is a bit different from rpm: - Signatures are

[OE-core] [PATCH v7 3/5] gpg_sign: export_pubkey: add signature type support

Add support for multiple types of signatures (binary or ascii) in export_pubkey(). There is no change in behaviour for the function, the previous implicit default is the new parameter "armor" default. Signed-off-by: Ioan-Adrian Ratiu --- meta/lib/oe/gpg_sign.py | 6 --

[OE-core] [PATCH v7 5/5] package_manager: sign IPK package feeds

Create gpg signed ipk package feeds using the gpg backend if configured. Signed-off-by: Ioan-Adrian Ratiu --- meta/classes/sign_package_feed.bbclass | 17 - meta/lib/oe/package_manager.py | 17 +++-- 2 files changed, 31 insertions(+), 3

[OE-core] [PATCH v7 4/5] signing-keys: create ipk package

Store the ascii armored pubkey generated using gpg_sign.export_pubkey() in its own package. Signed-off-by: Ioan-Adrian Ratiu --- meta/recipes-core/meta/signing-keys.bb | 15 ++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git

[OE-core] [PATCH v7 0/5] IPK signing for the gpg_sign module

This patch series extends the gpg_sign module to support ipk signing. Changes since v6: * Added pubkey to signing_keys.bb and rebased on top of Randy's work * Made gpg version detection logic more robust * Simplified detach_sign() gpg communication (no more os.pipe) Ioan-Adrian Ratiu (5):

[OE-core] [PATCH v7 2/5] gpg_sign: detach_sign: fix gpg > 2.1 STDIN file descriptor

Starting from v2.1 passing passwords directly to gpg does not work anymore [1], instead a loopback interface must be used otherwise gpg >2.1 will error out with: "gpg: signing failed: Inappropriate ioctl for device" gpg <2.1 does not work with the new --pinentry-mode arg and gives an invalid

Re: [OE-core] [PATCH 04/19] nspr: update to 4.12

On Wed, Mar 2, 2016 at 6:18 AM, Alexander Kanavin wrote: > On 03/01/2016 04:58 PM, Khem Raj wrote: > >>> The failing patch is applied only when musl is in use (and so the >>> regression >>> went unnoticed). Can you rework it so that it can be applied >>>

Re: [OE-core] [PATCH 04/19] nspr: update to 4.12

On 03/01/2016 04:58 PM, Khem Raj wrote: The failing patch is applied only when musl is in use (and so the regression went unnoticed). Can you rework it so that it can be applied unconditionally? This probably could be however OE-Core supports musl and poky-tiny defaults to it. It will be good

Re: [OE-core] [PATCH][RFC] base.bbclass: Introduce EXTRA_CONF_PACKAGECONFIG variable

On Wed, Mar 02, 2016 at 01:11:45PM +, Richard Purdie wrote: > On Wed, 2016-03-02 at 13:38 +0100, Martin Jansa wrote: > > On Sat, Feb 27, 2016 at 11:09:47PM +0100, Martin Jansa wrote: > > > * add separate variable for configuration options generated from > > > PACKAGECONFIG setting, this

Re: [OE-core] [PATCH][RFC] base.bbclass: Introduce EXTRA_CONF_PACKAGECONFIG variable

On Wed, 2016-03-02 at 13:38 +0100, Martin Jansa wrote: > On Sat, Feb 27, 2016 at 11:09:47PM +0100, Martin Jansa wrote: > > * add separate variable for configuration options generated from > > PACKAGECONFIG setting, this helps other bbclasses and recipes > > to take advantage of PACKAGECONFIG

Re: [OE-core] [PATCH][RFC] base.bbclass: Introduce EXTRA_CONF_PACKAGECONFIG variable

On 27 February 2016 at 22:09, Martin Jansa wrote: > * add separate variable for configuration options generated from > PACKAGECONFIG setting, this helps other bbclasses and recipes > to take advantage of PACKAGECONFIG mechanism, without including > other options

Re: [OE-core] [PATCH][RFC] base.bbclass: Introduce EXTRA_CONF_PACKAGECONFIG variable

On Sat, Feb 27, 2016 at 11:09:47PM +0100, Martin Jansa wrote: > * add separate variable for configuration options generated from > PACKAGECONFIG setting, this helps other bbclasses and recipes > to take advantage of PACKAGECONFIG mechanism, without including > other options from EXTRA_OECONF

Re: [OE-core] [PATCH] packagegroup-core-tools-profile: Enable valgrind on ARM

On 15/02/16 12:37, Burton, Ross wrote: > On 13 February 2016 at 04:31, Andre McCurdy > wrote: > > $ cd openembedded-core > $ git show af1ddab5c > fatal: ambiguous argument 'af1ddab5c': unknown revision or path not in > the

Re: [OE-core] [PATCH] packagegroup-core-tools-profile: Enable valgrind on ARM

Hi Ross, On 15/02/16 12:37, Burton, Ross wrote: > On 13 February 2016 at 04:31, Andre McCurdy > wrote: > > $ cd openembedded-core > $ git show af1ddab5c > fatal: ambiguous argument 'af1ddab5c': unknown revision or path not in >

[OE-core] [PATCH 0/3] Extensible SDK improvements

Add ability to build derivative extensible SDK and fix up an issue with the earlier patch introducing oe-workdir and oe-logs symlinks. The following changes since commit 390bad905537820f49add855c95d726b5b55c8fa: sanity: Fix int verses string reference (2016-02-28 22:54:06 +) are

[OE-core] [PATCH 2/3] devtool: build-image: rename module

Hyphens aren't allowed in python identifiers, so you shouldn't use them in module names or they are more difficult to import. Signed-off-by: Paul Eggleton --- scripts/lib/devtool/{build-image.py => build_image.py} | 0 1 file changed, 0 insertions(+), 0

[OE-core] [PATCH 1/3] classes/externalsrc: fix symlinking if symlink exists pointing to another path

If the oe-workdir / oe-logs symlink exists and points to a different path then the symlink needs to be removed before calling os.symlink() or it'll fail. Signed-off-by: Paul Eggleton --- meta/classes/externalsrc.bbclass | 1 + 1 file changed, 1 insertion(+) diff

[OE-core] [PATCH 3/3] devtool: add build-sdk subcommand

Add a build-sdk command which is only available within the extensible SDK that builds a derivative extensible SDK. The idea is recipes in the workspace become a part of the new SDK - for example, this allows taking a vendor provided SDK, adding a few libs and then producing a new SDK with those

Re: [OE-core] [PATCHv2] Add tune for 32-bit ARMv8-a

Hi Andrei, On 03/02/2016 02:17 AM, Andrei Gherzan wrote: Hi Daniel, On Sat, Feb 27, 2016 at 1:44 PM, Daniel Dragomir > wrote: This patch adds tunes for 32-bit armv8 platforms. The user can select the vector

Re: [OE-core] [PATCHv2] Add tune for 32-bit ARMv8-a

On 03/01/2016 09:12 PM, Andre McCurdy wrote: On Tue, Mar 1, 2016 at 8:33 AM, Dragomir Daniel wrote: On 03/01/2016 02:02 AM, Andre McCurdy wrote: On Sat, Feb 27, 2016 at 4:44 AM, Daniel Dragomir wrote: This patch adds tunes for

[OE-core] [meta-intel][master][jethro][PATCH 1/1] tune-corei7.inc: Fix PACKAGE_EXTRA_ARCHS for corei7-32

From: Chang Rebecca Swee Fun Change the name to core2-32 from core2. There's no AVAILTUNES with the name core2. Make sure that we specify the correct TUNE name so PACKAGE_EXTRA_ARCHS is expanded correctly. [ YOCTO #9197 ] Signed-off-by: Chang Rebecca Swee Fun

[OE-core] [meta-intel][master][jethro][PATCH 0/1] Fix tune name in tune-corei7.inc

There's no AVAILTUNES with the name "core2" while tune-corei7.inc seems to have a reference to it. $ grep -r core2 tune-corei7.inc require conf/machine/include/tune-core2.inc PACKAGE_EXTRA_ARCHS_tune-corei7-32 = "${PACKAGE_EXTRA_ARCHS_tune-core2} corei7-32" $ grep -r AVAILTUNES tune-core2.inc

Re: [OE-core] How to integrate third party application software to yocto image

Hi, I am new to this community.What does mean top post? Please see my bblayers.conf file content. # LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf # changes incompatibly LCONF_VERSION = "6" BBPATH = "${TOPDIR}" BBFILES ?= "" BBLAYERS ?= " \ /home/winiston/poky/meta \