[linux-yocto] [linux-yocto 4.15] crypto: aes-generic - fix aes-generic regression on powerpc

From: Arnd Bergmann commit 6e36719fbe90213fbba9f50093fa2d4d69b0e93c upstream My last bugfix added -Os on the command line, which unfortunately caused a build regression on powerpc in some configurations. I've done some more analysis of the original problem and found slightly different

Re: [yocto] mono-native is trying to install files into a shared area...

I wrote: > > Lately, I'm trying to upgrade to a later version of mono, 5.4.1.6. When I try > to > do a build of my Yocto image, bitbake gets to the end of building mono- > native, and then gets an error: > > > ERROR: mono-native-5.4.1.6-r0 do_populate_sysroot: The recipe mono- > native is

Re: [yocto] sysroot not being populated

Hi Patrick On Mon, Jun 4, 2018 at 2:01 AM, Patrick Vacek wrote: > Hello all, > > I have a recipe (aktualizr-hsm-prov) that depends on another (aktualizr) > to provide an executable and a config file. The former recipe includes > `DEPENDS = "aktualizr-native"`, and my do_install() for >

Re: [yocto] Issue when integrating different bsp-layers on a single bblayers.conf

Hi Iván, On Thu 2018-06-07 @ 04:39:11 PM, Iván Castell wrote: > When setting the "build" directory with a bblayers.conf customized for a > single platform, each platform builds the image recipe properly. > > However, when I have integrated all bsp-layers in a single bblayers.conf, > the

[yocto] [meta-security][PATCH 2/2] Fix build issue for apparmor when systemd is used

When systemd is used as system init manager, there is a build issue complains "can't found apparmor.service". This patch fix it. Signed-off-by: Jinliang Li --- recipes-security/AppArmor/apparmor_2.11.0.bb | 5 + 1 file changed, 5 insertions(+) diff --git

[yocto] [meta-security][PATCH 1/2] Fix build issue for apparmor kernel configuration

Set the correct path of kernel configuration file in linux-yocto_4.%.bbappend to fix the build issue, which is "Fetcher failure for URL: 'file://apparmor.cfg'. Unable to fetch URL from any source." Signed-off-by: Jinliang Li --- recipes-kernel/linux/linux-yocto_4.%.bbappend | 2 +- 1 file

[yocto] [meta-security][PATCH 0/2] Fix build issue for apparmor

This patch series fix 2 build issues for apparmor. Jinliang Li (2): Fix build issue for apparmor kernel configuration Fix build issue for apparmor when systemd is used recipes-kernel/linux/linux-yocto_4.%.bbappend | 2 +- recipes-security/AppArmor/apparmor_2.11.0.bb | 5 + 2 files

Re: [yocto] cgroups and iptables problems running docker - maybe my config wrong?

On 04.06.2018 17:53, Bruce Ashfield wrote: On 2018-06-01 12:15 PM, Jakob Hasse wrote: Hello Bruce, Thank you very much for the quick response. I tried to built in the kernel changes. But the iptables error persists. I double checked over the weekend, and I have no problems with linux-yocto

[yocto] sysroot not being populated

Hello all, I have a recipe (aktualizr-hsm-prov) that depends on another (aktualizr) to provide an executable and a config file. The former recipe includes `DEPENDS = "aktualizr-native"`, and my do_install() for aktualizr-hsm-prov has a line something like this: aktualizr -i

[yocto] Minutes: Yocto Project Weekly Triage Meeting

Attendees: Armin, Stephen, Joshua, Amanda, Anuj, Richard, Ross, Randy, Trevor, Tim, Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage AR: Joshua - Close

[yocto] Issue when integrating different bsp-layers on a single bblayers.conf

Hello forum. I am trying to integrate several BSP-layers for different platforms on a single Yocto repository to build a Linux Yocto-based distro for all those platforms easily. The idea is maintaining a single bblayers.conf with all the layers available, set PLATFORM and DISTRO on local.conf,

Re: [yocto] [meta-mingw][PATCH] mingw-w64-runtime: Fix build with gcc8

On Thu, Jun 7, 2018 at 7:00 AM, Burton, Ross wrote: > I've a nigh-on identical patch in master-next running on the AB already: > > http://git.yoctoproject.org/cgit.cgi/meta-mingw/commit/?h=master-next=46b1bfd8ef26dd9c778504143d4dea2fbe2ce90f > > Don't have the security flags bit though (our mingw

[yocto] [meta-mingw][PATCH 2/2] pthreads-win32: Disable ssp for pthreads-win32

It compiles before gcc-runtime so ssp is not yet available Signed-off-by: Khem Raj --- recipes-devtools/pthreads-win32/pthreads-win32_2.9.1.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/recipes-devtools/pthreads-win32/pthreads-win32_2.9.1.bb

[yocto] [meta-mingw][PATCH V2 1/2] mingw-w64-runtime: Fix hardened build with gcc8

Signed-off-by: Khem Raj --- recipes-devtools/mingw-w64/mingw-w64-runtime_5.0.3.bb | 2 ++ 1 file changed, 2 insertions(+) diff --git a/recipes-devtools/mingw-w64/mingw-w64-runtime_5.0.3.bb b/recipes-devtools/mingw-w64/mingw-w64-runtime_5.0.3.bb index d249c79..a33a739 100644 ---

Re: [yocto] [meta-mingw][PATCH] mingw-w64-runtime: Fix build with gcc8

I've a nigh-on identical patch in master-next running on the AB already: http://git.yoctoproject.org/cgit.cgi/meta-mingw/commit/?h=master-next=46b1bfd8ef26dd9c778504143d4dea2fbe2ce90f Don't have the security flags bit though (our mingw builds don't use that), can you rebase to master-next and

[yocto] [meta-mingw][PATCH] mingw-w64-runtime: Fix build with gcc8

Signed-off-by: Khem Raj --- .../mingw-w64/mingw-w64-headers/gcc8.patch| 30 +++ .../mingw-w64/mingw-w64-headers_5.0.3.bb | 5 ++-- .../mingw-w64/mingw-w64-runtime_5.0.3.bb | 2 ++ 3 files changed, 35 insertions(+), 2 deletions(-) create mode 100644

[yocto] Run QEMU from within Eclipse

Hello All, I'd like to ask since I am setting uo the Eclipse IDE for Yocot app development and I got stuck to start the QEMU from within Eclipse. I got working QEMU image and seems running OK. *ubuntu@ubuntu:~/work/community/build-x11$ runqemu qemuarm

[yocto] link loop in /tmp (bug in volatile)

I think there is something unintended to create a /var/volatile/tmp/tmp as it links back to /var/volatile/tmp So if you are in /tmp and do a cd tmp you keep just where you are. Does this folder /tmp/tmp does make any sense? I doubt about. I think this line is not required in