Re: [linux-yocto] [yocto-4.12][PATCH 0/4] enable Cannon Lake PCH gpio support

On 2018-02-01 9:02 PM, Liwei Song wrote: ping... I've been working on 4.14, 4.15 as well as CVE backports, so this is still pending, but will be merged shortly. Bruce On 01/26/2018 09:55 AM, Liwei Song wrote: Hi Bruce, These patches include a kernel-cache patch to enable kernel option

Re: [linux-yocto] [yocto-4.12][PATCH 0/4] enable Cannon Lake PCH gpio support

ping... On 01/26/2018 09:55 AM, Liwei Song wrote: > Hi Bruce, > > These patches include a kernel-cache patch to enable kernel option > CONFIG_PINCTRL_CANNONLAKE. > Other patches are upstream patches to enable Cannon Lake PCH gpio support. > Please review and merge them. > > Thanks, > Liwei. >

Re: [yocto] gcc leak-sanitizer on arm target

On Wed, Jan 31, 2018 at 7:06 AM, Pieter Cardoen wrote: > > Dear > > > > I am having trouble to enable leak sanitizer and thread sanitizer for my > > arm target. If I enable gcc-sanitizers, I only have these libraries on the > > target rootfs: > > * libasan.so.3 > > *

Re: [yocto] applying patches depending on the image's name

Hi Ross, This "two different kernels" feature would be useful to me. Where can I find out how to use it? Regards, MV On 01/11/18 12:34, Burton, Ross wrote: No, because images are built from packages, and the packages have already been built by the time the image is considered. Using master

Re: [yocto] Patching only the target version of a package?

bbclasses can cause a recipe to be cloned and overrides created. The overrides are class-target for the target build, class-native for the native build, class-nativesdk for the SDK build. The mechanism is normally inheriting the class directly (eg when a recipe is only useful as native) or using

Re: [yocto] Installing Wind River Linux

On 1/30/18 3:15 AM, 永瀨桂 wrote: > Hi, > I'm trying to build the installer for using the WindRiverLinux9 with a > development board. > > I want to build the installer's image using the Intel-corei7-64 BSP, but > I can't build wrlinux-image-glibc-small like in the guide below. >

Re: [yocto] Patching only the target version of a package?

Thanks, that seems to be pretty much precisely what I need. Where can I learn more about the class construct, e.g. class-target and native? I saw some references to it in the docs, but not an actual explanation of how that all works and is put together. Any ideas? On Thu, Feb 1, 2018 at 9:34 AM,

Re: [yocto] [PATCH] opkg-build: improve package reproducibility

merged From: Alejandro del Castillo Sent: Monday, January 29, 2018 4:23:15 AM To: opkg-de...@googlegroups.com; yocto@yoctoproject.org Cc: Alejandro del Castillo Subject: [PATCH] opkg-build: improve package reproducibility

[yocto] [multilib] 64-bit and 32-bit package install the same executable

I've noticed that for my custom image both the 32-bit and the 64-bit versions of the same package are getting installed. For example, it has both shadow-base and lib32-shadow-base installed. When I check the /bin/su.shadow executable I find it is 32-bit. Is it expected that the lib32 version

[yocto] fsck fsck.ext4 no such file or directory

Hi all, when I try to use fsck tool, this one answer me,  fsck : fsck.ext4 no such file or directory. anyone have an idea whyt these files are not include automatically in the rootfs? Thanks -- ___ yocto mailing list yocto@yoctoproject.org

Re: [yocto] Patching only the target version of a package?

On 1 February 2018 at 15:03, Michael Habibi wrote: > So let's say my whole bbappend file is only necessary for the target > version. Can I rename the whole thing package-target.bbappend (add the > -target suffix) and it will only append it to the recipe when building the >

Re: [yocto] Patching only the target version of a package?

So let's say my whole bbappend file is only necessary for the target version. Can I rename the whole thing package-target.bbappend (add the -target suffix) and it will only append it to the recipe when building the target? Is "target" the actual suffix or is it a placeholder for something more

Re: [yocto] Patching only the target version of a package?

On 1 February 2018 at 14:29, Michael Habibi wrote: > I'm sure this is really simple but I haven't quite wrapped my head around > it. > > We have a bbappend file that supplies a set of patches. It currently has > the unintended side-effect of patching both the native version

[yocto] Patching only the target version of a package?

I'm sure this is really simple but I haven't quite wrapped my head around it. We have a bbappend file that supplies a set of patches. It currently has the unintended side-effect of patching both the native version used during the Yocto build process, and the eventual target version. How do I

Re: [yocto] [meta-raspberrypi][PATCH] [kronos]wayland lib linking added for libbrcmEGL to avoid undefined symbol while linking libbrcmEGL.so

On Thu, Feb 1, 2018 at 6:56 AM, HASEENAMOL wrote: > [meta-raspberrypi][PATCH] > > In wayland enabled build libbrcmEGL lib is using wayland functions, but > during the build it is not linking with wayland libraries. Hence if try to > link libbrcmEGL, will get undefined

[yocto] meta-ide-support toolchain & Recipe-specific Sysroots

I have a problem starting from the rocko upgrade and related to the Recipe-specific Sysroots introduced in Yocto 2.3 Our project uses cmake. So out recipe has: DEPENDS = "cmake-native [...]" So cmake ends up in

Re: [yocto] error: impossible constraint in 'asm'

2018-02-01 9:32 GMT+01:00 dhkoo : > Hi. > > > > Recently, I'm work on mplayer that media player for my custom system. > > My Kernel version is 3.8, and mplayer version is 1.3.0. > > > > And when I perform bitbake, there's error on do_compile process. The > messages says like

[yocto] error: impossible constraint in 'asm'

Hi. Recently, I'm work on mplayer that media player for my custom system. My Kernel version is 3.8, and mplayer version is 1.3.0. And when I perform bitbake, there's error on do_compile process. The messages says like below. ERROR: mplayer-1.3.0-r0 do_compile: oe_runmake failed ERROR: