[OE-core] [RESEND PATCH v3 2/2] package_manager: support for signed IPK package feeds

Create gpg signed package feeds if configured. Very similar to how rpm does it. Most of the config variables are shared with the rpm backend (like PACKAGE_FEED_GPG_NAME), with the exception of PACKAGE_FEED_GPG_PUBKEY which is not needed in this case. Signed-off-by: Ioan-Adrian Ratiu

Re: [OE-core] [RESEND PATCH] x11vnc: move recipe to meta-oe

On Fri, 11 Dec 2015 17:09:21 +0200 Ioan-Adrian Ratiu wrote: > On Thu, 3 Dec 2015 14:18:53 + > "Burton, Ross" wrote: > > > On 3 December 2015 at 10:17, Ioan-Adrian Ratiu wrote: > > > > > x11vnc can be configured with

[OE-core] [PATCH v2 1/2] boost: ensure boost to remain an empty metapackage

To ensure that boost remains an empty metapackage after version updates, we explicitly require boost files to be empty. If new libraries exist after a version update of the boost recipe, bitbake will emit a warning at the do_package task. For example, at the version update from 1.58.0 to 1.59.0,

[OE-core] [RESEND PATCH v3 1/2] package_ipk: support signing of ipk packages

Minimum required opkg version: 3.0 (already in master/jethro). Add a new bbclass for creating signatures for ipk files. The signing process is very similar to the existing rpm signing, but different in some important ways: - Signatures are stored outside the ipk files, opkg connects to a feed

[OE-core] [PATCH v2 2/2] boost: update to 1.60.0

Due to the version update to 1.59.0, the two patches previously backported in this recipe are now dropped. The actual status of the arm-intrinsics.patch (reported with Upstream-Status: Backport) is unknown to the committer, and hence, that patch is kept in the recipe, even if it is possibly not

[OE-core] [PATCH] selftest: Added testcase decorators for 2 tests

1391 for test_devtool_add_fetch_simple from devtool 1392 for test_recipetool_create_simple from recipetool Signed-off-by: Daniel Istrate --- meta/lib/oeqa/selftest/devtool.py| 1 + meta/lib/oeqa/selftest/recipetool.py | 1 + 2 files changed, 2

Re: [OE-core] [PATCH 1/1] linux-firmware: remove hard-coded paths

On 01/05/2016 03:26 AM, Matthias Schiffer wrote: > On 01/05/2016 01:28 AM, Mark Hatle wrote: >> On 1/4/16 5:57 PM, Matthias Schiffer wrote: >>> On 01/04/2016 11:56 PM, Mark Hatle wrote: On 1/4/16 4:26 PM, Matthias Schiffer wrote: > On 01/04/2016 05:32 PM, Mark Hatle wrote: >> On

Re: [OE-core] [PATCH v2] bluez5: upgrade to 5.37

On Tue, Jan 05, 2016 at 06:34:13PM +0200, Maxin B. John wrote: > 5.36 -> 5.37 > > Remove the backported patch: > core-profile-Fix-possible-crash-when-registering-pro.patch > > Blacklist bluez5 only recipes when bluez4 is in DISTRO_FEATURES LGTM thanks signature.asc Description: Digital

Re: [OE-core] [PATCH 1/1] linux-firmware: remove hard-coded paths

On 1/5/16 8:41 AM, Ray, Ian (GE Healthcare) wrote: > On 01/05/2016 4:33 PM, Mark Hatle wrote: >> On 1/5/16 8:04 AM, Ray, Ian (GE Healthcare) wrote: >>> On 01/05/2016 03:26 AM, Matthias Schiffer wrote: On 01/05/2016 01:28 AM, Mark Hatle wrote: > On 1/4/16 5:57 PM, Matthias Schiffer wrote:

Re: [OE-core] [PATCH v2] bluez5: upgrade to 5.37

