|
Kirkstone Upgrade now gives RDEPENDS error with /usr/bin/python
#python
#kirkstone
Good Afternoon, I am updating a project from Honister to Kirkstone, Has anyone else run into an issue with python files with a #!/usr/bin/python header throwing the (abbreviated) Error below? This did
Good Afternoon, I am updating a project from Honister to Kirkstone, Has anyone else run into an issue with python files with a #!/usr/bin/python header throwing the (abbreviated) Error below? This did
|
By
bgctkd@...
·
|
|
Mini-Summit in Dublin: Hands on with the Yocto Project
Howdy there! We're happy to finally announce the Yocto Project Mini-Summit taking place the day before ELC-E in Dublin! Monday, September 12th, 2022 | 2:00 – 5:30 PM Location: Convention Centre Dublin
Howdy there! We're happy to finally announce the Yocto Project Mini-Summit taking place the day before ELC-E in Dublin! Monday, September 12th, 2022 | 2:00 – 5:30 PM Location: Convention Centre Dublin
|
By
Josef Holzmayr
·
|
|
Recipe with kernel configuration fragment 2 messages
Hi, For a firewall recipe using nftables we need to make some kernel configuration changes. At first we added the needed CONFIG_ lines to a bbappend in the recipes-kernel directory of our own layer, b
Hi, For a firewall recipe using nftables we need to make some kernel configuration changes. At first we added the needed CONFIG_ lines to a bbappend in the recipes-kernel directory of our own layer, b
|
By
Maik Vermeulen
·
|
|
How to insure SRCREV is consistent with PV 4 messages
Hi Since the last version of bibake it looks like SRCREV must be set with a SHA1 in order to fetch source from a git repository. We previously set it with a tag corresponding to PV. Manually retrievin
Hi Since the last version of bibake it looks like SRCREV must be set with a SHA1 in order to fetch source from a git repository. We previously set it with a tag corresponding to PV. Manually retrievin
|
By
Philippe Midol-Monnet
·
|
|
#kirkstone qemu
#kirkstone
Hello: I built kirkstone core-image-sato from scratch no modifications, clean build was going test kirkstone out… When I went to run using qemu I saw the following issue with “tun”, even after a manua
Hello: I built kirkstone core-image-sato from scratch no modifications, clean build was going test kirkstone out… When I went to run using qemu I saw the following issue with “tun”, even after a manua
|
By
Monsees, Steven C (US)
·
|
|
Yocto Project Status 9 August 2022 (WW32)
Current Dev Position: YP 4.1 M3 Next Deadline: 22nd August 2022 YP 4.1 M3 Build Next Team Meetings: Bug Triage meeting Thursday August 11th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y
Current Dev Position: YP 4.1 M3 Next Deadline: 22nd August 2022 YP 4.1 M3 Build Next Team Meetings: Bug Triage meeting Thursday August 11th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y
|
By
Richard Purdie
·
|
|
Enhancements/Bugs closed WW32!
All, The below were the owners of enhancements or bugs closed during the last week! Who Count richard.purdie@... 1 randy.macleod@... 1 Grand Total 2 Thanks, Stephen K. Jolley Yocto Project Program Man
All, The below were the owners of enhancements or bugs closed during the last week! Who Count richard.purdie@... 1 randy.macleod@... 1 Grand Total 2 Thanks, Stephen K. Jolley Yocto Project Program Man
|
By
Stephen Jolley
·
|
|
Current high bug count owners for Yocto Project 4.1
All, Below is the list as of top 37 bug owners as of the end of WW32 of who have open medium or higher bugs and enhancements against YP 4.1. There are 57 possible work days left until the final releas
All, Below is the list as of top 37 bug owners as of the end of WW32 of who have open medium or higher bugs and enhancements against YP 4.1. There are 57 possible work days left until the final releas
|
By
Stephen Jolley
·
|
|
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
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
|
By
Stephen Jolley
·
|
|
[meta-security][PATCH V2] meta-security: Add recipe for Glome
From: John Edward Broadbent <jebr@...> Generic Low Overhead Message Exchange (GLOME) is a protocol providing secure authentication and authorization for low dependency environments. Signed-off-by: Joh
From: John Edward Broadbent <jebr@...> Generic Low Overhead Message Exchange (GLOME) is a protocol providing secure authentication and authorization for low dependency environments. Signed-off-by: Joh
|
By
John Broadbent
·
|
|
[meta-security][PATCH] meta-security: Add recipe for Glome 2 messages
From: John Edward Broadbent <jebr@...> Generic Low Overhead Message Exchange (GLOME) is a protocol providing secure authentication and authorization for low dependency environments. Signed-off-by: Joh
From: John Edward Broadbent <jebr@...> Generic Low Overhead Message Exchange (GLOME) is a protocol providing secure authentication and authorization for low dependency environments. Signed-off-by: Joh
|
By
John Broadbent
·
|
|
How to add INCOMPATIBLE_LICENSE only for one image? 2 messages
#bitbake
#dunfell
Hi, I've two image recipes (foo.bb & bar.bb). I want to add INCOMPATIBLE_LICENSE="GPLv3" only in foo.bb & not bar.bb Adding INCOMPATIBLE_LICENSE="GPLv3" in local.conf is applying it on both the images
Hi, I've two image recipes (foo.bb & bar.bb). I want to add INCOMPATIBLE_LICENSE="GPLv3" only in foo.bb & not bar.bb Adding INCOMPATIBLE_LICENSE="GPLv3" in local.conf is applying it on both the images
|
By
Priyanshu Sharma
·
|
|
binutils not compiling in my system (Ubuntu 18.04) 2 messages
#dunfell
Hi I am working on a custom board , which i develop bsp based on a poky(dunfell). Iam unable to build the basic core-image-minimal(with out adding any of our custom layers and beaglebone-yocto as MACH
Hi I am working on a custom board , which i develop bsp based on a poky(dunfell). Iam unable to build the basic core-image-minimal(with out adding any of our custom layers and beaglebone-yocto as MACH
|
By
Sethu Madhav
·
|
|
[layerindex-web][PATCH] admin.py: Remove has_delete_permission()
The following commit has added on_delete=models.CASCADE to the ForeignKey: === commit 2d526f9b0d363f3e442abc97ef9bd9fab37ee5e4 Author: Amber Elliot <amber.n.elliot@...> Date: Thu Jun 25 15:57:34 2020
The following commit has added on_delete=models.CASCADE to the ForeignKey: === commit 2d526f9b0d363f3e442abc97ef9bd9fab37ee5e4 Author: Amber Elliot <amber.n.elliot@...> Date: Thu Jun 25 15:57:34 2020
|
By
Robert Yang
·
|
|
Binutils Error during compiling
Hi I am working on a custom board , which i develop bsp based on a poky(dunfell). Iam unable to build the basic core-image-minimal(with out adding any of our custom layers and beaglebone-yocto as MACH
Hi I am working on a custom board , which i develop bsp based on a poky(dunfell). Iam unable to build the basic core-image-minimal(with out adding any of our custom layers and beaglebone-yocto as MACH
|
By
Sethu Madhav
·
|
|
error: package target-sdk-provides-dummy-1.0-r0.sdk_provides_dummy_target is intended for a different architecture
Hi. I'm trying to add python3-pyelftools to SDK, I added "nativesdk" to BBCLASSEXTEND and added "nativesdk-python3-pyelftools" to TOOLCHAIN_HOST_TASK. When running bitbake -c populate_sdk results in t
Hi. I'm trying to add python3-pyelftools to SDK, I added "nativesdk" to BBCLASSEXTEND and added "nativesdk-python3-pyelftools" to TOOLCHAIN_HOST_TASK. When running bitbake -c populate_sdk results in t
|
By
Ramon Fried
·
|
|
Getting Error while trying to run graphical yocto build image 2 messages
#yocto
#linux
#dunfell
#qemu
Hello Everyone here, I want to run the graphic image of qemux86-64 which I have built with yocto. When I am running command "runqemu qemux86-64" or "runqemu" or "runqemu core-image-minimal" I am getti
Hello Everyone here, I want to run the graphic image of qemux86-64 which I have built with yocto. When I am running command "runqemu qemux86-64" or "runqemu" or "runqemu core-image-minimal" I am getti
|
By
Nikita Gupta
·
|
|
[meta-zephyr][PATCH 3/3] zephyr-kernel: Checkout zephyr in subdir to match West usage
From: Peter Hoyes <Peter.Hoyes@...> When using West, Zephyr is checked out in a "zephyr" subdirectory of the working directory. At the moment Zephyr is checked out at the root, meaning a workaround is
From: Peter Hoyes <Peter.Hoyes@...> When using West, Zephyr is checked out in a "zephyr" subdirectory of the working directory. At the moment Zephyr is checked out at the root, meaning a workaround is
|
By
Peter Hoyes
·
|
|
[meta-zephyr][PATCH 2/3] zephyr-kernel: Use ZEPHYR_BASE in all application recipes
From: Peter Hoyes <Peter.Hoyes@...> Change ${S} -> ${ZEPHYR_BASE} in all application recipes, as Zephyr might not always be found at the root of the source directory. Signed-off-by: Peter Hoyes <Peter
From: Peter Hoyes <Peter.Hoyes@...> Change ${S} -> ${ZEPHYR_BASE} in all application recipes, as Zephyr might not always be found at the root of the source directory. Signed-off-by: Peter Hoyes <Peter
|
By
Peter Hoyes
·
|
|
[meta-zephyr][PATCH 1/3] zephyr-kernel: Remove redundant ZEPHYR_BASE definitions
From: Peter Hoyes <Peter.Hoyes@...> zephyr-image.inc and zephyr-sample.inc both include zephyr-kernel-common.inc, which already defines ZEPHYR_BASE. Remove the redundant definitions. Also, pass -DZEPH
From: Peter Hoyes <Peter.Hoyes@...> zephyr-image.inc and zephyr-sample.inc both include zephyr-kernel-common.inc, which already defines ZEPHYR_BASE. Remove the redundant definitions. Also, pass -DZEPH
|
By
Peter Hoyes
·
|