[yocto] [meta-raspberrypi][PATCH] sdcard_image: Depend on do_deploy for kernel

SD image is expecting dtb files to be deployed in deploy area, this step however is done when do_deploy of kernel is finished and we need to pin that in dependency list, otherwise there are build race conditions during builds especially visible when building with initramfs enabled. Signed-off-by:

Re: [yocto] Problems building live image

On 3/14/16 15:58 , Rudolf Streif wrote: Richard, On Mon, Mar 14, 2016 at 1:55 PM, K Richard Pixley > wrote: If I add that line, ( IMAGE_FSTYPES = "vmdk" ), to my local.conf, I get: rich@burgess> time bitbake core-image-minimal ERROR: OE-cor

[yocto] OpenEmbedded Developer meeting April 8 after ELC/Yocto Project developer day

Yes, I am nagging. On the Friday after ELC in San Diego (Yocto Project Dev Day is Thursday), we will have a developer meeting near the conference venue Jefro has arranged for a room at the Marriot next to the conference venue, sponsored by the Yocto Project. OpenEmbedded would like to thank the Y

Re: [yocto] Problems building live image

Richard, On Mon, Mar 14, 2016 at 1:55 PM, K Richard Pixley wrote: > If I add that line, ( > > IMAGE_FSTYPES = "vmdk" > > ), to my local.conf, I get: > > rich@burgess> time bitbake core-image-minimal > ERROR: OE-core's config sanity checker detected a potential > misconfiguration. > Either f

Re: [yocto] Problems building live image

If I add that line, ( IMAGE_FSTYPES = "vmdk" ), to my local.conf, I get: rich@burgess> time bitbake core-image-minimal ERROR: OE-core's config sanity checker detected a potential misconfiguration. Either fix the cause of this error or at your own risk disable the checker (s

Re: [yocto] kernel: "devtool modify -x" issue

awesome! Thanks On Mon, Mar 14, 2016 at 1:53 PM, Paul Eggleton wrote: > I hope we are talking a week or less, but I'm not able to give you a > definitive > answer - it depends on patch review and how busy we are dealing with issues on > the master branch among other things. > > Cheers, > Paul >

Re: [yocto] kernel: "devtool modify -x" issue

I hope we are talking a week or less, but I'm not able to give you a definitive answer - it depends on patch review and how busy we are dealing with issues on the master branch among other things. Cheers, Paul On Mon, 14 Mar 2016 13:49:40 Steve Rae wrote: > thanks much... > I am very new to thi

Re: [yocto] kernel: "devtool modify -x" issue

thanks much... I am very new to this: does "not long though" mean 2-3 days or 2-3 weeks or ??? On Mon, Mar 14, 2016 at 1:47 PM, Paul Eggleton wrote: > Hi Steve, > > I've just sent out the patches; beyond that it's a matter of the stable branch > testing and integration process. I hope not long t

Re: [yocto] kernel: "devtool modify -x" issue

Hi Steve, I've just sent out the patches; beyond that it's a matter of the stable branch testing and integration process. I hope not long though. Cheers, Paul On Mon, 14 Mar 2016 11:51:08 Steve Rae wrote: > Paul -- please ETA for getting this into the "jethro" branch. > Thanks, Steve > > On Fr

Re: [yocto] kernel: "devtool modify -x" issue

Paul -- please ETA for getting this into the "jethro" branch. Thanks, Steve On Fri, Mar 11, 2016 at 10:11 AM, Steve Rae wrote: > OK - this seems to build successfully - Thanks! > >>> although I still do see the line: > Cloning into '/tmp/devtool6ZA4IK/workdir/source'... > > On Thu, Mar 10, 2

Re: [yocto] Two or more _append()'s on same task

On Mon, Mar 14, 2016 at 10:56 AM Daniel. wrote: > Hi all, > > I was wondering how OE/Yocto would respond if the same task is appended > twice. > > If I have a .bbclass that already creates a do_install_append() and I > inherit this class at my recipe, will my do_install_append be aplied: > > - Be

[yocto] Two or more _append()'s on same task

Hi all, I was wondering how OE/Yocto would respond if the same task is appended twice. If I have a .bbclass that already creates a do_install_append() and I inherit this class at my recipe, will my do_install_append be aplied: - Before .bbclass do_install_append() - After it - Will not be aplied