Just a quick question regarding this: On 05/01/16 17:34, Maxin B. John wrote: > +PNBLACKLIST[bluez5] ?= "${@bb.utils.contains('DISTRO_FEATURES', 'bluez4', > 'bluez5 conflicts with bluez4 and bluez4 is selected in DISTRO_FEATURES', '', > d)}" Is 'bluez4' a user's custom distro feature, because

[OE-core] [PATCH] image: Remove pointless rootfs lock

It was added in aa3141e979326a9d931ff03bad75923faa1d9dc6 back in 2008 but I don't see why multiple images would need this now. Signed-off-by: Richard Purdie diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass index d2f8105..8242c56 100644 ---

Re: [OE-core] [oe] [RFT] glibc 2.23

On 4 January 2016 at 19:00, Khem Raj wrote: > I have done OE-Core only clean world builds for all Qemu machines > without a single build failure and > runtime boot tested. > I threw this at the autobuilder and glibc failed to build on one of the runs:

Re: [OE-core] [PATCH v2 2/2] boost: update to 1.60.0

On 5 January 2016 at 09:32, Lukas Bulwahn wrote: > Due to the version update to 1.59.0, the two patches previously > backported in this recipe are now dropped. The actual status of > the arm-intrinsics.patch (reported with Upstream-Status: Backport) > is unknown

Re: [OE-core] [PATCH v2 0/3] Debian multilib packaging fixes

On Mon, Jan 4, 2016 at 12:56 PM, Aníbal Limón wrote: > Hi Matt, > > Sorry for the delay in the response, i'll test again your patches with > the new one and the same error appears when build > core-image-full-cmdline or core-image-sato. No problem, I figured things

[OE-core] [PATCH v2] bluez5: upgrade to 5.37

5.36 -> 5.37 Remove the backported patch: core-profile-Fix-possible-crash-when-registering-pro.patch Blacklist bluez5 only recipes when bluez4 is in DISTRO_FEATURES Signed-off-by: Maxin B. John --- ...e-Fix-possible-crash-when-registering-pro.patch | 54

[OE-core] [PATCH RESEND] udev-extraconf: introduce multiple blacklist files for more complex setups

In cases where a target image wants prevent the recovery partition is mounted automatically, but the recovery partition identifier moves with the device (internal flash, sd card, usb stick, ...), device/machine dependend extra blacklists might be desired. The grep utility prints the file name

Re: [OE-core] [PATCH v2] bluez5: upgrade to 5.37

On 5 January 2016 at 17:19, Javier Viguera wrote: > Is 'bluez4' a user's custom distro feature, because it doesn't seem to be > part of the standard distro features. What poky.git at current master has > is 'bluetooth' and 'bluez5' as distro features and those are used

Re: [OE-core] [PATCH] valgrind: update to 3.11.0

On 15 December 2015 at 15:02, Alexander Kanavin < alexander.kana...@linux.intel.com> wrote: > LICENSE checksums are changed due to a change in FSF address, or copyright > years update. > > Rebased patches: > sepbuildfix.patch rebased to 0004-Fix-out-of-tree-builds.patch > add-ptest.patch rebased

Re: [OE-core] [PATCH 1/1] linux-firmware: remove hard-coded paths

On 1/4/16 7:26 PM, Matthias Schiffer wrote: > On 01/05/2016 01:28 AM, Mark Hatle wrote: >> On 1/4/16 5:57 PM, Matthias Schiffer wrote: >>> On 01/04/2016 11:56 PM, Mark Hatle wrote: On 1/4/16 4:26 PM, Matthias Schiffer wrote: > On 01/04/2016 05:32 PM, Mark Hatle wrote: >> On 1/4/16

Re: [OE-core] [PATCH v2 2/2] x11vnc: remove all references to moved package

On 5 January 2016 at 14:22, Ioan-Adrian Ratiu wrote: > Yes and also if there are no x11 dependencies in this packagegroup, > then it should be renamed to packagegroup-core-sato. > > I'll resubmit. Thank you. > Don't - sato is explicitly X11 based. Ross --

