Re: [yocto] Y-AB automatic updates?

On Tue, 2016-10-11 at 11:42 +0300, gm...@reliableembeddedsystems.com wrote: > Hi, > > With a latest and greatest Yocto Autobuilder I noticed stuff like > this  > when I restart it: > > --- > ... >   Updating PRSERV > remote: Counting objects: 20, done. > remote: Compressing objects: 100%

[yocto] [meta-security][PATCH] clamav: fixup improper quoting

Commit 217e06badb146539122732ab0eb27fd17cce09e5 [clamav: fix gcc 6.x build failure.] fixed a typo in "PACKAGECONFIG" (was missing the 'G') but unfortunately the PACKAGECONFIG string was incorrectly formed due to mismatched quotes. This caused a parsing error: ERROR: Unable to parse

[yocto] Proper way of rebuilding kernel image

Hi, I am compiling Yocto kernel image with: * a third party's "in-tree" kernel configuration * the same third party's BSP (which has some further kernel configurations as well) * my own kernel configuration fragments for my project on top of the above two What I found was if I make a small

Re: [yocto] Docs help - proper way of adding a userspace header for the kernel

On 10/11/16 4:21 AM, Paul Eggleton wrote: > Hi folks, > > Would someone be able to help Scott with the background for this: > > https://bugzilla.yoctoproject.org/show_bug.cgi?id=8596 > > It's not really my area of expertise and we really want this documented > properly once and for all. I

Re: [yocto] Y-AB automatic updates?

Hi, On 2016-10-11 17:39, Joshua Lock wrote: aren't set. If you point PRSERV_HOST and PRSERV_PORT at a non-localhost PRServer the git repo won't be fetched/updated. I use the Y-AB for nightly builds and to populate DL_DIR and friends. It's also not unusual to use this machine as the

[yocto] Conflict between multilib glibc and non-multlib glibc

Hi, We have a project running an aarch64 compatible processor. For backward compatibility with some internal software packages, we're using the armv7a-vfp machine type as a multilib lib32 variant. However, we have found that when attempting to install both lib32-glibc and glibc we encounter a

[yocto] Yocto compiles raspi kernel with 'bcm2709_defconfig' error.

I want to use the 'KBUILD_DEFCONFIG' to build the kernel, but an compile error happens, here is the piece of the log: NOTE: make -j 2 zImage CC=arm-poky-linux-gnueabi-gcc -mno-thumb-interwork -marm -fuse-ld=bfd LD=arm-poky-linux-gnueabi-ld.bfd CC

Re: [yocto] [meta-security][PATCH] clamav: fixup improper quoting

On 10/11/2016 07:30 AM, Mark Asselstine wrote: Commit 217e06badb146539122732ab0eb27fd17cce09e5 [clamav: fix gcc 6.x build failure.] fixed a typo in "PACKAGECONFIG" (was missing the 'G') but unfortunately the PACKAGECONFIG string was incorrectly formed due to mismatched quotes. This caused a

[yocto] add dejavu-fonts to image

Hi, i have build an image for an imx6 card (secoA62) based on this good layer https://github.com/graugans/meta-udoo (krogoth branch). All work fine but since the last version of qt 5.7, qtbase-font is not provided and now i have this error when i deploy an app : /QFontDatabase: Cannot find

[yocto] problem with developer sdk

Hi, i have rebuild an image of yocto krogoth with qt 5.6.2 (lasted release). The problem is now i have a problem with developer sdk. The problem is when i use it with a host machine (after install the script and configure qt creator), i obtain this error when i want to deploy an app :

Re: [yocto] [layerindex-web][PATCH v2 05/12] layerindex: Add distro to web interface and model.

On 10/10/16 3:20 AM, Paul Eggleton wrote: > This looks good, just a few notes about this bit: > > On Fri, 07 Oct 2016 11:57:14 Liam R. Howlett wrote: >> +def update_distro_conf_file(path, distro): >> +logger.debug('Updating distro %s' % path) >> +desc = "" >> +with open(path, 'r') as

Re: [yocto] [layerindex-web][PATCH v2 09/12] layerindex: Add collection and version to layerbranch

On 10/10/16 3:32 AM, Paul Eggleton wrote: > On Fri, 07 Oct 2016 11:57:18 Liam R. Howlett wrote: >> Collection and version will be pulled from the layer.conf if it exists >> and dependencies will be resolved by first checking for layers with the >> dependency name and then checking for collections.

