Re: [yocto] [OE-core] [RFT] GCC 8.1

I threw the branch at the Yocto Project autobuilder today, produced a number of failures: http://errors.yoctoproject.org/Errors/Latest//?filter=b23dba19607412c8cc7d267d95354d65f5631088=commit Ross On 5 May 2018 at 01:26, Khem Raj wrote: > Hi All > > As you might have

[yocto] [ANNOUNCEMENT] Yocto Project 2.5 (sumo 19.0.0) Released

Hello, We are pleased to announce the latest release of the Yocto Project 2.5 (sumo-19.0.0) is now available for download at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.5/poky-sumo-19.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.5/poky-sumo-19.0.0.tar.bz2 A gpg

[yocto-announce] [ANNOUNCEMENT] Yocto Project 2.5 (sumo 19.0.0) Released

Hello, We are pleased to announce the latest release of the Yocto Project 2.5 (sumo-19.0.0) is now available for download at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.5/poky-sumo-19.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.5/poky-sumo-19.0.0.tar.bz2 A gpg

Re: [linux-yocto] v4.12.x - stable updates comprising v4.12.24

On 05/10/2018 02:30 PM, Paul Gortmaker wrote: > Bruce, Yocto kernel folks: > > Here is another 4.12.x stable update "extension" primarily created for > the Yocto project, continuing on top of the previous v4.12.23 kernel. Thanks for keeping this kernel version updated. Much appreciated. I know

Re: [yocto] [meta-selinux][PATCH] libselinux: python-importlib is now part of python*-core

Thank you, Mark. Much appreciated and understood. Would you be open to tagging the layer for rocko to the right commit and applying the patches sent to the mailing list by Armin and Kai to master so that we have known points to move forward? Thank you, Rudi On 05/11/2018 10:45 AM, Mark Hatle

Re: [yocto] [meta-selinux][PATCH] libselinux: python-importlib is now part of python*-core

On 5/11/18 12:28 PM, Rudolf J Streif wrote: > Echoing this: may I ask what the current maintenance status of > meta-selinux is. It appears that no updates have been made for more than > 9 months. This is of course not to blame anybody but out of concern that > the layer is falling behind even more

Re: [yocto] [meta-selinux][PATCH] libselinux: python-importlib is now part of python*-core

Echoing this: may I ask what the current maintenance status of meta-selinux is. It appears that no updates have been made for more than 9 months. This is of course not to blame anybody but out of concern that the layer is falling behind even more and to find a solution. In addition to Armin's

Re: [yocto] Wrong file's ownership in rootfs.

Hi! On Fri, May 11, 2018 at 2:42 PM, Grzegorz Mierzejewski wrote: > Hello all, > > I have the following problem concerning the file's ownership. > In my recipe I install the new file to rootfs and change it's ownership in > do_install function: > do_install () { >

Re: [yocto] Compilation error after upgrading rocko branch

This works fine. Thanks a lot! :-) 2018-05-11 14:10 GMT+02:00 Burton, Ross : > Turns out this is due to uninative only having a limited subset of the > conversion tables and fontforge checks for ones that we don't ship. > The good news is that Khem sent a patch this

Re: [yocto] Compilation error after upgrading rocko branch

Turns out this is due to uninative only having a limited subset of the conversion tables and fontforge checks for ones that we don't ship. The good news is that Khem sent a patch this morning, but the workaround right now is to disable uninative. This in your local.conf will work: INHERIT_remove

[yocto] Compilation error after upgrading rocko branch

Hello forum. After updating all my layers to the lastest state of the "rocko" branch, I am getting this error in "meta-oe" layer: | In file included from ../../git/fontforge/splinefont.h:36:0, | from ../../git/fontforge/sd.h:34, | from

[yocto] Wrong file's ownership in rootfs.

Hello all, I have the following problem concerning the files ownership. In my recipe I install the new file to rootfs and change its ownership in do_install function: do_install () {     install -p -m 644 file1 ${D}/     chmod 777 ${D}/file1     chown ${USER_DUMMY} ${D}/file1 }