Re: [yocto] Problems building live image

> While we're on it... > > Can anyone explain what a "live" image is intended to be? > > (I haven't gotten a live image to "work", but I'm not entirely > sure I know what "work" means for a live image.) > > Or how hdddirect is intended to be different fr

Re: [yocto] Problems building live image

On 3/14/16 10:16 , Khem Raj wrote: On Mon, Mar 14, 2016 at 10:11 AM, K Richard Pixley wrote: While we're on it... Can anyone explain what a "live" image is intended to be? it can either boot from the disk or you can run the installer to install it to another media on your device. How is that

Re: [yocto] Problems building live image

On Mon, Mar 14, 2016 at 10:11 AM, K Richard Pixley wrote: > While we're on it... > > Can anyone explain what a "live" image is intended to be? it can either boot from the disk or you can run the installer to install it to another media on your device. > > (I haven't gotten a live image to "work"

Re: [yocto] Problems building live image

While we're on it... Can anyone explain what a "live" image is intended to be? (I haven't gotten a live image to "work", but I'm not entirely sure I know what "work" means for a live image.) Or how hdddirect is intended to be different from hddimg? --rich -- _

Re: [yocto] Problems building live image

> On Mar 14, 2016, at 10:01 AM, Gary Thomas wrote: > > On 03/14/2016 05:34 PM, K Richard Pixley wrote: >> On 3/13/16 22:16 , Gary Thomas wrote: >>> I'd like to to some testing that qemu just doesn't seem up to >>> so I attempted to build a live ISO per the documentation. I >>> added these lines

Re: [yocto] Problems building live image

On 03/14/2016 05:34 PM, K Richard Pixley wrote: On 3/13/16 22:16 , Gary Thomas wrote: I'd like to to some testing that qemu just doesn't seem up to so I attempted to build a live ISO per the documentation. I added these lines to local.conf: IMAGE_FSTYPES_genericx86 += "live" NOISO_genericx86

Re: [yocto] Problems building live image

On 3/13/16 22:16 , Gary Thomas wrote: I'd like to to some testing that qemu just doesn't seem up to so I attempted to build a live ISO per the documentation. I added these lines to local.conf: IMAGE_FSTYPES_genericx86 += "live" NOISO_genericx86 = "0" When I try to build core-image-base I get

Re: [yocto] New message

On 14 March 2016 at 15:58, Christopher Larson wrote: > You're using the poky distribution which for build performance uses >> uninative (from 477b8fb), which means that instead of building native >> dependencies per-host-distribution there's a static libc which is built >> against to enable nativ

Re: [yocto] New message

On Mon, Mar 14, 2016 at 5:50 AM Burton, Ross wrote: > On 14 March 2016 at 03:10, Gary Thomas wrote: > >> I just started a new build and saw a message that's new to me: >> NOTE: Fetching uninative binary shim from >> http://downloads.yoctoproject.org/releases/uninative/0.95/x86_64-nativesdk-lib

Re: [yocto] Strange build dependency

On Mon, Mar 14, 2016 at 6:55 AM Martin Jansa wrote: > On Mon, Mar 14, 2016 at 02:44:58PM +0100, Gary Thomas wrote: > > On 03/14/2016 01:51 PM, Gary Thomas wrote: > > > On 03/14/2016 01:46 PM, Burton, Ross wrote: > > >> > > >> On 14 March 2016 at 12:41, Gary Thomas g...@mlbassoc.com>> wrote: > >

[yocto] [meta-cgl][PATCH 3/6] remove lksctp-tools from meta-cgl

lksctp-tools was initially added with the aim to fulfill STD.3.1. The Linux kernel >2.6 includes support for the base features of SCTP, so there is no need for the package. Besides that, there is already a recipe defined in meta-networking that is kept up to date. If a P2 requirement will require

[yocto] [meta-cgl][PATCH 6/6] cgl_common_security_flags.inc: Remove compiler override for openhpi

