[OE-core] [PATCH] gcc-6: Sync gcc stddef.h with musl stddef.h

GCC provides some of std* headers including stddef.h and it syncs with glibc definitions via __needed* defines to find which datatypes are expected to be defined on top of glibc. we need same for musl. Drop unused 0048-ARM-PR-target-71056-Don-t-use-vectorized-builtins-wh.patch Signed-off-by:

Re: [OE-core] whatever happened to a proposal for "read-only" sstate?

On Fri, 2017-02-03 at 16:24 -0500, Robert P. J. Day wrote: > On Fri, 3 Feb 2017, Patrick Ohly wrote: > > > On Fri, 2017-02-03 at 14:14 -0500, Robert P. J. Day wrote: > > > is there a command that will tell you how much shared state info a > > > given build would be able to take advantage of? >

Re: [OE-core] whatever happened to a proposal for "read-only" sstate?

On Fri, 3 Feb 2017, Patrick Ohly wrote: > On Fri, 2017-02-03 at 14:14 -0500, Robert P. J. Day wrote: > > is there a command that will tell you how much shared state info a > > given build would be able to take advantage of? > > INHERIT += "buildstats-summary" in local.conf will print that >

Re: [OE-core] whatever happened to a proposal for "read-only" sstate?

On Fri, 2017-02-03 at 14:14 -0500, Robert P. J. Day wrote: > is there a command that will tell you how much shared state info a > given build would be able to take advantage of? INHERIT += "buildstats-summary" in local.conf will print that information after a build is done. -- Best Regards,

[OE-core] [PATCH] wic: flatten imager class hierarchy

wic code is hard to follow due to deep and twiggy class inheritance tree. Flatten imager tree: wic -> wic_create -> Creator -> DirectPlugin -> DirectImageCreator to wic -> wic_create -> DirectPlugin by removing Creator class and creator module merging DirectImageCreator into DirectPlugin

Re: [OE-core] whatever happened to a proposal for "read-only" sstate?

On Fri, 3 Feb 2017, Richard Purdie wrote: > On Fri, 2017-02-03 at 06:45 -0500, Robert P. J. Day wrote: > >   for purposes of teaching, i wanted to check into the feasibility of > > having students take advantage of a single shared state cache, but > > still have the option of building whatever

Re: [OE-core] [PATCH] [RFC]kernel-yocto.bbclass: ensure repatching when HEAD is checked out

Here's the patch that I came up with based on your change. The only difference is that I modified the patching script to have a --clean option .. and used that instead. That way we keep the internals hidden. If this works for you, I can send it in my next kernel pull request. Bruce On Fri, Feb

[OE-core] [PATCH] wic: fix call of serial_console_form_kargs

As syslinux module has been recently removed and serial_consloe_form_kargs became local API in rootfs_pcbios_ext plugin it should be called without syslinux. prefix. Signed-off-by: Ed Bartosh --- scripts/lib/wic/plugins/source/rootfs_pcbios_ext.py | 2 +- 1 file

[OE-core] [PATCH] selftest: wic: stop using iso image type

Removed 'IMAGE_FSTYPES = "iso" as this functionality depends on do_bootimg, which is going to be obsoleted soon. As wic doesn't depend on bootimg it's safe to remove this. Signed-off-by: Ed Bartosh --- meta/lib/oeqa/selftest/wic.py | 6 +++--- 1 file changed, 3

Re: [OE-core] Want to strip rootfs

On 2/3/17 6:25 AM, ANDANI PRASHANT wrote: > Hi, > > I build rootfs which size is 100MB+ > As i look in to filesystem, there are 14mb libc-2.23.so , > 12mb libstdc++.so.6.0.22,..etc. > Is there any flag or option during build to strip all library and binary to > optimise size

[OE-core] [PATCH] selftest: wic: use wic-tools recipe to get STAGING_DIR

STAGING_DIR variable is used to get path to a boot dir. It's better to use wic-tools recipe to it as it contains all bootloader artifacts. Modified test_build_artifacts and test_rootfs_artifacts to use wic-tools target to get STAGING_DIR. Signed-off-by: Ed Bartosh

Re: [OE-core] whatever happened to a proposal for "read-only" sstate?

On Fri, 3 Feb 2017, Richard Purdie wrote: > On Fri, 2017-02-03 at 06:45 -0500, Robert P. J. Day wrote: > >   for purposes of teaching, i wanted to check into the feasibility of > > having students take advantage of a single shared state cache, but > > still have the option of building whatever

Re: [OE-core] whatever happened to a proposal for "read-only" sstate?

On Fri, 2017-02-03 at 06:45 -0500, Robert P. J. Day wrote: >   for purposes of teaching, i wanted to check into the feasibility of > having students take advantage of a single shared state cache, but > still have the option of building whatever source they needed in > their > own *personal* sstate

