Re: [OE-core] [PATCH V2 1/8] populate_sdk_ext.bbclass: break the long lines

I'm not a big fan of those run-on lines either, so thanks. Some superficial comments: On Wed, Dec 14, 2016 at 8:24 AM, Robert Yang wrote: > Make it easier to read and maintain. > > [YOCTO #10647] > > Signed-off-by: Robert Yang > --- >

Re: [OE-core] migrating simple tarballs over to OE recipes?

On Wed, Nov 23, 2016 at 12:34 PM, Robert P. J. Day wrote: > On Wed, 23 Nov 2016, Burton, Ross wrote: > >> >> On 23 November 2016 at 10:42, Robert P. J. Day wrote: >> colleague has a pile of tarballs that were used to customize an x86 >>

[OE-core] [PATCH v2 1/1] package.bbclass: Remove unused variables and imports

Probably leftovers. Verified with a full core-image-sato build. For imports, I tried to find helper functions that might use an import from the parent function as well. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/package.bbclass | 13 + 1 file chan

[OE-core] [PATCH v2 0/1] Remove unused variables and imports from package.bbclass

Changes since v1: Remove accidentally omitted 's' variable too. Ulf Magnusson (1): package.bbclass: Remove unused variables and imports meta/classes/package.bbclass | 13 + 1 file changed, 1 insertion(+), 12 deletions(-) -- 2.7.4

[OE-core] [PATCH 1/1] package.bbclass: Remove unused variables and imports

Probably leftovers. Verified with a full core-image-sato build. For imports, I tried to find helper functions that might use an import from the parent function as well. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/package.bbclass | 11 --- 1 file chang

Re: [OE-core] [PATCH v3] package.py: New EXTRA_STRIPFLAGS variable

Hello, On Wed, Oct 26, 2016 at 8:51 AM, Michael Blättler wrote: > The EXTRA_STRIPFLAGS variable can be used to pass additional parameters to > the strip command. > This can be used to remove additional sections or to keep symbols. > The removal of additional

Re: [OE-core] [PATCH v2] package.py: New EXTRA_STRIPFLAGS variable

On Tue, Oct 25, 2016 at 1:18 PM, Ulf Magnusson <ulfali...@gmail.com> wrote: > On Tue, Oct 25, 2016 at 12:23 PM, Michael Blättler > <michael.blaett...@siemens.com> wrote: >> The EXTRA_STRIPFLAGS variable can be used to pass additional parameters to >> the stri

Re: [OE-core] Howto find the providing recipe for a specific package?

On Tue, Oct 25, 2016 at 1:03 PM, thilo.ceston...@ts.fujitsu.com wrote: > >> $ oe-pkgdata-util lookup-recipe kernel-module-xfrm6-mode-transport >> > Thanks! That is what I was looking for! > > Cheers, > Thilo > -- > ___ >

Re: [OE-core] [PATCH v2] package.py: New EXTRA_STRIPFLAGS variable

On Tue, Oct 25, 2016 at 12:23 PM, Michael Blättler wrote: > The EXTRA_STRIPFLAGS variable can be used to pass additional parameters to > the strip command. > This can be used to remove additional sections or to keep symbols. > The removal of additional sections can

Re: [OE-core] in what recipe context can "bb" show me TOOLCHAIN_HOST_TASK?

Hello, On Sat, Oct 22, 2016 at 9:39 AM, Robert P. J. Day wrote: > > a question about chris larson's nifty "bb" utility ... i recently > figured out that, to get rpm-build into the SDK, i needed to add: > > TOOLCHAIN_HOST_TASK += "nativesdk-rpm-build" > > to my

[OE-core] [PATCH 1/1] task-time: Add simple buildstats analysis script

0m2.772s 20161005225856/gettext-0.19.8.1-r0/do_compile: real 0m41.520s user 2m17.312s sys 0m7.536s Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- scripts/task-time | 132 ++ 1 file changed, 132 insertions(+) create mode 100755 s

[OE-core] [PATCH 0/1] Add 'task-time' buildstats helper script

