Re: [yocto] How to log inside a recipe #yocto

Thanks a lot. That works perfectly, but do you know how to use the log commands inside the recipe? It seems they work inside functions only (`do_install` e.g.) -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#55496):

[yocto] Is there any recipe for #FRR

Hi There is an old discussion regarding this in this link: https://lists.frrouting.org/pipermail/frog/2019-January/000445.html But I can't find any updated one. Is there an updated recipe to build FRR? Thanks -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply

Re: [yocto] How to log inside a recipe #yocto

Hi To get a value of some variable added in recipe it is best to use bitbake with `-e` flag which should print the whole environment, then one can just use `grep` to search for given variable. Let say we have recipe `example.bb` and need to know the value of `A_VAR` - with bitbake you can find it

[yocto] How to log inside a recipe #yocto

Hi There is a variable (or what ever it's called) inside a recipe. I want to know its value. I've used `bbnote "something"` but this gives a parse error. How to properly log? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#55493):

[yocto] Help with Inclusive Language in OpenEmbedded/Yocto Project

This email is a follow-up from the session held on Friday at the OpenEmbedded Developer's Virtual Meeting (see https://www.openembedded.org/wiki/OEDVM_Nov_2021) The session was not recorded, but the slides can be found at

Re: [yocto] Setting BUILDNAME to a string broke in 3.1.12

On Mon, 2021-12-06 at 14:27 -1000, Steve Sakoman wrote: > On Mon, Dec 6, 2021 at 6:40 AM Henrik Riomar wrote: > > > > Hi, > > > > We set the BUILDNAME (via local.conf) variable to the output of "git > > describe --long --always" so this info ends up in /etc/version instead > > of a date. (i.e

Re: [yocto] Setting BUILDNAME to a string broke in 3.1.12

On Mon, Dec 6, 2021 at 6:40 AM Henrik Riomar wrote: > > Hi, > > We set the BUILDNAME (via local.conf) variable to the output of "git > describe --long --always" so this info ends up in /etc/version instead > of a date. (i.e to know the exact source version of the code > deployed on a target) > >

[yocto] spdx: Extending SPDX SBOMs for SDKs

Hello, I've been working on extending SPDX SBOMs for SDKs. In poky/meta/classes/create-spdx.bbclass I added: /do_populate_sdk[recrdeptask] += "do_create_spdx do_create_runtime_spdx"/ I ran into a dependency loop when I try to build an SDK that contains nativesdk-clang (it works fine for

[yocto] Enhancements/Bugs closed WW49!

All, The below were the owners of enhancements or bugs closed during the last week! Who Count michael.opdenac...@bootlin.com 1 Grand Total 1 Thanks, Stephen K. Jolley Yocto Project Program Manager *Cell:(208) 244-4460 * Email:

[yocto] Current high bug count owners for Yocto Project 3.5

All, Below is the list as of top 46 bug owners as of the end of WW49 of who have open medium or higher bugs and enhancements against YP 3.5. There are 99 possible work days left until the final release candidates for YP 3.5 needs to be released. Who Count r...@burtonini.com 36

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading:

Re: [yocto] Setting BUILDNAME to a string broke in 3.1.12

Hi, On Mon, 6 Dec 2021 at 17:40, Henrik Riomar wrote: > > Hi, > > We set the BUILDNAME (via local.conf) variable to the output of "git > describe --long --always" so this info ends up in /etc/version instead > of a date. (i.e to know the exact source version of the code > deployed on a target) >

[yocto] Setting BUILDNAME to a string broke in 3.1.12

Hi, We set the BUILDNAME (via local.conf) variable to the output of "git describe --long --always" so this info ends up in /etc/version instead of a date. (i.e to know the exact source version of the code deployed on a target) This has worked fine for us up until 3.1.12, but now we just get a

Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.4.1.rc1)

Hello everyone, This is the full report for yocto-3.4.1.rc1: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults === Summary No high milestone defects. new issue found Bug 14622 - bsps-hw.bsps-hw.Test_Seek_bar_and_volume_control

[linux-yocto] [linux-yocto preempt-rt kernel]: nxp-s32g2xx: update linux-yocto to NXP bsp31 release version

Hi Bruce, There are 42 patches(including 25 patches from bsp31 rc5~rc8 and 17 patches for bug-fix) for rebase the following branch v5.10/standard/preempt-rt/nxp-sdk-5.10/nxp-s32g2xx on NXP SDK bsp31 release(v5.10 kernel), would you please help to merge these patches? The patch infos

[linux-yocto] [linux-yocto std kernel]: nxp-s32g2xx: update linux-yocto to NXP bsp31 release version

Hi Bruce, There are 43 patches(including 25 patches from bsp31 rc5~rc8 and 18 patches for bug-fix) for rebase the following branch v5.10/standard/nxp-sdk-5.10/nxp-s32g2xx on NXP SDK bsp31 release(v5.10 kernel), would you please help to merge these patches? The patch infos as

Re: [linux-yocto] [linux-yocto std kernels]: nxp-s32g2xx: fix

Please ignore this request, I will resend one with a correct subject. Thanks, Zhantao On 2021/12/6 下午3:39, Zhantao Tang wrote: Hi Bruce, There are 43 patches(including 25 patches from bsp31 rc5~rc8 and 18 patches for bug-fix) for rebase the following branch