[yocto] [meta-raspberrypi][PATCH] conf/layer.conf: Remove duplicated BBFILES

From: Robert Yang The following doubles BBFILES for all layers in BBFILE_COLLECTIONS: BBFILES += "${@' '.join('${LAYERDIR}/dynamic-layers/%s/recipes*/*/*.bb' % layer \ for layer in BBFILE_COLLECTIONS.split())}" And most of them are invalid, use

[yocto] esdk configuration issues

y-file } This works fine when building with bitbake, but when building in the ESDK the directory paths have changed. In bitbake, the binaries are placed in ${WORKDIR}/build, but in the SDK the binaries are placed in ${WORKDIR}/. Is there a consistent way to find the build directory? This is u

[yocto] how to intelligently avoid OOM build errors with BB_PRESSURE_MAX_MEMORY?

a colleague is using Wind River Linux and is getting occasional OOM errors when taking advantage of maximum parallelism, so he took the quick way out and dialed things back using BB_NUMBER_THREADS and PARALLEL_MAKE. however, i am aware of the bitbake variables BB_PRESSURE_MAX_{IO,CPU,MEMORY}

[yocto] example where "RDEPENDS" is including a "virtual/" run-time dependency

while the dev manual insists that "virtual/" dependencies are only for build-time deps and not run-time deps, i ran across this example on the meta-intel master branch, under dynamic-layers/openembedded-layer/recipes-oneapi/ (blank lines added for clarity): $ grep -r "RDEPENDS.*virtual/" * com

Re: [yocto] any interest in a YP riscv mailing list?

On 2023-10-13 11:14, Ross Burton wrote: On 13 Oct 2023, at 15:20, Robert P. J. Day via lists.yoctoproject.org wrote: given that other acrhitectures have their own ML, is it reasonable that risc-v have its own mailing list? meta-arm, meta-intel etc are primarily because they take patches via

[yocto] any interest in a YP riscv mailing list?

given that other acrhitectures have their own ML, is it reasonable that risc-v have its own mailing list? rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61333): https://lists.yoctoproject.org/g/yocto/message/61333 Mute This Topic: https://l

Re: [yocto] are there any plans for a RISC-V reference board?

On Fri, 13 Oct 2023, Alexander Kanavin wrote: > Can you clarify please what LTS means here? > > Alex > > On Fri 13. Oct 2023 at 9.09, Robert P. J. Day wrote: > On Tue, 10 Oct 2023, Josef Holzmayr wrote: > > > Hi Robert, > > > It has been

Re: [yocto] are there any plans for a RISC-V reference board?

On Tue, 10 Oct 2023, Josef Holzmayr wrote: > Hi Robert, > It has been discussed at numerous occasions. The main blocker is: we > need a commitment for the maintenance. So if a high-ranking member > decides to push forwards with this and allocate resources, or a new > member

[yocto] Sovereign Tech Fund Boosts Yocto Project

cool ... https://www.linuxfoundation.org/blog/sovereign-tech-fund-boosts-yocto-project rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#61301): https://lists.yoctoproject.org/g/yocto/message/61301 Mute This Topic: https://lists.yoctoproject.org

[yocto] are there any plans for a RISC-V reference board?

at some point, will there be a poky (meta-yocto-bsp) RISC-V reference board? i'm thinking the Nezha Allwinner D1 (which is already supported in meta-riscv) would be a safe choice. or maybe the more powerful VisionFive 2? thoughts? rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages

Re: [yocto] Adding openjdk-11 to Yocto

, Robert > On Mar 27, 2023, at 6:13 AM, Spore, David wrote: > > Hello, > > Just wanted to check if there has been any progress on this. > > Thanks! > > David > > > -Original Message- > From: yocto@lists.yoctoproject.org On Behalf > Of Spor

Re: [yocto] Adding openjdk-11 to Yocto

> On Feb 1, 2023, at 2:26 AM, Richard Leitner wrote: > > Hi, > > On Tue, Jan 31, 2023 at 06:39:08AM -0800, Robert Joslyn wrote: >> >>> On Jan 30, 2023, at 12:27 PM, Richard Leitner >>> wrote: >>> >>> Hi David, >>> unfortun

Re: [yocto] Adding openjdk-11 to Yocto

but obviously there’s tradeoffs to using someones pre-built binary. I can send a patch to add these to meta-java if it would be useful to others. Thanks, Robert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59121): https://lists.yoctoproject.

