[yocto] Fwd: do_configure error

-- Forwarded message -- From: "mohammed aqdam" Date: Sep 21, 2017 6:59 PM Subject: do_configure error To: "yocto" Cc: Hi all, i was trying to build rpi-test-image for my rpi3. i'm getting the following error...

Re: [yocto] libgcrypt building fails for armv6 binaries.

On 09/22/2017 09:15 PM, Yusuke Mitsuki wrote: > Hello yocto > > libgcrypt has problem that build for armv6. > bitbake said error messages at do_compile as follows: > ...(snip)... > | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S: Assembler > messages: > |

[yocto] libgcrypt building fails for armv6 binaries.

Hello yocto libgcrypt has problem that build for armv6. bitbake said error messages at do_compile as follows: ...(snip)... | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S: Assembler messages: | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165: Error: selected processor

Re: [linux-yocto] [linux-yocto-4.8][PATCH] mm/workingset.c: fix implicit declaration of __list_lru_init_key

Cal, On 09/22/2017 03:48 PM, California Sullivan wrote: > __list_lru_init_key does not exist. We're looking for __list_lru_init as > shown in the patch "26690f5 mm: workingset: fix premature shadow node > shrinking with cgroups". > > Signed-off-by: California Sullivan

Re: [yocto] RFC: Backwards compatibility checking sstate-cache

On 22/09/17 15:00, Mike Looijmans wrote: I think this remark in the referenced link is the best summary of "what could be improved": """the biggest weakness of the sstate signature bits, in my opinion, is that it only tracks inputs, not outputs. If task A depends on B, and the metadata input

[linux-yocto] [linux-yocto-4.8][PATCH] mm/workingset.c: fix implicit declaration of __list_lru_init_key

__list_lru_init_key does not exist. We're looking for __list_lru_init as shown in the patch "26690f5 mm: workingset: fix premature shadow node shrinking with cgroups". Signed-off-by: California Sullivan --- This is for the standard/preempt-rt/base branch.

[yocto] Workdir of qmake5 recipes in Pyro

Hi I have a qt5 recipe which is built for a imx6 system with MACHINE=lm_cm-poky-linux-gnueabi). The recipe sp.bb contains: include qmake5 # PACKAGE_ARCH = "${MACHINE_ARCH}" When I build this on Krogoth I find the build for my recipe under:

Re: [yocto] release management

I have also been slightly puzzled over the meticulousness and determinism of Yocto on recipe level, but the left-to-yourself thinking for the top-level meta-level and configuration management. We have chosen to make a custom configuration management (CM) and lightweight build system on top of

Re: [yocto] RFC: Backwards compatibility checking sstate-cache

I think this remark in the referenced link is the best summary of "what could be improved": """the biggest weakness of the sstate signature bits, in my opinion, is that it only tracks inputs, not outputs. If task A depends on B, and the metadata input to B changes, then A will be rebuilt,

Re: [yocto] Path to current bb-file or layer

On 22. sep. 2017 13:42, Richard Purdie wrote: A better way to get what you're after may be to look at the contents of BBINCLUDED. Ah, yes. Perfect. You got me onto a lead: Setting SP_BASEDIR := "${LAYERDIR}" in layer.conf and then access this variable from the bbclass file. Although I

Re: [yocto] Path to current bb-file or layer

On Fri, 2017-09-22 at 13:04 +0200, Svein Seldal wrote: > On 22. sep. 2017 10:30, Richard Purdie wrote: > > Its all about when your code is executed. Try putting: > >  > > SP_BASEVERSION := "${@read_spbaseversion(d)}" > >  > > in the bbclass file. I suspect that will give you the bbclass file > >

Re: [yocto] Path to current bb-file or layer

On 22. sep. 2017 10:30, Richard Purdie wrote: > Its all about when your code is executed. Try putting: > > SP_BASEVERSION := "${@read_spbaseversion(d)}" > > in the bbclass file. I suspect that will give you the bbclass file > name. > > By default everything is deferred expansion so your code

[linux-yocto] [kernel-cache][PATCH] cgl: Add cgl features

From: He Zhe Add features for Carrier Grade Linux https://wiki.linuxfoundation.org/cgl/start Signed-off-by: He Zhe --- cfg/dmm.cfg | 1 + cfg/dmm.scc | 4 cfg/drbd.cfg | 1 +

Re: [yocto] QA cycle report for 2.3.2 rc1

On 22/09/17 00:42, Cruz, Libertad wrote: === QA-Hints QA needs help from Joshua and the official AB so that we may run the Ubuntu 17.04 distro testing, if you have an Ubuntu 17.04 worker. With the objective that the report would be complete before CCB session finishes analyzing

Re: [yocto] Path to current bb-file or layer

On Fri, 2017-09-22 at 10:17 +0200, Svein Seldal wrote: > On 21. sep. 2017 23:36, Richard Purdie wrote: >  > You mean like ${FILE} ? >  > >  > $ bitbake bash -e | grep ^FILE= >  > FILE="/media/build1/poky/meta/recipes-extended/bash/bash_4.4.bb" > > To me ${FILE} seems to be pointing towards the

Re: [yocto] Path to current bb-file or layer

On 21. sep. 2017 23:36, Richard Purdie wrote: > You mean like ${FILE} ? > > $ bitbake bash -e | grep ^FILE= > FILE="/media/build1/poky/meta/recipes-extended/bash/bash_4.4.bb" To me ${FILE} seems to be pointing towards the receipe, and not the current .bbclass file as you'd expect. If I put