Re: [OE-core] [PATCH] [RFC]kernel-yocto.bbclass: ensure repatching when HEAD is checked out

On Fri, Feb 3, 2017 at 5:49 AM, Awais Belal wrote: > In some cases it is seen that kernel_checkout and > validate_branches are run again in simultaneous builds. > During do_patch the kgit-s2q mechanism creates and > checks for the kgit-s2q.last file inside the .git >

[OE-core] [PATCH] wic: isoimage-isohybrid: use wic-tools to get syslinux path

wic-tools recipe specific sysroot contains syslinux as wic-tools depends on it. Used wic-tools target to get syslinux path should guarantee that syslinux is installed there and can be used. Signed-off-by: Ed Bartosh ---

Re: [OE-core] [PATCH 4/4] libgcrypt.inc: Enable use of binconfig

On 3 February 2017 at 00:17, Burton, Ross wrote: > > On 30 January 2017 at 07:47, Nathan Rossi wrote: >> >> Due to pkg-config support for libgcrypt being un-available for upstream >> libgcrypt, some packages that depend on libgcrypt rely on the use

Re: [OE-core] RSS difficulties

On Fri, 2017-02-03 at 11:20 +, Richard Purdie wrote: > > It comes down to what setscene_depvalid() in sstate.bbclass returns. > If > that returns False a given dependency is installed, it if returns > True, > it is skipped and not installed. > > Reading that function should give some clues

[OE-core] Want to strip rootfs

Hi, I build rootfs which size is 100MB+ As i look in to filesystem, there are 14mb libc-2.23.so, 12mb libstdc++.so.6.0.22,..etc. Is there any flag or option during build to strip all library and binary to optimise size of rootfs. Regards, Prashant --

Re: [OE-core] [PATCH] pulseaudio: 9.0 -> 10.0

On Fri, 2017-02-03 at 13:42 +0200, Alexander Kanavin wrote: > On 02/03/2017 09:06 AM, Tanu Kaskinen wrote: > > > > Dropped json-c and gdbm from DEPENDS. The new release doesn't use json-c > > any more. gdbm isn't used when --with-database=simple is passed to > > configure, so it should have been

[OE-core] whatever happened to a proposal for "read-only" sstate?

for purposes of teaching, i wanted to check into the feasibility of having students take advantage of a single shared state cache, but still have the option of building whatever source they needed in their own *personal* sstate cache. i found this reference from 2014:

Re: [OE-core] [PATCH] pulseaudio: 9.0 -> 10.0

On 02/03/2017 09:06 AM, Tanu Kaskinen wrote: Dropped json-c and gdbm from DEPENDS. The new release doesn't use json-c any more. gdbm isn't used when --with-database=simple is passed to configure, so it should have been removed from DEPENDS a long time ago. Does anything else in oe-core still

Re: [OE-core] RSS difficulties

On Fri, 2017-02-03 at 11:10 +, Phil Blundell wrote: > I'm having a few problems adapting our build setup to work with > recipe specific sysroots.  More specifically, I am finding it > difficult to get the correct set of components installed into the > recipe-sysroot in all cases.  In some

[OE-core] RSS difficulties

I'm having a few problems adapting our build setup to work with recipe specific sysroots. More specifically, I am finding it difficult to get the correct set of components installed into the recipe-sysroot in all cases. In some cases I am getting too much (which causes build failures if oe

[OE-core] [PATCH] [RFC]kernel-yocto.bbclass: ensure repatching when HEAD is checked out

In some cases it is seen that kernel_checkout and validate_branches are run again in simultaneous builds. During do_patch the kgit-s2q mechanism creates and checks for the kgit-s2q.last file inside the .git directory, finds a fence post and starts picking up patches after that. This can create

[OE-core] [PATCH 2/2] oeqa/buildproject: Run gnu-configize by default

The runtime oeqa tests were failing in the on-target case, only for aarch64. This was because an old config.sub was being used. Similar to the SDK testing, call gnu-configize in the on-target case too to resolve the failing tests. Signed-off-by: Richard Purdie

[OE-core] [PATCH 1/2] oeqa/runtime: Improve failure log output

Printing a message which says "configure failed" without the log output is effectively useless. If a command fails, print the output by default and simplify the calling code which makes debugging any of these failures much easier. Signed-off-by: Richard Purdie

[OE-core] [PATCH] oeqa.buildperf: reword test descriptions

In an attempt to make them more compact and coherent. Signed-off-by: Markus Lehtonen --- meta/lib/oeqa/buildperf/test_basic.py | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/meta/lib/oeqa/buildperf/test_basic.py