Re: [OE-core] [PATCH 1/2] bluez5: upgrade to 5.37

Hi Martin, On Tue, Jan 05, 2016 at 04:01:24PM +0100, Martin Jansa wrote: > On Tue, Jan 05, 2016 at 04:08:13PM +0200, Maxin B. John wrote: > > 5.36 -> 5.37 > > > > Remove the backported patch: > > core-profile-Fix-possible-crash-when-registering-pro.patch > Don't you need to remove >

Re: [OE-core] [PATCH v2 2/2] x11vnc: remove all references to moved package

On 5 January 2016 at 15:25, Ioan-Adrian Ratiu wrote: > Just one more question: When you say don't are you referring only to the > image rename or also to the removal of the distro feature check? > Both. Don't rename the packagegroup, don't remove the check. Ross --

[OE-core] [PATCH] udev-extraconf: introduce multiple blacklist files for more complex setups

In cases where a target image wants prevent the recovery partition is mounted automatically, but the recovery partition identifier moves with the device (internal flash, sd card, usb stick, ...), device/machine dependend extra blacklists might be desired. The grep utility prints the file name

Re: [OE-core] [PATCH] udev-extraconf: introduce multiple blacklist files for more complex setups

Hi Jens, On 5 January 2016 at 13:58, Jens Rehsack wrote: > In cases where a target image wants prevent the recovery partition is > mounted > automatically, but the recovery partition identifier moves with the device > (internal flash, sd card, usb stick, ...), device/machine

Re: [OE-core] [PATCH v2 2/2] x11vnc: remove all references to moved package

On Tue, Jan 05, 2016 at 02:24:23PM +0200, Ioan-Adrian Ratiu wrote: > Together with the move to meta-oe, all references to x11vnc should be > removed from oe-core. There are three of these: a distro alias, a > packagegroup rdepends and a runtime test. > > Signed-off-by: Ioan-Adrian Ratiu

Re: [OE-core] [PATCH V1 1/3] kernel.bbclass: do not install initramfs bundled kernel image

Hi, Bruce: I had sent out another 0/N thread as you requested, please ignore this thread then. the best, thank you 2016-01-04 15:58 GMT+01:00 Bruce Ashfield : > On 15-12-30 04:19 PM, Ming Liu wrote: > >> From: Ming Liu >> >>

Re: [OE-core] [PATCH v2 2/2] x11vnc: remove all references to moved package

On Tue, 5 Jan 2016 14:31:19 + "Burton, Ross" wrote: > On 5 January 2016 at 14:22, Ioan-Adrian Ratiu wrote: > > > Yes and also if there are no x11 dependencies in this packagegroup, > > then it should be renamed to packagegroup-core-sato. > > > >

[OE-core] [PATCH] uclibc: disable parallel builds

There appears to be a parallel make race in uclibc: GEN /extra/locale/locale_collate.h xargs: ../..//extra/locale/gen_collate: Text file busy make[1]: *** [../..//extra/locale/locale_collate.h] Error 126 As uclibc is slated to be removed in the 2.1 cycle let's just disable parallel building

Re: [OE-core] [PATCH 1/2] bluez5: upgrade to 5.37

On Tue, Jan 05, 2016 at 04:08:13PM +0200, Maxin B. John wrote: > 5.36 -> 5.37 > > Remove the backported patch: > core-profile-Fix-possible-crash-when-registering-pro.patch Don't you need to remove file://core-profile-Fix-possible-crash-when-registering-pro.patch from SRC_URI when you're removing

[OE-core] [PATCH] orc: Add missing PACKAGES_DYNAMIC

Recipes should always indicate the packages they build, this corresponds to the do_split_packages() call. Signed-off-by: Richard Purdie diff --git a/meta/recipes-devtools/orc/orc_0.4.24.bb b/meta/recipes-devtools/orc/orc_0.4.24.bb index 4fa311f..9e70d55