Re: [yocto] [layerindex-web][PATCH v2 00/12] Add Distro, dependency and recommends detection, and import_project

On 10/10/16 10:24 PM, Paul Eggleton wrote: > On Tue, 11 Oct 2016 09:19:15 Paul Eggleton wrote: >> On Mon, 10 Oct 2016 12:47:11 Mark Hatle wrote: >>> On 10/10/16 12:37 PM, Paul Eggleton wrote: On Mon, 10 Oct 2016 04:48:41 Hatle, Mark wrote: >> On Oct 10, 2016, at 2:54 AM, Paul Eggleton

[yocto] Y-AB automatic updates?

Hi, With a latest and greatest Yocto Autobuilder I noticed stuff like this when I restart it: --- ... Updating PRSERV remote: Counting objects: 20, done. remote: Compressing objects: 100% (20/20), done. remote: Total 20 (delta 17), reused 0 (delta 0) Unpacking objects: 100% (20/20), done.

Re: [linux-yocto] [kernel-meta] meta-yocto-bsp: beaglebone: remove the stale kernel options

I'm about to get onto a plane, but when I land in Berlin, I can have a look and locate the missing change! Cheers, Bruce On Sat, Oct 8, 2016 at 3:37 AM, Kevin Hao wrote: > On Sat, Oct 08, 2016 at 03:36:34PM +0800, Kevin Hao wrote: > > On Tue, Sep 20, 2016 at

Re: [linux-yocto] [PATCH] Backport smack patch from 4.6 to 4.4

On 2016-10-11 11:51 AM, Saul Wold wrote: Bruce, Please merge this backported patch to 4.4, it's a backport so it can go in either standard/base or standard/intel/base. Ultimately it's needed in standard/intel/bxt-rebase. We need the upstream commit ID in the patch itself. But otherwise,

[linux-yocto] [PATCH] Backport smack patch from 4.6 to 4.4

Bruce, Please merge this backported patch to 4.4, it's a backport so it can go in either standard/base or standard/intel/base. Ultimately it's needed in standard/intel/bxt-rebase. Thanks Sau! Casey Schaufler (1): Smack: File receive for sockets security/smack/smack_lsm.c | 22

Re: [linux-yocto] [PATCH] Backport smack patch from 4.6 to 4.4

On Tue, 2016-10-11 at 11:58 -0400, Bruce Ashfield wrote: > On 2016-10-11 11:51 AM, Saul Wold wrote: > > > > Bruce, > > > > Please merge this backported patch to 4.4, it's a backport so it > > can go in either standard/base or standard/intel/base.  Ultimately > > it's needed in

[linux-yocto] [yocto-kernel-cache] [PATCH 2/4] bsp/leafhill: additional configs for graphics and media driver

From: Anuj Mittal Leaf Hill BSP media drivers required specific configurations. The configurations are unique and they are different from settings available in media feature fragments. Signed-off-by: Anuj Mittal Signed-off-by: Rebecca Chang Swee

[linux-yocto] [yocto-kernel-cache] [PATCH 0/4] Configs only for Leaf Hill BSP

Hi Bruce, The reason for these changes for Leaf Hill BSP is we have special requirements for specific drivers to be compiled as built-in feature and some need to be loadable modules. We understand that most of the configs has its own feature fragments to be reused for BSP enabling. Due to the

[linux-yocto] [yocto-kernel-cache] [PATCH 4/4] bsp/leafhill: configs for LPSS I/O and misc. driver support

From: Anuj Mittal It was a requirement to compile some drivers as built-in and some drivers as loadable modules. Since the configurations are different from feature fragments, we have specifically called out the kernel configurations in leafhill.cfg to make it unique to

[linux-yocto] [yocto-kernel-cache] [PATCH 3/4] bsp/leafhill: additional configs setting for connectivity support

From: Anuj Mittal We want the additional MWIFIEX wifi support for Leaf Hill. Additionally we want the ethernet driver to be compiled as loadable modules. Signed-off-by: Anuj Mittal Signed-off-by: Rebecca Chang Swee Fun

[linux-yocto] [yocto-kernel-cache] [PATCH 1/4] bsp/leafhill: additional USB configs for leafhill bsp

From: Anuj Mittal We need additional USD net support for Leaf Hill BSP and USB controller support required to be compiled as modules. These settings are required to be different from configs set in feature fragments. Signed-off-by: Anuj Mittal