Re: [yocto] [layerindex-web] [PATCH] layerindex/utils.py: Add to baseconfig=True for bb.parse.handle()

On 12/21/22 00:39, Tim Orling wrote: On Mon, Dec 19, 2022 at 11:26 PM Robert Yang <mailto:liezhi.y...@windriver.com>> wrote: Bitbake's api has been changed via: afb8478d3 parse: Add support for addpylib conf file directive and BB_GLOBAL_PYMODULES The conf

[yocto] [PATCH 1/3] util.py: Fix for removing non-existed dependencies

The previous code didn't work when there is no deps or recs, it would return immediately without removing the on-existed dependencies, this patch fixes the problem. Signed-off-by: Robert Yang --- layerindex/utils.py | 30 +++--- 1 file changed, 19 insertions(+

[yocto] [PATCH 2/3] recipeparse.py: Checkout deplayerbranch before parsing

fixed the problem. Signed-off-by: Robert Yang --- layerindex/recipeparse.py | 1 + 1 file changed, 1 insertion(+) diff --git a/layerindex/recipeparse.py b/layerindex/recipeparse.py index 6202745..6f2da0a 100644 --- a/layerindex/recipeparse.py +++ b/layerindex/recipeparse.py @@ -124,6 +124,7 @

[yocto] [PATCH 3/3] utils.py: Prefer the one which matches branchname for depends layer

meta-xilinx of layer meta-xilinx-bsp does not have branch record for branch master-wr And for build: Layer 'wr-xilinx-zynqmp' depends on layer 'xilinx', but this layer is not enabled in your configuration Prefer the one which matches branchname to fix the problem Signed

[yocto] [layerindex-web] [PATCH] layerindex/utils.py: Add to baseconfig=True for bb.parse.handle()

${LAYERDIR}/lib oe' Signed-off-by: Robert Yang --- layerindex/utils.py | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/layerindex/utils.py b/layerindex/utils.py index 6566710..9d94015 100644 --- a/layerindex/utils.py +++ b/layerindex/utils.py @@ -314,7 +314,10 @@

[yocto] [layerindex-web][PATCH 1/2] utils.py: Fix for is_commit_ancestor()

The runcmd() would print an "ERROR" when failed which caused confusions since the failed is expected on old branches, so subprocess.getstatusoutput to fix the problem. Signed-off-by: Robert Yang --- layerindex/utils.py | 18 ++ 1 file changed, 10 insertions(+), 8

[yocto] [layerindex-web][PATCH 2/2] layerindex/admin.py: Remove has_delete_permission to allow deletion

"patch" and other objects, but has_delete_permission returns False blocks the deletion, so we need remove the local has_delete_permission() to make Branch or LayerBranch can be deleted. The django's default has_delete_permission() will be used after removal. Signed-off-by: Ro

[yocto] [layerindex-web][PATCH] admin.py: Remove has_delete_permission()

owing types of objects: Append distro === This is because has_delete_permission() always return False, remove it to use Django's implementation to fix the problem. Signed-off-by: Robert Yang --- layerindex/admin.py | 17 - 1 file changed, 17 deletions(-) diff --git a/layerinde

[yocto] [layerindex-web][PATCH] utils.py: Fix for is_commit_ancestor()

The runcmd() would print an "ERROR" when failed which caused confusions since the failed is expected on old branches, so subprocess.getstatusoutput to fix the problem. Signed-off-by: Robert Yang --- layerindex/utils.py | 18 ++ 1 file changed, 10 insertions(+), 8

[yocto] [layerindex-web][PATCH] utils.py: Use get_layer_var() to get BBFILE_COLLECTIONS

the problem since it can ignore the extra oe-core from BBFILE_COLLECTIONS. Signed-off-by: Robert Yang --- layerindex/utils.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/layerindex/utils.py b/layerindex/utils.py index efd18e4..ed7fb47 100644 --- a/layerindex/utils.py +++ b

[yocto] meta-riscv layer *seems* to have broken opensbi_%.bbappend file

the SRC_URI line: SRC_URI:append:nezha = " \ ... seems odd since the machine name is actually "nezha-allwinner-d1", not just "nezha". i checked and the two listed patches there don't appear to be applied, for what i assume is just that reason. or is this somehow related to the "nezha.yml"

Re: [yocto] meta-riscv: building curl, "undefined reference to '__atomic_exchange_1'

