[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= "arago"
DISTRO_VERSION= "2017.12"
TUNE_FEATURES = "arm armv7a vfp thumb neon   callconvention-hard"
TARGET_FPU= "hard"
meta-processor-sdk = "HEAD:92db4d8023d88ab59fab2953e7447ec0bd5a6db1"
meta-ros  = "HEAD:e2566402ab108a19634354a934788109422cf409"
meta-arago-distro 
meta-arago-extras = "HEAD:5b2a44b0c4d989133bc13d59398fd10375d351bb"
meta-browser  = "HEAD:26d50665e2f7223c5f4ad7481a8d2431e7cb55fb"
meta-openamp  = "HEAD:8a214032bfb7e8124bc1485c70c69f7d60abb819"
meta-qt5  = "HEAD:2c9f0e4eb0e9097f6f872ec1e1d81768a8ab5f1b"
meta-networking   
meta-ruby 
meta-python   
meta-oe   
meta-gnome
meta-multimedia   = "HEAD:b40116cf457b88a2db14b86fda9627fb34d56ae6"
meta-ti   = "HEAD:3dc08477529b31ce887bb22a08201a843ded48f0"
meta-linaro-toolchain 
meta-optee= "HEAD:d73e794c7e7ebb1cc5bf495a52a72b26fb118250"
meta  = "HEAD:39fd8c129e2bff7f2f1649b7f6e036ccc50fd5d8"
meta-custom  = ""
meta-printing = "morty:72811bc3755d1a943fa2a2e79601781b44a77420"


We run a Qt5 application using EGLFS but can no longer capture screenshots. 
In a previous yocto build based on Linux 3.x we were able to use a screenshot 
tool which effectively just read /dev/fb0 to a file.

I believe this was a change to how the underlying drivers interact with the 
GPU/Screen - I've started reading up on KMS/DRM.


Does anyone know is there a utility/tool which I could use to capture the Qt5 
application as its drawn on screen?


Regards,
Evan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


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 
Qt5 releases and we're currently on Qt 5.11/5.12.


Might be worth to give a go at your end:

https://github.com/webOS-ports/luna-next/blob/f5fc4c8af0d0c6f74f57d3963eb570966bc8fa55/plugins/compositor/screenshooter.cpp

And the header file at:

https://github.com/webOS-ports/luna-next/blob/f5fc4c8af0d0c6f74f57d3963eb570966bc8fa55/plugins/compositor/screenshooter.h

Hope this helps.

Best regards,
Herman

On 2019-04-16 09:15, Evan O'Loughlin wrote:

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= "arago"
DISTRO_VERSION= "2017.12"
TUNE_FEATURES = "arm armv7a vfp thumb neon   
callconvention-hard"

TARGET_FPU= "hard"
meta-processor-sdk = "HEAD:92db4d8023d88ab59fab2953e7447ec0bd5a6db1"
meta-ros  = "HEAD:e2566402ab108a19634354a934788109422cf409"
meta-arago-distro
meta-arago-extras = "HEAD:5b2a44b0c4d989133bc13d59398fd10375d351bb"
meta-browser  = "HEAD:26d50665e2f7223c5f4ad7481a8d2431e7cb55fb"
meta-openamp  = "HEAD:8a214032bfb7e8124bc1485c70c69f7d60abb819"
meta-qt5  = "HEAD:2c9f0e4eb0e9097f6f872ec1e1d81768a8ab5f1b"
meta-networking
meta-ruby
meta-python
meta-oe
meta-gnome
meta-multimedia   = "HEAD:b40116cf457b88a2db14b86fda9627fb34d56ae6"
meta-ti   = "HEAD:3dc08477529b31ce887bb22a08201a843ded48f0"
meta-linaro-toolchain
meta-optee= "HEAD:d73e794c7e7ebb1cc5bf495a52a72b26fb118250"
meta  = "HEAD:39fd8c129e2bff7f2f1649b7f6e036ccc50fd5d8"
meta-custom  = ""
meta-printing = "morty:72811bc3755d1a943fa2a2e79601781b44a77420"


We run a Qt5 application using EGLFS but can no longer capture 
screenshots.

In a previous yocto build based on Linux 3.x we were able to use a
screenshot tool which effectively just read /dev/fb0 to a file.

I believe this was a change to how the underlying drivers interact
with the GPU/Screen - I've started reading up on KMS/DRM.


Does anyone know is there a utility/tool which I could use to capture
the Qt5 application as its drawn on screen?


Regards,
Evan

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[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 a pending change that isn't here.  There were a couple that
didn't get merged, but I think the only ones I dropped were due to being
no longer applicable (for example Yi's updates to refpolicy to the 2018
release).



The following changes since commit d6686698444616b9857a15bb514400f8a629e7ed:

  refpolicy: update to 2.20190201 and git HEAD policies (2019-04-12 15:28:38 
-0400)

are available in the Git repository at:

  git://git.yoctoproject.org/meta-selinux yocto/master-next

for you to fetch changes up to e0105eed2b2461bf08b7aaf71db12dfae6ca51e3:

  audit: change to use ${WORKDIR} instead ${S}/../ (2019-04-15 09:02:21 -0400)


Chen Qi (1):
  audit: change to use ${WORKDIR} instead ${S}/../

Kai Kang (2):
  layer.conf: update to warrior release name series
  setools: fix build failure with gcc 7

Luca Boccassi (1):
  packagegroup-selinux-minimal: add selinux-init

Sinan Kaya (1):
  libpcre: do no create links when compiling for windows

Yi Zhao (4):
  core-image-selinux.bb: remove trailing whitespace
  openssh: update sshd_config
  selinux-image.bbclass: using append instead of += for 
IMAGE_PREPROCESS_COMMAND
  selinux: remove git version

 classes/selinux-image.bbclass  |  2 +-
 conf/layer.conf|  2 +-
 recipes-connectivity/openssh/files/sshd_config | 53 +++--
 recipes-security/audit/audit_2.8.4.bb  |  2 +-
 recipes-security/images/core-image-selinux.bb  |  2 +-
 .../packagegroups/packagegroup-selinux-minimal.bb  |  1 +
 recipes-security/selinux/checkpolicy_git.bb|  6 --
 recipes-security/selinux/libselinux_git.bb | 14 
 recipes-security/selinux/libsemanage_git.bb| 17 
 recipes-security/selinux/libsepol_git.bb   |  8 --
 recipes-security/selinux/policycoreutils_git.bb|  6 --
 recipes-security/selinux/selinux_git.inc   | 11 ---
 ...ailure-with-GCC-7-due-to-possible-truncat.patch | 90 ++
 recipes-support/libpcre/libpcre_selinux.inc| 20 +++--
 14 files changed, 118 insertions(+), 116 deletions(-)
 delete mode 100644 recipes-security/selinux/checkpolicy_git.bb
 delete mode 100644 recipes-security/selinux/libselinux_git.bb
 delete mode 100644 recipes-security/selinux/libsemanage_git.bb
 delete mode 100644 recipes-security/selinux/libsepol_git.bb
 delete mode 100644 recipes-security/selinux/policycoreutils_git.bb
 delete mode 100644 recipes-security/selinux/selinux_git.inc

-- 
-Joe MacDonald.
:wq


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


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 mail to the list in order to keep everyone reasonably
informed of what's in and what's not.  Once that happens, if you have a
patch that's still pending but not in my pull list, please let me know
with a follow up to the list.

Thanks,
-J.

[[yocto] [meta-selinux][PULL] refpolicy: update to 2.20190201 and git HEAD 
policies (2019-04-10 10:57:14 -0400)] On 19.04.10 (Wed 11:53) Joe MacDonald 
wrote:

> This is a huge, long-overdue update the refpolicy.  I apologise for it
> blocking the other outstanding meta-selinux patches, but I've been
> trying to limit the scope of changes while this happens.  Now that this
> is cleared off the slate, I'll be gathering up the other meta-selinux
> patches from the list.  I'll send out a follow-up on those as they're
> merged and another when I think I'm done, so if I've missed your patch,
> that'll be the time to ping me about it.
> 
> As for this, here's what I've done.
> 
>   - manually reviewed all patches that had been present in
> repolicy-* for both the old stable (2.20170204) and git
> versions
> 
>   - forked the SELinuxPolicy/refpolicy repo and applied all
> still-relevant patches to the RELEASE_2.20190201 branch
> 
>   - restructured the patches so that all patches that should
> reasonably apply to all variants (mcs, mls, minimum, standard
> and targeted) were in a common branch and only the ones that
> are specific to each variant would be in their own recipe
> 
>   - restructure the patches so that systemd and sysvinit patches
> were not applied to the same tree
> 
>   - created a parallel set of branches for each of these against
> current git HEAD
> 
> The results of this can be examined here:
> 
>   https://github.com/joeythesaint/refpolicy
> 
> Then each of these were exported and put in the appropriate SRC_URIs so
> the branch structure is more-or-less preserved.
> 
> My goals with this approach were the following:
> 
>   - make it easier to keep refpolicy up to date, particularly for
> anyone wanting to use the git variants
> 
>   - make it easier to determine how your preferred version of
> refpolicy on Yocto differs from upstream refpolicy
> 
>   - limit the above differences to the minimum to achieve the goal
> of a functional Yocto system
> 
>   - eventually move us away from release tarballs entirely
> 
> That last point is why I'm preserving the refpolicy fork above.  I'd
> like to keep going with this and so future refpolicy patches will first
> be put in that repo then exported and applied to the SRC_URIs.  If you
> have such a patch and want to send me a PR against the branch you think
> it belongs on from github directly, that'd be awesome, but the old
> method of patches to the mailing list will work fine too, just know that
> this is the way I'm going to try to manage this for the foreseeable
> future.  Ultimately, if this proves to work well, I would like to move
> the refpolicy fork off github and house it on git.yoctoproject.org
> beside meta-selinux, but the workflow needs to be properly validated
> first.
> 
> One additional point, I intend to take another pass at revising this
> stuff, ideally moving the huge number of common patches out as well.
> There's still some that aren't necessary for base yocto but are for
> additional layers.  That's fine for us to have, but I'd like to get
> those moved to optional layer directories so we're making the best use
> of that functionality we can.  If you have suggestions on which pieces
> already present are good candidates, let me know.  Similarly, if you've
> got additional policy patches you want to see included, feel free to
> send them along, we can easily move them to optional locations inside
> meta-selinux.
> 
> Finally, please everyone test this and provide feedback on anything that
> doesn't work or looks strange.  This is easily the biggest change we've
> had in meta-selinux in years and I expect there's still some wrinkles to
> be ironed out.  And I really appreciate everyone's patience while we got
> to this point and hope it's not too much more pain before we put a
> ribbon on this and call it done.
> 
> I'll give this until at least the weekend before merging it to master,
> pending comments or an overwhelming "please just do it" from the
> community.
> 
> Thanks.
> 
> ---
> 
> The following changes since commit a6a3cadb1ef3203a123d8f5f9df27832f55b2ce3:
> 
>   Backport patches from upstream to fix build with musl (2019-03-25 09:43:53 
> +0100)
> 
> are available in the Git repository at:
> 
>   git://git.yoctoproject.org/meta-selinux yocto/master-next
> 
> for y

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 available, but why it failed to find it?

> $ which x86_64-linux-gnu-gcc
> /usr/bin/x86_64-linux-gnu-gcc

Could you provide more details, please? Which Yocto version do you use? Could 
you present some more context or logs?
What does following command does?
file /usr/bin/x86_64-linux-gnu-gcc

Best regards,
Lukasz Zemla

***
The information in this email is confidential and intended solely for the 
individual or entity to whom it is addressed.  If you have received this email 
in error please notify the sender by return e-mail, delete this email, and 
refrain from any disclosure or action based on the information.
***
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[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/kbassford/repo/poky/meta-yocto-bsp \ 
/home/kbassford/repo/poky/meta-openembedded/meta-oe \ 
/home/kbassford/repo/poky/meta-openembedded/meta-filesystems \ 
/home/kbassford/repo/poky/meta-openembedded/meta-python \ 
/home/kbassford/repo/poky/meta-openembedded/meta-networking \ 
/home/kbassford/repo/poky/meta-openembedded/meta-perl \ 
/home/kbassford/repo/poky/meta-intel \ 
/home/kbassford/repo/poky/meta-selinux \ 
/home/kbassford/repo/poky/meta-virtualization \ 
/home/kbassford/repo/poky/meta-security \ 
" 

My local.conf is appended with the following ... 
# Customizations 
DISTRO_FEATURES_append = " xen virtualization " 
IMAGE_INSTALL_append += " bridge-utils wireshark" 
IMAGE_EXTRA_INSTALL ?= " strace" 
CORE_IMAGE_EXTRA_INSTALL ?= " strace" 
PACKAGECONFIG_append_pn-recipename = " dhcp dhcpcd" 

IMAGE_ROOTFS_SIZE = "381600" 
BB_ENV_WHITELIST = " IMAGE_ROOTFS_EXTRA_SPACE" 

# for Dom0 
BOOTIMG_EXTRA_SPACE = '825312' 
BOOTIMG_VOLUME_ID = 'dom0sd' 

The first failure I encountered was this ... 
glibc-locale-2.28: glibc-locale: Files/directories were installed but not 
shipped in any package: 
/usr/lib/gconv/EBCDIC-DK-NO-A.so 
/usr/lib/gconv/IBM1097.so 
/usr/lib/gconv/IBM874.so 
/usr/lib/gconv/ISO8859-14.so 
/usr/lib/gconv/IBM865.so 
/usr/lib/gconv/IBM1157.so 
/usr/lib/gconv/MAC-CENTRALEUROPE.so 
/usr/lib/gconv/IBM274.so 
/usr/lib/gconv/EUC-JP.so 
/usr/lib/gconv/IBM1025.so 
... 

This has been documented on and off through several releases, usually solved by 
using "DISTRO_FEATURES_append =" in place of "DISTRO_FEATURES +=" in the 
local.conf file. Despite my local.conf containing "DISTRO_FEATURES_append = " 
the compile fails. 
Compiling glibc-locale by itself succeeds (bitbake glibc-locale -c cleanall && 
bitbake glibc-locale) 

The second failure I encountered was ... 
util/zbin.c:7:18: fatal error: lzma.h: No such file or directory 
#include  
^ 
compilation terminated. 

Compiling xz-native by itself succeeds, but compiling ipxe by itself fails with 
the same error. 

Could someone from the community tell me what I'm overlooking? 
Are there bugs in the aforementioned recipes? 

Apologies for the length, I wanted to include all the details up front. Thanks 
in advance. 

Sincerely, 
Ken Bassford 
Apertus Solutions

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[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_Build_Failure_Swat_Team
Next Team Meetings:
YP 2.8 Planning meeting Tuesday April 16nd at 8am PDT (
https://zoom.us/j/990892712) Bug Triage meeting Thursday April 18th at
7:30am PDT (https://zoom.us/j/454367603)
Key Status/Updates:
Stephen is unavailable at the moment, please refer any queries to
RichardYP 2.6.2 was rebuilt as rc4 to include the boost upgrade revert
and is due to be released today. The YP 2.6.2 rc3/4 report is
summarized at 
https://lists.yoctoproject.org/pipermail/yocto/2019-April/044827.html
and the results are at https://autobuilder.yocto.io/pub/releases/yocto
-2.6.2.rc4/testresults/.YP 2.5.3 is currently going through the QA
process.We’re sad to announce that we will be removing eclipse plugin
builds from the autobuilder and will not be including the plugin in any
future project releases. This is due to a lack of anyone able to help
work on the plugin development, bug fixing or release.The key fixes
mentioned in last week’s status have been merged into 2.7.A key bug in
pseudo was identified which may be the root cause of the long standing
glibc-locale uid “host contamination” issue. Many thanks to Peter and
Otavio for the help in debugging that. A separate fix should also
ensure pseudo works with newer distro coreutils and glibc versions.YP
2.7 rc2 (warrior) was built successfully and is currently going through
the QA process after 2.5.3 is done.The ptest results in 2.7 are much
more stable than ever before with results being consistent from build
to build. At the start of 2.8 we can make some further improvements so
we take advantage of this and build upon it to reduce regressions in
the system.In an effort to keep the patch queue under control, patches
are merging to master.The list of issues from last week of worrying
things we lack resources to improve upon remains:Intermittent
autobuilder failures (fork running out of resources - which resources?,
oe-selftest intermittent issues, gpg signing resource problems,
occasional PR server failure and more)Build-appliance testing issues
(show up on each QA report across multiple releases)40% valgrind ptest
failuresKnown bitbake memory resident bugsOther ptest failuresThe 2.8
planning discussions are starting and there is a google doc summarising
the discussions so far: 
https://docs.google.com/document/d/1CNEKA4d0eT6-e0hnS2pwi7xdZ5_t6smpZO2HbaJGXbU/If
people are planning to work on specific things in 2.8 please let us
know so we can incorporate this into our plans. If you’re interested in
working on anything in the document, please also let us know or talk
with us in one of the planning meetings.

Planned Releases for YP 2.7:
YP 2.7 M4 Cutoff was Apr. 1, 2019YP 2.7 M4 Release Target is Apr. 26,
2019
Planned upcoming dot releases:
YP 2.5.3 (Sumo) is in QA.
Tracking Metrics:
WDD 2523 (last week 2471) (
https://wiki.yoctoproject.org/charts/combo.html)Poky Patch Metrics
 Total patches found: 1553 (last week 1553)Patches in the Pending
State: 654 (42%) [last week 655 (42%)]
Key Status Links for YP:
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.7_Status
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Schedule
https://wiki.yoctoproject.org/wiki/Yocto_2.7_Features

The Status reports are now stored on the wiki at: 
https://wiki.yoctoproject.org/wiki/Weekly_Status

[If anyone has suggestions for other information you’d like to see on
this weekly status update, let us know!]


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[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.yoctoproject.org/listinfo/yocto


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
installed (BeagleBone Black). This is just the rootfs. Add another 6 to
10 MB for bootloader and kernel.

> 
> Thanks,
> 
> Nick
> 

Cheers,
Chris

-- 
Chris Simmonds, trainer and consultant at 2net
http://www.2net.co.uk
Author of "Mastering Embedded Linux Programming"
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


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 
(depending
on the requirements) and enable the ssh-server via IMAGE_FEATURES: 
https://www.yoctoproject.org/docs/2.5/ref-manual/ref-manual.html#ref-features-image


Typically, at the start of development, by adding the following line in 
build/conf/local.conf:


IMAGE_FEATURES_append = " ssh-server-openssh"


Thanks,

Nick


--
Maciej Pijanowski
Embedded Systems Engineer
https://3mdeb.com | @3mdeb_com

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto