[yocto] Screenshot tool

2019-04-16 Thread Evan O'Loughlin
Hi, I’m currently using yocto to build a custom OS based on Linux 4.9 for our hardware: Build Configuration: BB_VERSION= "1.32.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-16.04" TARGET_SYS= "arm-linux-gnueabi" MACHINE = "CUSTOM_MACHINE_NAME" DISTRO

Re: [yocto] Screenshot tool

2019-04-16 Thread Herman van Hazendonk
Hi Evan, We don't currently have a 4.9 kernel running for our project since we're working mainly with mobile devices which are stuck on 3.4 and 3.18 kernels for now, however we do have small screenshot utility which we have as a plugin to our compositor which we have been using since early Qt

[yocto] [meta-selinux][PULL] consolidated meta-selinux updates

2019-04-16 Thread Joe MacDonald
Hi all, This is the promised update to meta-selinux, incorporating all of the current pending patches I'm aware of on the list. As before, I'll give everyone a couple of days to check this out and raise any questions or concerns before merging it. Please take a look and let me know if you've got

Re: [yocto] [meta-selinux][PULL] refpolicy: update to 2.20190201 and git HEAD policies (2019-04-10 10:57:14 -0400)

2019-04-16 Thread Joe MacDonald
Hi all, Update on this, I've just now completed this merge (with Yi's corrected SRC_URI for the RELEASE_2.20190201 tag) and I'm going to start pulling in the additional meta-selinux patches that have been sent to the mailing list. I'll prep a queue of those updates soon and send out another pull

Re: [yocto] Failed to execute GCC

2019-04-16 Thread Lukasz Zemla
On Tuesday, April 16, 2019 3:10 AM JH wrote: > I am building an image on Ubuntu 18.04 host, I got following error: > unable to execute 'x86_64-linux-gnu-gcc': No such file or directory | error: > command 'x86_64-linux-gnu-gcc' failed with exit status 1 > I can see the x86_64-linux-gnu-gcc is a

[yocto] Yocto (poky) thud build problems with xen-image-minimal

2019-04-16 Thread Ken Bassford
Greetings, I have just transitioned to a clean upgrade to 'thud' (poky) and I'm having problems executing a test build of "xen-image minimal". My bblayers.conf file contains the following layers ... BBLAYERS ?= " \ /home/kbassford/repo/poky/meta \ /home/kbassford/repo/poky/meta-poky \ /home

[yocto] [OE-core] Yocto Project Status WW15'19

2019-04-16 Thread Richard Purdie
Current Dev Position: YP 2.7 M4 (2.7 rc2 is in QA) Next Deadline: YP 2.7 Release Target April 26, 2019 SWAT Team Rotation: SWAT lead is currently: Chen SWAT team rotation: Chen -> Armin on Apr. 19, 2019SWAT team rotation: Armin -> Anuj on Apr. 26, 2019 https://wiki.yoctoproject.org/wiki/Yocto_Buil

[yocto] Intel Galleio Board SSH Minimal Poky Image

2019-04-16 Thread nick
Greetings, What is the minimal image from the poky yocto recipes that has ssh enabled by default or is it just better to enable it in the core minimal image on system startup. Thanks, Nick -- ___ yocto mailing list yocto@yoctoproject.org https://lists

Re: [yocto] Intel Galleio Board SSH Minimal Poky Image

2019-04-16 Thread Chris Simmonds
Hi Nick, On 16/04/2019 16:36, nick wrote: > Greetings, > > What is the minimal image from the poky yocto recipes that has ssh enabled by > default or is it just better to enable it in the core minimal image on system > startup. core-image-minimal plus dropbear (ssh daemon) comes to 16 MB when in

Re: [yocto] Intel Galleio Board SSH Minimal Poky Image

2019-04-16 Thread Maciej Pijanowski
On 16.04.2019 17:36, nick wrote: Greetings, Hello, What is the minimal image from the poky yocto recipes that has ssh enabled by default or is it just better to enable it in the core minimal image on system startup. I would go with the core-image-minimal or the core-image-full-cmdline (depe