On Thu, 7 Jul 2022, Khem Raj wrote: > On Thu, Jul 7, 2022 at 1:06 PM Robert P. J. Day wrote: > > > > On Thu, 7 Jul 2022, Khem Raj wrote: > > > > > On Thu, Jul 7, 2022 at 6:14 AM Robert P. J. Day > > > wrote: > > > >

Re: [yocto] meta-riscv: building curl, "undefined reference to '__atomic_exchange_1'

On Thu, 7 Jul 2022, Khem Raj wrote: > On Thu, Jul 7, 2022 at 6:14 AM Robert P. J. Day wrote: > > > > On Thu, 7 Jul 2022, Robert P. J. Day wrote: > > > > > > > on admittedly unsupported ubuntu 22.04 platform but it's clear this > > > is a kno

Re: [yocto] meta-riscv: building curl, "undefined reference to '__atomic_exchange_1'

On Thu, 7 Jul 2022, Khem Raj wrote: > On Thu, Jul 7, 2022 at 6:14 AM Robert P. J. Day wrote: > > > > On Thu, 7 Jul 2022, Robert P. J. Day wrote: > > > > > > > on admittedly unsupported ubuntu 22.04 platform but it's clear this > > > is a kno

Re: [yocto] meta-riscv: building curl, "undefined reference to '__atomic_exchange_1'

On Thu, 7 Jul 2022, Robert P. J. Day wrote: > on admittedly unsupported ubuntu 22.04 platform but it's clear this > is a known issue as it's pretty much identical to what one reads here: > > https://github.com/advancedtelematic/aktualizr/issues/1427 > > the explan

[yocto] meta-riscv: building curl, "undefined reference to '__atomic_exchange_1'

on admittedly unsupported ubuntu 22.04 platform but it's clear this is a known issue as it's pretty much identical to what one reads here: https://github.com/advancedtelematic/aktualizr/issues/1427 the explanation being that, "not every atomic operation is currently supported by GCC on RISC-

[yocto] looking to build meta-riscv based HDMI image for nezha board

after finally unpacking my risc-v nezha SBC, i'm trying to download/build an image that will boot to a desktop with as little effort as possible. that is, given this board, i would prefer to do no more than: * flash appropriate image to micro SD and insert * connect HDMI port to monitor *

[yocto] what's the situation with yocto support for qualcomm qcs{410,610} eval boards?

colleague just asked if i had any useful advice (spoiler: no) on how easy it would be to build a yocto-based image for *some* qcs410-based eval board. i'm familiar with meta-qcom, and machine definitions for dragonboards, but this is clearly(?) different, and i see nothing in the meta-qcom laye

[yocto] simple YP layer to add "snaps" to a YP build

these days, i'm hip-deep in canonical stuff, working with ubuntu core and snaps (boo! hiss! oh, relax ... :-), and i chanced across a somewhat-neglected layer that supports adding snaps to a basic YP build, so i forked a copy, tidied it up, and verified that i can build a core-image-minimal for

Re: [yocto] is there already online the YP summit "hands-on setup"?

On Mon, 16 May 2022, Nicolas Dechesne wrote: > On Mon, May 16, 2022 at 2:17 PM Robert P. J. Day > wrote: > >   i note that one of the first sessions is 15 minutes of "A session to > help people setup their Digital Ocean account." would this lab already >

[yocto] is there already online the YP summit "hands-on setup"?

i note that one of the first sessions is 15 minutes of "A session to help people setup their Digital Ocean account." would this lab already be online somewhere so people can do this ahead of time to make sure nothing goes wrong? rday https://pretalx.com/yocto-project-summit-2022-05/talk/URUNLG

Re: [yocto] a waitlist for YP summit 2022.05?

On Mon, 16 May 2022, Nicolas Dechesne wrote: > On Mon, May 16, 2022 at 11:29 AM Nicolas Dechesne > wrote: > hey Robert, > > On Mon, May 16, 2022 at 11:27 AM Robert P. J. Day > wrote: > >   given that i freed up my schedule for the upcoming week, i zipped

[yocto] a waitlist for YP summit 2022.05?

given that i freed up my schedule for the upcoming week, i zipped over to register for this week's yp virtual summit, but was told i was being placed on a wait list. a wait list for a virtual summit? is there a limit being put on registrations due to technical limitations or something? seems odd

Re: [yocto] are there any plans for meta-riscv support for StarFive VisionFive?