If this goes in, I could also submit some documentation to the manuals. I suspect many people don't use the buildstats since getting useful information out of them is a bit of work. Ulf Magnusson (1): task-time: Add simple buildstats analysis script scripts/task-time | 132

Re: [OE-core] Two kmeta's not allowed for master?

On Tue, Oct 18, 2016 at 2:56 PM, Vesa Jääskeläinen wrote: > On 2016-10-11 16:38, Nathan Rossi wrote: >> >> On Tue, Oct 11, 2016 at 11:15 PM, wrote: >>> >>> Hi, >>> >>> I was trying out how well 'master' branch compiles in our

Re: [OE-core] [PATCH v2] bitbake: bitbake-layers: Make show-recipes show PR

On Mon, Oct 17, 2016 at 11:42 PM, Paul Eggleton <paul.eggle...@linux.intel.com> wrote: > Hi Ulf, > > On Mon, 17 Oct 2016 20:30:27 Ulf Magnusson wrote: >> Only PE and PV were shown, which might have been an oversight. The >> tuples passed to version_str() contain thr

[OE-core] [PATCH v2] bitbake: bitbake-layers: Make show-recipes show PR

Changes since v1: Remove now-redundant default 'pr' argument in QueryPlugin.version_str(). Ulf Magnusson (1): bitbake: bitbake-layers: Make show-recipes show PR bitbake/lib/bblayers/query.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) -- 2.7.4

[OE-core] [PATCH v2] bitbake: bitbake-layers: Make show-recipes show PR

Only PE and PV were shown, which might have been an oversight. The tuples passed to version_str() contain three elements (PE, PV, and PR), not two. Also remove now-redundant default 'pr' argument in QueryPlugin.version_str(). Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- bitba

[OE-core] [PATCH] bitbake: bitbake-layers: Make show-recipes show PR

Only PE and PV were shown, which might have been an oversight. The tuples passed to version_str() contain three elements (PE, PV, and PR), not two. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- bitbake/lib/bblayers/query.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

Re: [OE-core] [PATCH v2] scripts: add new script 'native'

On Thu, Oct 6, 2016 at 5:02 AM, Paul Eggleton wrote: > On Tue, 04 Oct 2016 12:22:56 Randy MacLeod wrote: >> On 2016-10-02 03:37 PM, Paul Eggleton wrote: >> >> "native" might be a bit too generic... >> >> >> >> > >> could I suggest oe_native-run or bitbake-native ?

[OE-core] [PATCH] scripts: Rename 'native' to 'oe-run-native'

Makes it a bit more descriptive and potentially more discoverable. Most people seemed to prefer an oe- prefix, so let's go with that. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- scripts/{native => oe-run-native} | 0 1 file changed, 0 insertions(+), 0 deletions(-) renam

Re: [OE-core] [PATCH 22/22] cmake: Use bb.fatal() instead of raising FuncFailed

On Thu, Oct 6, 2016 at 12:15 AM, Richard Purdie <richard.pur...@linuxfoundation.org> wrote: > On Wed, 2016-10-05 at 22:26 +0200, Ulf Magnusson wrote: >> On Sat, Oct 1, 2016 at 4:47 AM, Ulf Magnusson <ulfali...@gmail.com> >> wrote: >> > >> > This

Re: [OE-core] [PATCH 22/22] cmake: Use bb.fatal() instead of raising FuncFailed

On Sat, Oct 1, 2016 at 4:47 AM, Ulf Magnusson <ulfali...@gmail.com> wrote: > This sets a good example and avoids unnecessarily contributing to > perceived complexity and cargo culting. > > Motivating quote below: > > < kergoth> the *original* intent was for

Re: [OE-core] [PATCH v2 1/2] classes/uboot-extlinux-config: Add class

On Tue, Oct 4, 2016 at 12:24 AM, Ulf Magnusson <ulfali...@gmail.com> wrote: > On Tue, Oct 4, 2016 at 12:08 AM, Ulf Magnusson <ulfali...@gmail.com> wrote: >> Hello, >> >> On Mon, Oct 3, 2016 at 2:17 PM, Fabio Berton >> <fabio.ber...@ossystems.com.br>

