[yocto] QA cycle report for 2.4 RC2

Hello All, Enjoy viewing the full Report for 2.4 RC2: https://wiki.yoctoproject.org/wiki/WW41_-_2017-10-13_-_Full_Test_Cycle_2.4_RC2 === Summary The QA cycle for release 2.4 RC2 is complete. There are 5 new bugs from which so far none of them are high. There seems to be no b

[yocto] why there is no branch dizzy in meta-ti ?

I work on dizzy branch of yocto/meta-ti, and I can see here :  http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/refs/heads  that there is no dizzy branch. Why ? Few weeks / month ago, the wifi on my boards stopped working after doing a repo sync ... (my bad) ... I think one of the layer changed

Re: [yocto] How to use two recipes to satisfy different PROVIDES -- gpu support

Raj, Thanks for your response. I figured two issues I had in my original recipe. (after your response and other queries I did) a) virtual/libgl is not provided by my recipe, and I was claiming to provide it. b) I read that mesa has to provide some of the libraries, even if you have a GPU, so

[yocto] raspberrypi3 static library linking

Hello everyone, I'm using a raspberry pi 3 with meta-raspberrypi meta layer. I have created a meta-layer (meta-kp) with two recipes directories: - *recipes-example*: an example taken from Embedded Linux Projects Using Yocto Project Cookbook with a static library recipe and the relative

[yocto] aarch64-poky-linux-gcc error during compilation

Hello, I am trying to include mlpack (with python bindings) to my yocto build. I get the following error while building the python bindings: === aarch64-poky-linux-gcc -march=armv8-a -mtune=cortex-a57.cortex-a53 --sysroot=/builds/build-h3/tmp/sysroots/h3ulc

Re: [yocto] Yocto Image with custom directory layout

Hi, On 12.10.2017 19:07, Ayoub Zaki wrote: Hi, I would like to generate an image that contains a custom directories layout for expl: foo/ ├── bar1 │   └── bar2 │   ├── config │   └── data └── work └── var └── lib ├── config └── data It shoul

[yocto] rocko problem with external cross compilation

Hi, we're bumping our layer to latest master (rocko). Previously we use for development purposes only flow like: - build image and use sysroot + toolchain for cross compilation (we use cmake where we setup toolchain file with correct paths and compile our application) But when try to use same app

[yocto] [meta-selinux][PATCH] refpolicy: fix boot failure with systemd + mls

From: Wenzong Fan * Allow kernel_t to lower file level * Allow kernel_t to set process level Signed-off-by: Wenzong Fan --- ...-kernel_t-mls-trusted-for-lowering-file-l.patch | 74 ++ ...-kernel_t-mls-trusted-for-setting-process.patch | 43 + .../refpolicy/refpo

Re: [yocto] possible to append or patch existing machine .conf file?

I have now combined the last 2 answers: I did not want to put more customization than machine and distro into my local.conf and since I already have my own distro conf I have now put the include conf/machine/${MACHINE}-extra.conf into my own distro conf file and made colibri-vf-extra.conf, both fi

Re: [yocto] Yocto Image with custom directory layout

On 12/10/2017 20:47, Ayoub Zaki wrote: > Hi, > > > On 12.10.2017 20:34, Josef Holzmayr wrote: >> Hi >> >> On 12.10.2017 19:07, Ayoub Zaki wrote: >>> Hi, >>> I would like to generate an image that contains a custom directories >>> layout for expl: >>> >>> >>> foo/ >>> ├── bar1 >>> │   └── bar2 >>>