[OE-core] [PATCH 2/2] connman: upgrade to 1.31

1.30 -> 1.31 Signed-off-by: Maxin B. John --- .../recipes-connectivity/connman/{connman_1.30.bb => connman_1.31.bb} | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) rename meta/recipes-connectivity/connman/{connman_1.30.bb => connman_1.31.bb} (77%) diff --git

[OE-core] [PATCH 1/2] bluez5: upgrade to 5.37

5.36 -> 5.37 Remove the backported patch: core-profile-Fix-possible-crash-when-registering-pro.patch Signed-off-by: Maxin B. John --- ...e-Fix-possible-crash-when-registering-pro.patch | 54 -- .../bluez5/{bluez5_5.36.bb => bluez5_5.37.bb} | 5 +-

Re: [OE-core] [PATCH 1/1] linux-firmware: remove hard-coded paths

On 1/5/16 8:04 AM, Ray, Ian (GE Healthcare) wrote: > On 01/05/2016 03:26 AM, Matthias Schiffer wrote: >> On 01/05/2016 01:28 AM, Mark Hatle wrote: >>> On 1/4/16 5:57 PM, Matthias Schiffer wrote: On 01/04/2016 11:56 PM, Mark Hatle wrote: > On 1/4/16 4:26 PM, Matthias Schiffer wrote: >>

Re: [OE-core] [PATCH v2 2/2] x11vnc: remove all references to moved package

On Tue, 5 Jan 2016 14:31:19 + "Burton, Ross" wrote: > On 5 January 2016 at 14:22, Ioan-Adrian Ratiu wrote: > > > Yes and also if there are no x11 dependencies in this packagegroup, > > then it should be renamed to packagegroup-core-sato. > > > >

Re: [OE-core] [PATCH v2 2/2] x11vnc: remove all references to moved package

On Tue, 5 Jan 2016 14:41:50 +0100 Martin Jansa wrote: > On Tue, Jan 05, 2016 at 02:24:23PM +0200, Ioan-Adrian Ratiu wrote: > > Together with the move to meta-oe, all references to x11vnc should be > > removed from oe-core. There are three of these: a distro alias, a > >

Re: [OE-core] [PATCH 1/1] linux-firmware: remove hard-coded paths

On 01/05/2016 4:33 PM, Mark Hatle wrote: > On 1/5/16 8:04 AM, Ray, Ian (GE Healthcare) wrote: >> On 01/05/2016 03:26 AM, Matthias Schiffer wrote: >>> On 01/05/2016 01:28 AM, Mark Hatle wrote: On 1/4/16 5:57 PM, Matthias Schiffer wrote: > On 01/04/2016 11:56 PM, Mark Hatle wrote: >> On

[OE-core] [PATCHv5] scripts/oe-selftest: Allow to run tests on random/all MACHINEs

Add an option for random MACHINE into oe-selftest: --machine [random/all] 1. random: will set a random MACHINE for each test 2. all: will run tests for all machines Custom machine sets only weak default values (??=) for MACHINE in machine.inc. This let test cases that require a specific MACHINE

Re: [OE-core] [PATCH] sstate: change "stamp is not reachable, removing manifests" message from info to debug

On 01/05/16 07:32, Ross Burton wrote: > This code path has proven to work, so change the log level from info to debug > so > it doesn't spam the log in normal use. I liked having this as part of the regular processing. If I only update my upstream repositories once a week (for example) my next

[OE-core] [PATCH v2] tzdata: Make /etc/timezone optional

Add INSTALL_TIMEZONE_FILE config variable to enable/disable installation of ${sysconfdir}/timezone (/etc/timezone) by tzdata packages. Defaults to "1" to maintain previous behavior. Most libc implementations can be configured to retrieve system's defaults timezone from /etc/localtime, and don't

Re: [OE-core] [PATCH 0/4] Misc improvements 2 from Mentor