Re: [OE-core] [PATCH v2 1/2] classes/uboot-extlinux-config: Add class

On Tue, Oct 4, 2016 at 12:08 AM, Ulf Magnusson <ulfali...@gmail.com> wrote: > Hello, > > On Mon, Oct 3, 2016 at 2:17 PM, Fabio Berton > <fabio.ber...@ossystems.com.br> wrote: >> This class allow the extlinux.conf generation for U-Boot use. >> The U-Boot support

Re: [OE-core] [PATCH v2 1/2] classes/uboot-extlinux-config: Add class

Hello, On Mon, Oct 3, 2016 at 2:17 PM, Fabio Berton wrote: > This class allow the extlinux.conf generation for U-Boot use. > The U-Boot support for it is given to allow the Generic Distribution > Configuration specification use by OpenEmbedded-based products. > >

Re: [OE-core] [PATCH v2] scripts: add new script 'native'

On Sun, Oct 2, 2016 at 4:30 PM, Ulf Magnusson <ulfali...@gmail.com> wrote: > On Sun, Oct 2, 2016 at 4:15 PM, Jérémy Rosen <jeremy.ro...@smile.fr> wrote: >> "native" might be a bit too generic... >> >> could I suggest oe_native-run or bitbake-native ?

Re: [OE-core] [PATCH v2] scripts: add new script 'native'

On Sun, Oct 2, 2016 at 4:15 PM, Jérémy Rosen wrote: > "native" might be a bit too generic... > > could I suggest oe_native-run or bitbake-native ? > > something that says it's yocto-galaxy specific and can be autocompleted with > a reasonable prefix... > > > Jérémy Rosen I

[OE-core] [PATCH 16/22] chrpath.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/chrpath.bbclass | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/meta/classe

[OE-core] [PATCH 17/22] testsdk.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/testsdk.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classe

[OE-core] [PATCH 21/22] testimage.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/testimage.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classes/

[OE-core] [PATCH 18/22] libc-package.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/libc-package.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classes

[OE-core] [PATCH 14/22] useradd.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/useradd.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classe

[OE-core] [PATCH 20/22] utility-tasks.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/utility-tasks.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/class

[OE-core] [PATCH 22/22] cmake: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/recipes-devtools/cmake/cmake_3.6.1.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/met

[OE-core] [PATCH 19/22] package.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/package.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classe

[OE-core] [PATCH 15/22] sstate.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/sstate.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/classes/sstat

[OE-core] [PATCH 13/22] gtk-immodules-cache.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/gtk-immodules-cache.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/me

[OE-core] [PATCH 12/22] systemd.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/systemd.bbclass | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/meta/classe

[OE-core] [PATCH 09/22] gummiboot.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/gummiboot.bbclass | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/meta/cla

[OE-core] [PATCH 11/22] license.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/license.bbclass | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/classe

[OE-core] [PATCH 10/22] update-rc.d.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/update-rc.d.bbclass | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/cla

[OE-core] [PATCH 07/22] syslinux.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/syslinux.bbclass | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/meta/cl

[OE-core] [PATCH 08/22] systemd-boot.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/systemd-boot.bbclass | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --gi

[OE-core] [PATCH 05/22] useradd-staticids.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/useradd-staticids.bbclass | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --gi

[OE-core] [PATCH 06/22] grub-efi.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/grub-efi.bbclass | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/meta/cl

[OE-core] [PATCH 04/22] package_rpm.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/package_rpm.bbclass | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) d

[OE-core] [PATCH 02/22] package_ipk.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/package_ipk.bbclass | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) d

[OE-core] [PATCH 03/22] package_deb.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/package_deb.bbclass | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) d

[OE-core] [PATCH 01/22] base.bbclass: Use bb.fatal() instead of raising FuncFailed

uncFailed.__init__ takes a 'name' argument rather than a 'msg' argument, which also shows that the original purpose got lost. Signed-off-by: Ulf Magnusson <ulfali...@gmail.com> --- meta/classes/base.bbclass | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/meta/cla