Compiling openhpi with -fPIE works well now, so the override doesn't seem necessary anymore. Signed-off-by: Adrian Dudau --- meta-cgl-common/conf/distro/include/cgl_common_security_flags.inc | 1 - 1 file changed, 1 deletion(-) diff --git a/meta-cgl-common/conf/distro/include/cgl_common_securit

[yocto] [meta-cgl][PATCH 2/6] packagegroup-cgl-middleware: update drbd package name

drbd recipe has been renamed to drbd-utils in meta-networking Signed-off-by: Adrian Dudau --- meta-cgl-common/packagegroups/packagegroup-cgl-middleware.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-cgl-common/packagegroups/packagegroup-cgl-middleware.bb b/meta-cgl-

[yocto] [meta-cgl][PATCH 5/6] cgl_common_security_flags.inc: Add linker override for audit

Building audit with -fstack-protector-strong throws link errors on the native compiler. Add exception to avoid that. --- meta-cgl-common/conf/distro/include/cgl_common_security_flags.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/meta-cgl-common/conf/distro/include/cgl_common_security_fla

[yocto] [meta-cgl][PATCH 4/6] makedumpfile: compile with shared libraries

poky distro doesn't include static libraries by defaule anymore, so we should use shared libraries. If at a later point it proves that we must compile with static library we can override the no-static-libs include in our distro definition. Signed-off-by: Adrian Dudau --- meta-cgl-common/recipes-

[yocto] [meta-cgl][PATCH 1/6] sysvinit: remove permissions override

This leads to shutdown command being executable by everybody, which is a huge security issue. If there are issues related to the way this is configured in the main recipe, they should be handled differently. Signed-off-by: Adrian Dudau --- meta-cgl-common/recipes-core/sysvinit/sysvinit_2.%.bbapp

Re: [yocto] Strange build dependency

On Mon, Mar 14, 2016 at 02:44:58PM +0100, Gary Thomas wrote: > On 03/14/2016 01:51 PM, Gary Thomas wrote: > > On 03/14/2016 01:46 PM, Burton, Ross wrote: > >> > >> On 14 March 2016 at 12:41, Gary Thomas >> > wrote: > >> > >> How can I find out what's going on here? >

Re: [yocto] Strange build dependency

On 03/14/2016 01:51 PM, Gary Thomas wrote: On 03/14/2016 01:46 PM, Burton, Ross wrote: On 14 March 2016 at 12:41, Gary Thomas mailto:g...@mlbassoc.com>> wrote: How can I find out what's going on here? bitbake-whatchanged is generally helpful here. Do a build in one configuration, switc

Re: [yocto] Strange build dependency

On 03/14/2016 01:46 PM, Burton, Ross wrote: On 14 March 2016 at 12:41, Gary Thomas mailto:g...@mlbassoc.com>> wrote: How can I find out what's going on here? bitbake-whatchanged is generally helpful here. Do a build in one configuration, switch to the other, run bitbake-whatchanged. It

Re: [yocto] New message

On 14 March 2016 at 03:10, Gary Thomas wrote: > I just started a new build and saw a message that's new to me: > NOTE: Fetching uninative binary shim from > http://downloads.yoctoproject.org/releases/uninative/0.95/x86_64-nativesdk-libc.tar.bz2;md5sum=4b6fb2106c2f18b8f9c8ac67e1cf9e57 > > * What

Re: [yocto] Strange build dependency

On 14 March 2016 at 12:41, Gary Thomas wrote: > How can I find out what's going on here? > bitbake-whatchanged is generally helpful here. Do a build in one configuration, switch to the other, run bitbake-whatchanged. It will identify the hashes that have changed and try and chase them down. T

[yocto] Strange build dependency

I'm trying to sort out a problem with perl and have been switching between two different versions. What I don't understand is why so many recipes are being rebuilt when I change. I tried examining the dependencies with -g -u depexp but I'm unable to see why it's happening. I'm building core-ima

[yocto] [meta-selinux][PATCH] net-tools: Rebase netstat-selinux-support.patch

Signed-off-by: Adrian Dudau --- .../net-tools/netstat-selinux-support.patch| 55 +++--- 1 file changed, 28 insertions(+), 27 deletions(-) diff --git a/recipes-extended/net-tools/net-tools/netstat-selinux-support.patch b/recipes-extended/net-tools/net-tools/netstat-selinu