On Thu, 12 May 2022, Khem Raj wrote: > On Thu, May 12, 2022 at 2:00 AM Robert P. J. Day > wrote: > > > https://shop.allnetchina.cn/products/starfive-visionfive-ai-single-board-computer?variant=39522167783526 > > > Yes There already is beagleV machine and it will

[yocto] are there any plans for meta-riscv support for StarFive VisionFive?

https://shop.allnetchina.cn/products/starfive-visionfive-ai-single-board-computer?variant=39522167783526 rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#57063): https://lists.yoctoproject.org/g/yocto/message/57063 Mute This Topic: https://list

Re: [yocto] [Question] How to handle GPLv3 packages?

ar" you have an expensive eval board afterwards. Another interesting issue is the "EU Radio Equipment Directive". It seems to be incompatible with GPLv3[1] ;) [1] https://fsfe.org/activities/radiodirective/radiodirective.en.html Regards,     Matthias -- Robert Berger Embedded

Re: [yocto] Howto build packages for dependencies of an out of image recipe build.

bake --runall build build-essential Robert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56409): https://lists.yoctoproject.org/g/yocto/message/56409 Mute This Topic: https://lists.yoctoproject.org/mt/89659095/21656 Group Owner: yocto+ow...@lists

Re: [yocto] opkg not picking up RPROVIDES alias. #yocto #vivado

foo” to build your package feed, you won’t get all of the packages built. I just had to change how my package feed was generated by using "bitbake --runall build packagegroup-foo” to build my package feed from my packagegroup recipe. I’m not sure if you’re seeing the same i

Re: [yocto] looking to boot core-image-minimal on meta-riscv board

On Fri, 25 Feb 2022, Khem Raj wrote: > On Fri, Feb 25, 2022 at 8:36 AM Robert P. J. Day > wrote: > > > > > > a friend of mine is diving into trying to boot linux on a meta-riscv > > linux starter kit -- he's not using YP, and this is what

[yocto] looking to boot core-image-minimal on meta-riscv board

a friend of mine is diving into trying to boot linux on a meta-riscv linux starter kit -- he's not using YP, and this is what he's targeting: https://www.aliexpress.com/item/1005003751298305.html since i've wanted to jump into meta-riscv for a while, i figured i'd play along and ordered so

Re: [yocto] Building Yocto on M1 Mac

> On Feb 14, 2022, at 4:02 AM, Ross Burton wrote: > > On Mon, 14 Feb 2022 at 00:17, Robert Joslyn > wrote: >> On my 2020 M1 MacBook Air (8 cores, 16 GB RAM, docker using 8 cores and 8 >> GB), the build took 84 minutes. My desktop with an AMD Ryzen 9 3950X (16 >>

Re: [yocto] Building Yocto on M1 Mac

itbake core-image-minimal —runonly=fetch rm -rf tmp/ sstate-cache/ time bitbake core-image-minimal On my 2020 M1 MacBook Air (8 cores, 16 GB RAM, docker using 8 cores and 8 GB), the build took 84 minutes. My desktop with an AMD Ryzen 9 3950X (16 cores, 64 GB RAM) it takes 21 minutes. Docker perf

Re: [yocto] is there a viable YP-friendly risc-v dev kit?

Quoting Leon Woestenberg : Hello Robert, Alexander, On Fri, 4 Feb 2022 at 23:04, Robert P. J. Day wrote: Quoting Alexander Kanavin : > I think the best option at this point is qemu. Why does the 'friend' need > physical hardware? :) he's a hacker and just like

Re: [yocto] is there a viable YP-friendly risc-v dev kit?

Quoting Alexander Kanavin : I think the best option at this point is qemu. Why does the 'friend' need physical hardware? :) he's a hacker and just likes the feel of circuit boards, but qemu does look like the only feasible option at the moment. rday -=-=-=-=-=-=-=-=-=-=-=- Links: You rec

[yocto] is there a viable YP-friendly risc-v dev kit?

friend asked me about the options for a risc-v dev kit that worked with YP, and i'm aware of the meta-riscv layer, but wherever i looked, it seems like risc-v dev kits have a very short life span, being either put on hold or outright cancelled (beaglev, hifive unmatched, etc.) are there, in fact,

Re: [yocto] Additional hardening options

lla.yoctoproject.org/show_bug.cgi?id=14570 Regards, Robert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56040): https://lists.yoctoproject.org/g/yocto/message/56040 Mute This Topic: https://lists.yoctoproject.org/mt/88687579/21656 Group Owner: yocto+ow...@li