[OE-core] [PATCH 00/22] Use bb.fatal() instead of raising FuncFailed

alled in a context where it'd be safe. Ulf Magnusson (22): base.bbclass: Use bb.fatal() instead of raising FuncFailed package_ipk.bbclass: Use bb.fatal() instead of raising FuncFailed package_deb.bbclass: Use bb.fatal() instead of raising FuncFailed package_rpm.bbclass: Use bb.fatal()

Re: [OE-core] [PATCH 1/2] classes/uboot-extlinux-config: Add class

On Sat, Oct 1, 2016 at 12:54 AM, Ulf Magnusson <ulfali...@gmail.com> wrote: > On Fri, Sep 30, 2016 at 10:33 PM, Fabio Berton > <fabio.ber...@ossystems.com.br> wrote: >> This class allow the extlinux.conf generation for U-Boot use. >> The U-Boot support for it

Re: [OE-core] [PATCH 1/2] classes/uboot-extlinux-config: Add class

On Fri, Sep 30, 2016 at 10:33 PM, Fabio Berton wrote: > This class allow the extlinux.conf generation for U-Boot use. > The U-Boot support for it is given to allow the Generic Distribution > Configuration specification use by OpenEmbedded-based products. > > This

Re: [OE-core] [PATCH] e2fsprogs: add packageconfig for -file-

On Mon, Sep 19, 2016 at 7:00 AM, Ulf Magnusson <ulfali...@gmail.com> wrote: > On Mon, Sep 19, 2016 at 5:42 AM, Robert Yang <liezhi.y...@windriver.com> > wrote: >> >> >> On 09/19/2016 11:32 AM, Randy MacLeod wrote: >>> >>> On 2016-09-18 10:

Re: [OE-core] [PATCH] e2fsprogs: add packageconfig for -file-

On Mon, Sep 19, 2016 at 5:42 AM, Robert Yang wrote: > > > On 09/19/2016 11:32 AM, Randy MacLeod wrote: >> >> On 2016-09-18 10:37 PM, Christopher Larson wrote: >>> >>> >>> On Sun, Sep 18, 2016 at 7:32 PM, Randy MacLeod >>>

Re: [OE-core] [PATCH 2/2] package_manager.py: Change diagnostic messages per IRC

On Fri, Sep 16, 2016 at 12:47 AM, Mark Hatle wrote: > Based on a discussion with IRC user: Ulfalizer > > It was suggested that removing the diagnostic list, and replacing it with a > simple hint to what might be causing the problem was a better solution. > >

Re: [OE-core] [PATCH] bitbake: fetch2: Make SRCREV_FORMAT name substitution safer

On Mon, Sep 12, 2016 at 10:11 PM, Ulf Magnusson <ulfali...@gmail.com> wrote: > Given two names "foo" and "foobar" and SRCREV_FORMAT = "foo_foobar", > "foo" might currently get substituted twice. Work around the issue by > sorting the list

[OE-core] [PATCH] bitbake: fetch2: Make SRCREV_FORMAT name substitution safer

Given two names "foo" and "foobar" and SRCREV_FORMAT = "foo_foobar", "foo" might currently get substituted twice. Work around the issue by sorting the list of names by length and substituting longer names first. Signed-off-by: Ulf Magnusson <ulfa

[OE-core] [PATCH v4 0/1] useradd.bbclass: Simplify target overrides

Changes since v3: Add Signed-off-by line. Changes since v2: Like SYSROOTFUNC, USERADDSETSCENEDEPS needs to be set to "" for non-target classes. Otherwise, "${USERADDSETSCENEDEPS}" will be kept unexpanded as is for those. Ulf Magnusson (1): useradd.bblass: Simplify tar

[OE-core] [PATCH v4 1/1] useradd.bblass: Simplify target overrides

The current style might be a leftover from when _class-target did not exist. Also change the assignment to SSTATECLEANFUNCS to an append, which makes more sense. useradd.bbclass is the only user of SSTATECLEANFUNCS as of writing, so it won't make any functional difference. Signed-off-by: Ulf