On Thu, Nov 12, 2015 at 4:41 PM, Christopher Larson wrote: > From: Christopher Larson > > This is the final of three pull requests / patch series from Mentor's > queue of > changes destined for oe-core master (not jethro). This series includes a >

[OE-core] [PATCH] image/rootfs-postcommands: Separate out post rootfs commands to separate class

Reading image.bbclass is a little difficult as it has many post rootfs helper functions and its hard to separate those from the core contents of the rootfs/image code. Moving it to a separate class would be one way of making it clearer what these functions are. There are some comment layout

[OE-core] [PATCH] image: Condense do_rootfs function/flags

Various prefuncs and flags and addtask statements make sense to belong together in one clearer function now, this patch cleans things up a bit. Signed-off-by: Richard Purdie diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass index

Re: [OE-core] [PATCH] tzdata: Make /etc/timezone optional

On 01/05/2016 07:03 AM, Burton, Ross wrote: On 23 December 2015 at 23:51, Haris Okanovic > wrote: +CONFFILES_${PN} += "${@['','${sysconfdir}/timezone'][d.getVar('INSTALL_TIMEZONE_FILE', True) == '1']}" This idiom (indexing an

[OE-core] [PATCH] Fix connectivity check for BB_FETCH_PREMIRRORONLY case

From: Jan-Simon Möller BB_FETCH_PREMIRRORONLY sets BB_NO_NETWORK (implicitly in the fetcher). To avoid the sanity check to fail in an offline environment, use the same override mechanism as in the fetcher. Signed-off-by: Jan-Simon Möller ---

Re: [OE-core] [PATCH 0/4] Misc improvements 2 from Mentor

On 5 January 2016 at 19:08, Christopher Larson wrote: > Any objections to this series? > Slipped through the net, thanks for the ping. They look good to me, in mut now. Ross -- ___ Openembedded-core mailing list

Re: [OE-core] [PATCH 2/2] connman: upgrade to 1.31

On 5 January 2016 at 14:08, Maxin B. John wrote: > 1.30 -> 1.31 > I saw this on one of my builds locally: ERROR: QA Issue: connman: Files/directories were installed but not shipped in any package: /lib/systemd/system/connman-wait-online.service /usr/lib/tmpfiles.d

[OE-core] [PATCH] [master, jethro] Fix connectivity check for BB_FETCH_PREMIRRORONLY case

Hi! This patch fixes a bug in the sanity checker that is visible if you set up a PREMIRROR and start a project from scratch using BB_FETCH_PREMIRRORONLY set. In this case the sanity check would fail as BB_NO_NETWORK is not set directly (just indirectly in the fetcher by BB_FETCH_PREMIRRORONLY).

Re: [OE-core] [PATCH] gcc5: Fix build on NIOS2

> On Jan 5, 2016, at 6:13 PM, Marek Vasut wrote: > > The gcc 5.3 does not build on NIOS2 due to a missing MUSL_DYNAMIC_LINKER > definition in it's config file. Add the definition to fix the build issue. > The output produced during the failing build is as follows: > > g++

Re: [OE-core] [oe] [RFT] glibc 2.23

> On Jan 5, 2016, at 4:01 PM, Paul Eggleton > wrote: > > On Tue, 05 Jan 2016 13:08:31 Khem Raj wrote: >>> On Jan 5, 2016, at 8:17 AM, Burton, Ross wrote: >>> >>> On 4 January 2016 at 19:00, Khem Raj wrote: I have

Re: [OE-core] [PATCH 1/1] Revert "glib-2.0: build dependency cleanup"

On 2016年01月04日 18:47, Burton, Ross wrote: On 29 December 2015 at 09:43, > wrote: This reverts commit fcd7494b347423185c883b2897c4908929843a71. Why revert? Just adding glib-2.0-native to DEPENDS is sufficient, no need to revert

Re: [OE-core] [PATCH v2 3/3] base-files: create typical merged /usr symlinks if the "merged-usr" distro feature is set

On Mon, 2016-01-04 at 23:38 +0100, Matthias Schiffer wrote: > Of course, the alternative would be to force such distros to > override the bases-files recipe in a .bbappend. I don't think this would be an especially big deal. The whole contents of base-files is already fairly distro-specific and

Re: [OE-core] [PATCH 1/1] linux-firmware: remove hard-coded paths

On Tue, 2016-01-05 at 11:06 -0600, Mark Hatle wrote: > This is a situation where we've got hard coded '/lib' entries in FILES, but > we're trying to move the directory elsewhere 'adjusting' FILES > automatically > is probably more error prone and complicated then desired.. but I'm not sure >

Re: [OE-core] [RESEND PATCH] x11vnc: move recipe to meta-oe

Hi, On 5 January 2016 at 08:46, Ioan-Adrian Ratiu wrote: > ping? anyone? The x11vnc recipe is in meta-oe master since 18 dec > Can you rebase to master and actually remove all the other references to x11vnc? For example, packagegroup-core-x11-sato still depends on x11vnc.

Re: [OE-core] [RESEND PATCH] x11vnc: move recipe to meta-oe

On Tue, 5 Jan 2016 11:16:06 + "Burton, Ross" wrote: > Hi, > > On 5 January 2016 at 08:46, Ioan-Adrian Ratiu wrote: > > > ping? anyone? The x11vnc recipe is in meta-oe master since 18 dec > > > > Can you rebase to master and actually remove all

Re: [OE-core] [oe] [RFT] glibc 2.23

> On Jan 5, 2016, at 8:17 AM, Burton, Ross wrote: > > On 4 January 2016 at 19:00, Khem Raj wrote: > >> I have done OE-Core only clean world builds for all Qemu machines >> without a single build failure and >> runtime boot tested. >> > > I threw

Re: [OE-core] [PATCH 2/2] systemd: add more compression and importd PACKAGECONFIGs

> On Jan 4, 2016, at 12:53 PM, Burton, Ross wrote: > > > On 4 January 2016 at 18:36, Khem Raj > wrote: > Would it thow some sensible configure errors on enabling importd > without the dependencies ? now that they are

Re: [OE-core] [oe-core] RFC: Split do_rootfs into image specific tasks?

Hi Richard, On Mon, 28 Dec 2015 13:00:40 Richard Purdie wrote: > I've heard complaints from people trying to create more interesting > image types about how hard it is to understand the rootfs/image > generation code and that its a pain to develop/test/debug. > > Having looked at it myself, the

Re: [OE-core] [PATCH] tzdata: Make /etc/timezone optional

On 23 December 2015 at 23:51, Haris Okanovic wrote: > +CONFFILES_${PN} += > "${@['','${sysconfdir}/timezone'][d.getVar('INSTALL_TIMEZONE_FILE', True) > == '1']}" > This idiom (indexing an array by a coerced boolean) is pretty difficult to read and bitbake has a helper

Re: [OE-core] korean/chinese keyboard layout support on yocto

On Dec 24, 2015 1:40 PM, "Bryan" wrote: > > On Dec 18, 2015 1:03 PM, "Bryan" wrote: > > > > Hi, > > I am working on yocto poky-dizzy 1.7.1 and have developed some > application on top of customized os image. I have a reqirement to support >

[OE-core] Fwd: korean/chinese keyboard layout support on yocto

-- Forwarded message -- From: "Bryan" Date: Dec 18, 2015 1:03 PM Subject: korean/chinese keyboard layout support on yocto To: Cc: Hi, I am working on yocto poky-dizzy 1.7.1 and have developed some application

[OE-core] [PATCH 0/3] Introduces kernel-initramfs recipe to resolve a implicit dependency issue

In current initramfs bundled kernel packaging policy, there are several dependency chains co-existing: | "core-image-minimal.do_build" -> "core-image-minimal.do_bundle_initramfs" | "core-image-minimal.do_bundle_initramfs" -> "virtual/kernel.do_bundle_initramfs" |

[OE-core] [PATCH 3/3] kernel-initramfs: new recipe, creates initramfs bundled kernel packaging

From: Ming Liu So far, there is not a workable way to package the initramfs bundled kernel image, the only place is tmp/deploy from where we could get it, but if a user want to add it into a certain image, there is no guarantee that he will achieve it because

[OE-core] [PATCH 2/3] image.bbclass: removes bundle_initramfs related code

From: Ming Liu The original purpose of these code is to repackage initramfs bundled kernel into rootfs by making image.bbclass build depend on bundle_initramfs of virtual/kernel. But this is not going to succeed because virtual/kernel's do_package is not

[OE-core] [PATCH 1/3] kernel.bbclass: do not install initramfs bundled kernel image

From: Ming Liu It makes no sense to install a initramfs bundled kernel image since do_package does not depend on do_bundle_initramfs at all, otherwise, it leads to a implicit kernel-image package depending on do_package run before or after

Re: [OE-core] [oe] [RFT] glibc 2.23

On Tue, 05 Jan 2016 13:08:31 Khem Raj wrote: > > On Jan 5, 2016, at 8:17 AM, Burton, Ross wrote: > > > > On 4 January 2016 at 19:00, Khem Raj wrote: > >> I have done OE-Core only clean world builds for all Qemu machines > >> without a single build

Re: [OE-core] [PATCH v3 0/3] ptest-runner 2.0

Hi Anibal, Please see my comments inline. Regards, Tudor. On 04/01/2016 20:29, Aníbal Limón wrote: > The whole set is sent to two ML for reviewing purposes the first > two patches are for oe-core and the last one for poky. > > The first two commits (oe-core) adds a new ptest-runner written in

Re: [OE-core] [PATCH v2 0/3] Debian multilib packaging fixes

Hi, I fixed the problem and add a 4 patch and sign-off your first tree patches also i tested your changes building images in machines: x86-64 (sato, minimal, multilib), x86(minimal), arm(minimal) and mips(minimal). Details below... Can you send the 4 patches again? alimon On 01/05/2016

[OE-core] [PATCH] sstate: change "stamp is not reachable, removing manifests" message from info to debug

This code path has proven to work, so change the log level from info to debug so it doesn't spam the log in normal use. Signed-off-by: Ross Burton --- meta/classes/sstate.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[OE-core] [PATCH v2 1/2] x11vnc: move recipe to meta-oe

x11vnc can be configured with --use-system-libvncserver to use an external libvncserver which will be added to meta-oe. Since oe-core should not depend on meta-oe, we move x11vnc there. Signed-off-by: Ioan-Adrian Ratiu --- .../recipes-graphics/x11vnc/files/endian-fix.patch

[OE-core] [PATCH v2 2/2] x11vnc: remove all references to moved package

Together with the move to meta-oe, all references to x11vnc should be removed from oe-core. There are three of these: a distro alias, a packagegroup rdepends and a runtime test. Signed-off-by: Ioan-Adrian Ratiu --- meta/conf/distro/include/distro_alias.inc| 1 -

[OE-core] [PATCH] strace: 4.10 -> 4.11

Update strace to 4.11 and remove patches which are now mainline. New patches: 0001-arc-metag-nios2-or1k-tile-fix-build.patch - backport from mainline to prevent build breakage on multiple arches. Updated patches: Makefile-ptest.patch strace-add-configure-options.patch Signed-off-by: Marek

[OE-core] [PATCH] gcc5: Fix build on NIOS2

The gcc 5.3 does not build on NIOS2 due to a missing MUSL_DYNAMIC_LINKER definition in it's config file. Add the definition to fix the build issue. The output produced during the failing build is as follows: g++-isystem/b/tmp/sysroots/x86_64-linux/usr/include -O2 -pipe -DIN_GCC