Re: [yocto] Packages Missing from Deploy

> On Jan 19, 2022, at 9:17 PM, Robert Joslyn > wrote: > > I’m testing migrating one of my dunfell builds to master in anticipation of > the upcoming LTS, and there is a difference in how packages are populated > into deploy that is causing me problems. My builds use a

[yocto] Packages Missing from Deploy

configure to get the same package generation as dunfell? Thanks, Robert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#55926): https://lists.yoctoproject.org/g/yocto/message/55926 Mute This Topic: https://lists.yoctoproject.org/mt/88553371/21656 Group

Re: [yocto] bbappend usage

On Mon, 25 Oct 2021, Monsees, Steven C (US) via lists.yoctoproject.org wrote: > If I am building an image “image-ABC”, and it is composed of a > number recipes, and for some of these recipes I may NOT want to > install their final components within my image… > > Which is the best place to modify t

Re: [yocto] #dunfell Path to sources in debugfs

f-target:1234 At least in the latest and greatest version this works. I remember a bug a long time ago with some ancient yocto release with cross-debugging, but this was resolved with some upgrade and was certainly older than dunfell. Regards, Robert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive

Re: [yocto] #yocto -third party licensimg

t fancy, since it does not seem to be an open source license, you can mark it also as: LICENSE_FLAGS = "commercial" in the recipe but then you need to whitelist e.g. in your local.conf to be able to bitbake it: # whitelist example recipe, which is under a commercial license LICEN

[yocto] [layerindex-web][PATCH] recipeparse.py: Checkout deplayerbranch before parsing

fixed the problem. Signed-off-by: Robert Yang --- layerindex/recipeparse.py | 1 + 1 file changed, 1 insertion(+) diff --git a/layerindex/recipeparse.py b/layerindex/recipeparse.py index 62c08e91..0870e4f3 100644 --- a/layerindex/recipeparse.py +++ b/layerindex/recipeparse.py @@ -118,6 +118,7 @

Re: [yocto] Pyinstaller error in yocto #yocto

work It misses ldd. It's here: https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-core/glibc/glibc-package.inc You might want to try something like: IMAGE_INSTALL += "ldd" Regards, Robert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this

Re: [yocto] [meta-security][PATCH 1/2] image-with-hardened-binaries: add class

Hi, On 21/08/2021 18:35, Armin Kuster wrote: Regarding the selftest, is there test for failure? I ran this against core-image-minimal and nothing was printed out. Does that mean its fine? You may want to remove the ".py" from python3-checksec.py-native_0.6.1.bb, its not needed. If you run c

Re: [yocto] Cannot build yocto anymore after updating all layers to current dunfell branch tips

ke meta-openembedded incorporated this change into their master branch. So either you need to update all your layers as well, or you need to use meta-openembedded with a branch/commit before the change. Regards, Robert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this grou

Re: [yocto] Install SDK with yocto

want it I suggest to talk to Baumer about it and I am happy to help you and them with the integration. Regards, Robert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#54256): https://lists.yoctoproject.org/g/yocto/message/54256 Mute This

Re: [yocto] [poky] [PATCH] local.conf.sample: disable prelink

g benefit visible in the tests: 0.01s vs 0.1s. Also less CPU usage can be seen. I hope I'll find time to run some test with bootchart. Maybe then we can also see boot time, memory, CPU,... Regards, Robert Alex On Mon, 19 Jul 2021 at 22:58, Robert ber...@yocto.user <mailto:robe

Re: [yocto] [poky] [PATCH] local.conf.sample: disable prelink

ag it along and come up more fine-grained configuration options?" We could e.g. exclude certain files from pre-linking. IMHO cross-prelink still works, but not on exe/libs which were compiled in PIE mode. Regards, Robert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to

[yocto] what's the state of things with pushing the bounds on ASSUME_PROVIDED?

i asked about this once upon a time, so i thought i'd follow up ... given the fairly stable state of recent linux distros, is there any standard for taking advantage of what *should* be robust native tools rather than building them? (i'm ignoring taking advantage of sstate and building SDKs and

Re: [yocto] the downside of parallelism