[OE-core] [PATCH v3 1/1] useradd.bblass: Simplify target overrides

The current style might be a leftover from when _class-target did not exist. Also change the assignment to SSTATECLEANFUNCS to an append, which makes more sense. useradd.bbclass is the only user of SSTATECLEANFUNCS as of writing, so it won't make any functional difference. ---

[OE-core] [PATCH v3 0/1] useradd.bbclass: Simplify target overrides

Changes since v2: Like SYSROOTFUNC, USERADDSETSCENEDEPS needs to be set to "" for non-target classes. Otherwise, "${USERADDSETSCENEDEPS}" will be kept unexpanded as is for those. Ulf Magnusson (1): useradd.bblass: Simplify target overrides meta/classes/

Re: [OE-core] [PATCH] useradd.bblass: Simplify target overrides

On Tue, Aug 23, 2016 at 10:19 PM, Burton, Ross <ross.bur...@intel.com> wrote: > > On 9 August 2016 at 02:48, Ulf Magnusson <ulfali...@gmail.com> wrote: >> >> The current style might be a leftover from when _class-target did not >> exist. > > > Can you

[OE-core] [PATCH v2] useradd.bblass: Simplify target overrides

The current style might be a leftover from when _class-target did not exist. Also change the assignment to SSTATECLEANFUNCS to an append, which makes more sense. useradd.bbclass is the only user of SSTATECLEANFUNCS as of writing, so it won't make any functional difference. ---

Re: [OE-core] Broken "bitbake -S printdiff" in current OE

On Tue, Aug 23, 2016 at 8:18 AM, Mike Looijmans wrote: > Was attempting to figure out why something wasn't being grabbed from the > sstate-cache, but running "bitbake -S printdiff qt4-embedded" only yields > tons > of lines like this: > > WARNING:

Re: [OE-core] subtle weirdness when you combine "_append" with "+="?

On Wed, Aug 17, 2016 at 3:21 PM, Robert P. J. Day wrote: > On Tue, 16 Aug 2016, Khem Raj wrote: > > ... big snip ... > >> the _append/_prepend in conjunction with += is a undocumented >> behavior however, I do not see it as much a side effect. But in >> future bitbake may

Re: [OE-core] subtle weirdness when you combine "_append" with "+="?

On Tue, Aug 16, 2016 at 5:49 PM, Robert P. J. Day <rpj...@crashcourse.ca> wrote: > On Tue, 16 Aug 2016, Ulf Magnusson wrote: > >> On Tue, Aug 16, 2016 at 4:02 PM, Robert P. J. Day <rpj...@crashcourse.ca> >> wrote: >> > >> > was about to submit

Re: [OE-core] subtle weirdness when you combine "_append" with "+="?

On Tue, Aug 16, 2016 at 4:02 PM, Robert P. J. Day wrote: > > was about to submit a small number of patches to clean up redundancy > when people combine "_append" with "+=" (because it offends my > delicate sensibilities), and ran across this in oe-core, >

[OE-core] [PATCH] useradd.bblass: Simplify target overrides

The current style might be a leftover from when _class-target did not exist. Also change the assignment to SSTATECLEANFUNCS to an append, which makes more sense. useradd.bbclass is the only user of SSTATECLEANFUNCS as of writing, so it won't make any functional difference. ---

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

On Wed, Apr 13, 2016 at 11:34 AM, Burton, Ross <ross.bur...@intel.com> wrote: > > On 13 April 2016 at 10:07, Ulf Magnusson <ulfali...@gmail.com> wrote: >> >> The problem seems to be a race with building libbsd (and unlucky >> timing in my build). Adding

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

On Wed, Apr 13, 2016 at 11:07 AM, Ulf Magnusson <ulfali...@gmail.com> 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 follo

[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] classes/packagegroup: Refactor code to be simpler

This was originally going to be a fix for ALLOW_EMPTY not being set on complementary package groups, but that was already fixed by d96ea299b3b5a44b1959 (classes/packagegroup: fix dbg/dev/ptest complementary packages). Since I also spent some time refactoring the code, I'll submit a patch (against