On Sun, 20 Jun 2021, Robert ber...@yocto.user wrote: > Hi, > > On 20/06/2021 12:55, Robert P. J. Day wrote: > > > >refactoring existing (legacy) code base into more bite-sized > > bitbake recipes to speed up build by taking advantage of 6-core > > (12-thre

Re: [yocto] the downside of parallelism

Hi, On 20/06/2021 12:55, Robert P. J. Day wrote: refactoring existing (legacy) code base into more bite-sized bitbake recipes to speed up build by taking advantage of 6-core (12-thread) dell laptop ... end result is that i get so much parallelism that laptop shuts down from overheating

Re: [yocto] the downside of parallelism

On Sun, 20 Jun 2021, Alexander Kanavin wrote: > This is hardly Yocto's fault: putting a 6 core CPU into a laptop > should be validated by saturating all cores for several hours and > ensuring the cooling and frequency throttling can handle it. Laptop > OEM is trying to be cheap I'd say. > > Alex

[yocto] the downside of parallelism

refactoring existing (legacy) code base into more bite-sized bitbake recipes to speed up build by taking advantage of 6-core (12-thread) dell laptop ... end result is that i get so much parallelism that laptop shuts down from overheating. le *sigh* ... rday -=-=-=-=-=-=-=-=-=-=-=- Links: Yo

[yocto] thoughts on YP-friendly developer laptop?

starting to think about a new laptop that will, among other things, do lots of OE/YP builds, and i'll start with this as the basis for a few questions about hard drives: https://www.dell.com/en-ca/shop/gaming-laptops/g15-ryzen-edition-gaming-laptop/spd/g-series-15-5515-laptop/ng155515_sb_ps25e

Re: [yocto] Extensible SDK of core-image-minimal fails to install

ate a build container and a similar sdk container. I added more information to the bug above. Regards, Robert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#53846): https://lists.yoctoproject.org/g/yocto/message/53846 Mute This Topic:

Re: [yocto] How to switch yocto INIT_MANAGER from systemd to sysvinit #dunfell

On Fri, 28 May 2021, Zoran wrote: > > Tried setting INIT_MANAGER = " sysvinit" in build/conf/local.conf > > Is it INIT_MANAGER = " sysvinit" , or INIT_MANAGER = "sysvinit" (no > blank at the beginning)? > > Thank you, > Zee you don't want the leading space. rday -=-=-=-=-=-=-=-=-=-=-=- Li

Re: [yocto] How to switch yocto INIT_MANAGER from systemd to sysvinit #dunfell

On Thu, 27 May 2021, sayinswa...@gmail.com wrote: > Hello Yocto team: > > I just started with yocto and would like to know the process for switching > the init > manager from systemd to sysvinit. > > I tried this options in config file > VIRTUAL-RUNTIME_init_manager = "busybox" > PREFERRED_PROVID

[yocto] [meta-security][PATCH] Correct "securiyt" typo in maintainers.inc

Signed-off-by: Robert P. J. Day --- diff --git a/conf/distro/include/maintainers.inc b/conf/distro/include/maintainers.inc index 7b82ef7..e02b903 100644 --- a/conf/distro/include/maintainers.inc +++ b/conf/distro/include/maintainers.inc @@ -1,4 +1,4 @@ -# meta-securiyt Maintainers File

[yocto] [meta-gplv2][PATCH] conf/distro: Restore btrfs-tools since it was relicensed

libbtrfsutil was relicensed from LGPL-3.0+ to LGPL-2.1+, so it is no longer necessary to remove btrfs-tools. Signed-off-by: Robert Joslyn --- conf/distro/include/disable-gplv3.inc | 1 - 1 file changed, 1 deletion(-) diff --git a/conf/distro/include/disable-gplv3.inc b/conf/distro/include

Re: [yocto] Recipe Grep'ing

bitbake, I'd love to be able to hand them oe-stylize or something similar and just tell them to run it before committing to make sure everything is formatted consistently. I've had updating oe-stylize.py on my TODO list for a while, but more important things always come up. Robert > -

Re: [yocto] what OE/YP layers should be considered "supported"?

On Tue, 4 May 2021, akuster808 wrote: > Helllo Robert, > > On 5/4/21 2:03 PM, Robert P. J. Day wrote: > > related to something that richard purdie mentioned on the OE list, > > if one wanted to do a YP-wide "cleanup" of some indeterminate form, > > what ar

[yocto] what OE/YP layers should be considered "supported"?

related to something that richard purdie mentioned on the OE list, if one wanted to do a YP-wide "cleanup" of some indeterminate form, what are the layers that would be considered mandatory to cover in such a cleanup? no-brainers would, of course, include: * oe-core * meta-openembedded

Re: [yocto] looking for a bit more info on licensing certain recipe files

On Tue, 4 May 2021, Quentin Schulz wrote: > On Tue, May 04, 2021 at 06:00:10AM -0400, Robert P. J. Day wrote: > > On Tue, 4 May 2021, Quentin Schulz wrote: > > > > > Hi Robert, > > > > > > On Tue, Apr 27, 2021 at 08:41:25AM -0400, Robert P. J. Day wrote:

Re: [yocto] looking for a bit more info on licensing certain recipe files

On Tue, 4 May 2021, Quentin Schulz wrote: > Hi Robert, > > On Tue, Apr 27, 2021 at 08:41:25AM -0400, Robert P. J. Day wrote: > > > > for the first time, i'm digging around in the docs for how to > > properly license various types of recipes, so a couple simple

[yocto] any compelling reason to use SDK rather than eSDK?

colleague wants to get into working with SDKs, and as i'm just diving into the intricacies of that myself, i'm not sure how to answser the question: "is there any reason to use the regular SDK as opposed to the extensible SDK?" superficially, it would seem that the eSDK has nothing but benefi

[yocto] looking for a bit more info on licensing certain recipe files

for the first time, i'm digging around in the docs for how to properly license various types of recipes, so a couple simple questions to start with, at least so i can make a first pass of cleaning up some content in front of me. as we established recently, packagegroup files need no licensing

Re: [yocto] [meta-gplv2] [PATCH] conf/distro: Add removal of btrfs-tools from util-linux ptest depends

builds. I’ll keep an eye out for the next upstream release which should allow this patch to be reverted. Thanks, Robert > On Apr 19, 2021, at 2:29 PM, Ross Burton wrote: > > +1. > > Ross > > On Mon, 19 Apr 2021 at 21:47, Richard Purdie > wrote: >> >> bt

[yocto] what to include in a "hardware bringup image"?

for a current project (and subsequent projects), i want to define a hardware bringup image; that is, a really basic image chock-full of low-level utilities for debugging initial board bringup. this means precious little unnecessary userspace crud that has no value in that context. (at the moment

Re: [yocto] #golang: go fetches dependencies in compile phase

Hi, My comments are inline. On 12/04/2021 14:47, Juergen Landwehr wrote: Hi Robert, thanks for your thoughts. I see your point and the last thing I want is "NOT reproducable builds". But dependency management in go is not that arbitrary as it may seem. ... if everybody does wha

Re: [yocto] #golang: go fetches dependencies in compile phase

owed to combine the licenses and in case it's allowed what are implications of GPLvx, LGPLv2, LGPLv3 without exceptions for your product. [1] https://www.yoctoproject.org/pipermail/yocto/2017-March/035028.html Regards, Robert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to th

Re: [yocto] bitbake controlling memory use

like memory. Do you use a build container? It uses cgroups underneath. e.g. docker: https://docs.docker.com/config/containers/resource_constraints/ Regards, Robert -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#53076): https

[yocto] is there a *compelling* use case for "FILESEXTRAPATHS_append"?

over the years, i've always been uncomfortable with the admittedly small number of examples in various layers i've found that append to FILESEXTRAPATHS rather than prepend, so i'm curious if there is an actual, persuasive reason to ever do that. philosophically, when one uses FILESEXTRAPATHS_

[yocto] does meta-virtualization layer have superfluous dynamic layers stuff?

just noticed this is meta-virt layer, file layer.conf: # The dynamic-layers directory hosts extensions and layer-specific # modifications. # # The .bbappend and .bb files are included if the respective layer # collection is available. BBFILES += "${@' '.join('${LAYERDIR}/dynamic-layers/%s/recip

[yocto] where is the definitive/canonical layer for TPM stuff?

i just noticed that both of the layers meta-secure-core and meta-security: https://github.com/jiazhang0/meta-secure-core https://git.yoctoproject.org/cgit/cgit.cgi/meta-security seem to include a good deal of TPM/TPM2 content ... is there a primary layer for that stuff? rday -=-=-=-=-=-=-=-=

[yocto] what is the state of upcoming(?) NXP S32G2xx support; layer, BSP?

i note that the linux-yocto repo has a nxp-s32g2xx branch: https://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/commit/?h=v5.10/standard/nxp-sdk-5.4/nxp-s32g2xx so wondering about the subsequent BSP layer, from NXP or elsewhere. thoughts? rday -=-=-=-=-=-=-=-=-=-=-=- Links: You receive al

Re: [yocto] is there a recent explanation of tricks you can play with MACHINEOVERRIDES?

On Sat, 20 Mar 2021, Quentin Schulz wrote: > Hi Robert, > > On March 19, 2021 9:54:34 AM UTC, "Robert P. J. Day" > wrote: > > > > years ago, i asked about how to support a small set of > >closely-related targets using MACHINEOVERRIDES to defin

Re: [yocto] does current bitbaking of core-image-minimal still need docbook stuff?

...@topicproducts.com > W: www.topic.nl > > Please consider the environment before printing this e-mail > On 19-03-2021 11:45, Robert P. J. Day via lists.yoctoproject.org wrote: > > On Fri, 19 Mar 2021, Nicolas Dechesne wrote: > > > >> On Fri, Mar 19, 2021 at 10:47 AM Robe

Re: [yocto] does current bitbaking of core-image-minimal still need docbook stuff?

On Fri, 19 Mar 2021, Nicolas Dechesne wrote: > On Fri, Mar 19, 2021 at 10:47 AM Robert P. J. Day > wrote: > > > > > > testing building qemuarm64 core-image-minimal from scratch, and > > noticed it fetching for docbook-xml and docbook-xsl stuff ... is there

[yocto] is there a recent explanation of tricks you can play with MACHINEOVERRIDES?

that? and is this sort of thing worth expanding on and adding to one of the manuals? rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca LinkedIn

[yocto] does current bitbaking of core-image-minimal still need docbook stuff?

testing building qemuarm64 core-image-minimal from scratch, and noticed it fetching for docbook-xml and docbook-xsl stuff ... is there something that still needs docbook support? i'm about to take a quick look to see what's demanding that, does anyone know? rday -=-=-=-=-=-=-=-=-=-=-=- Links:

Re: [yocto] Recipes and meta-data directory tree

On Wed, 17 Mar 2021, keydi wrote: > Two projects are given. They use different YP release each. > Projects use also different target platform each. ... snip ... > project B (YP release 2.0, actually backport of some later release you can't legitimately expect support for YP 2.0, which is six

Re: [yocto] Building test code?

On Tue, 16 Mar 2021, jchludzinski via lists.yoctoproject.org wrote: > I tried to build spidev-test using the bitbake recipe:  > > spidev-test.bb >   > I set: > ARCH=arm > BBPATH > CROSS_COMPILER=arm-linux-gnueabihf- > PATH > > ... and then tried to build spidev-test: > > $ bitbake -b spidev-test.b

Re: [yocto] how often would one use "VAR_someoverride_append = ..."?

On Wed, 10 Mar 2021, Quentin Schulz wrote: ... snip ... > https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-kernel/linux/linux-yocto_5.10.bb#n12 > for example. > > This is an example of a "valid" use case (not that there are invalid > ones) for VAR_foo. > > Would probably a better

Re: [yocto] how often would one use "VAR_someoverride_append = ..."?

On Tue, 9 Mar 2021, Quentin Schulz wrote: > Hi Robert, > > On Tue, Mar 09, 2021 at 09:39:14AM -0500, Robert P. J. Day wrote: > > > > bitbake manual, chapter 3, examples of conditional syntax: > > > > https://docs.yoctoproject.org/bitbake/bitbake-user-manual/

[yocto] konrad has officially blessed his new meta-rubygems layer

inspired by my earlier plaintive mewling of "gosh, i wish YP had better ruby support," konrad weihmann put in a ridiculous amount of work and came up with: https://github.com/priv-kweihmann/meta-rubygems while i am listed as a contributor, konrad has done 98% of the work, and i really plan o

[yocto] what version of YP will next wind river (LTS20) be based on?

i suspect i know the answer, just want to confirm ... friend tells me yesterday he's working with LTS20, i said, "uh, that's not even out yet," he assures he his company has an early release, but he couldn't tell me what version of YP it corresponded to. based on regularity of releases on bot

Re: [yocto] how often would one use "VAR_someoverride_append = ..."?

On Tue, 9 Mar 2021, Quentin Schulz wrote: > Hi Robert, > > On Tue, Mar 09, 2021 at 09:39:14AM -0500, Robert P. J. Day wrote: > > > > bitbake manual, chapter 3, examples of conditional syntax: > > > > https://docs.yoctoproject.org/bitbake/bitbake-user-manual/

  1   2   3   >