|
Re: #kirkstone efivar build failed
#kirkstone
Related: https://github.com/rhboot/efivar/issues/220
Related: https://github.com/rhboot/efivar/issues/220
|
By
Tim Orling
·
#58327
·
|
|
#kirkstone efivar build failed
#kirkstone
Hello guys,
I'm trying to use `QT6` and `Boot2QT` meta layer and I noticed that `ld-is-gold` is used in `DISTRO_FEATURES`
This build of efivar failed. Please see the logs below.
gcc
Hello guys,
I'm trying to use `QT6` and `Boot2QT` meta layer and I noticed that `ld-is-gold` is used in `DISTRO_FEATURES`
This build of efivar failed. Please see the logs below.
gcc
|
By
Ilies CHERGUI
·
#58326
·
|
|
Re: Dealing with go dependencies in recipes - native docker-compose
Adding the missing setuptools does get things working.
I actually have a prototype recipe for this that I was working on before ELCe, but I didn't get it into meta-virtualization yet, as it had a
Adding the missing setuptools does get things working.
I actually have a prototype recipe for this that I was working on before ELCe, but I didn't get it into meta-virtualization yet, as it had a
|
By
Bruce Ashfield
·
#58325
·
|
|
# honister #systemd attempting to run script on boot...
#systemd
I am trying to make use of system to run a test script at boot…
I can exercise my test_script/test_script.service manually using systemctl commands and it appears to work as expects.
I created
I am trying to make use of system to run a test script at boot…
I can exercise my test_script/test_script.service manually using systemctl commands and it appears to work as expects.
I created
|
By
Monsees, Steven C (US)
·
#58324
·
|
|
Dealing with go dependencies in recipes - native docker-compose
Today I realized, that the docker-compose in the meta-virtualization
layer is the old python3 based one and a native solution is available. I
tried to make a recipe for it to get rid of python3 (no
Today I realized, that the docker-compose in the meta-virtualization
layer is the old python3 based one and a native solution is available. I
tried to make a recipe for it to get rid of python3 (no
|
By
Konstantin Kletschke
·
#58323
·
|
|
Re: How to create symlink while installing binary in recipe?
Looks ok perhaps you want to double check using lnr we have dropped
its usage in master but I am not sure if hardknott needs it or not. I
would simily use
ln -sf test ${D}/usr/bin/test-x
and avoid
Looks ok perhaps you want to double check using lnr we have dropped
its usage in master but I am not sure if hardknott needs it or not. I
would simily use
ln -sf test ${D}/usr/bin/test-x
and avoid
|
By
Khem Raj
·
#58322
·
|
|
How to create symlink while installing binary in recipe?
Hello All,
I have a simple recipe in which a binary is installed to /usr/bin/. Now, I want to establish a symlink to same binary also. I am using hardknott release
do_install () {
install -d
Hello All,
I have a simple recipe in which a binary is installed to /usr/bin/. Now, I want to establish a symlink to same binary also. I am using hardknott release
do_install () {
install -d
|
By
Sourabh Hegde
·
#58321
·
|
|
Yocto Project Status 11 October 2022 (WW41)
Current Dev Position: YP 4.1 M4 (In TSC Review)
Next Deadline: 28th October 2022 YP 4.1 Release
Next Team Meetings:
Bug Triage meeting Thursday October 13th 7:30 am PDT
Current Dev Position: YP 4.1 M4 (In TSC Review)
Next Deadline: 28th October 2022 YP 4.1 Release
Next Team Meetings:
Bug Triage meeting Thursday October 13th 7:30 am PDT
|
By
Stephen Jolley
·
#58320
·
|
|
Re: [meta-zephyr][kirkstone][PATCH] nrf52840-mdk-usb-dongle.conf: Add new machine from makerdiary
Hi Philippe,
nrf52840-mdk-usb-dongle board is not supported in Zephyr 3.0 [in Kirkstone]. It's available in Zephyr 3.1
Hi Philippe,
nrf52840-mdk-usb-dongle board is not supported in Zephyr 3.0 [in Kirkstone]. It's available in Zephyr 3.1
|
By
Naveen Saini
·
#58319
·
|
|
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-4.1.rc2)
Hi All,
QA for yocto-4.1.rc2 is completed. This is the full report for this release:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=======
Hi All,
QA for yocto-4.1.rc2 is completed. This is the full report for this release:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
=======
|
By
Jing Hui Tham
·
#58318
·
|
|
M+ & H bugs with Milestone Movements WW10
All,
YP M+ or high bugs which moved to a new milestone in WW41 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
12723
mysql requires unicode and char
All,
YP M+ or high bugs which moved to a new milestone in WW41 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
12723
mysql requires unicode and char
|
By
Stephen Jolley
·
#58317
·
|
|
Enhancements/Bugs closed WW41!
All,
The below were the owners of enhancements or bugs closed during the last week!
Who
Count
michael.opdenacker@...
2
randy.macleod@...
1
mhalstead@...
1
Grand Total
4
Thanks,
Stephen
All,
The below were the owners of enhancements or bugs closed during the last week!
Who
Count
michael.opdenacker@...
2
randy.macleod@...
1
mhalstead@...
1
Grand Total
4
Thanks,
Stephen
|
By
Stephen Jolley
·
#58316
·
|
|
Current high bug count owners for Yocto Project 4.1
All,
Below is the list as of top 32 bug owners as of the end of WW41 of who have open medium or higher bugs and enhancements against YP 4.1. There are 13 possible work days left until the final
All,
Below is the list as of top 32 bug owners as of the end of WW41 of who have open medium or higher bugs and enhancements against YP 4.1. There are 13 possible work days left until the final
|
By
Stephen Jolley
·
#58315
·
|
|
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
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
|
By
Stephen Jolley
·
#58314
·
|
|
Re: [meta-zephyr][PATCH 1/6] zephyr-bsp: add support for qemu-cortex-a9
While running qemu, it throws following error:
runqemu - ERROR - Failed to run qemu: qemu-system-arm: -device virtio-rng-pci,rng=rng0: No 'PCI' bus found for device 'virtio-rng-pci'
While running qemu, it throws following error:
runqemu - ERROR - Failed to run qemu: qemu-system-arm: -device virtio-rng-pci,rng=rng0: No 'PCI' bus found for device 'virtio-rng-pci'
|
By
Naveen Saini
·
#58313
·
|
|
Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.20.rc2)
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.20.rc2. We are planning to execute following tests for this cycle:
OEQA-manual tests for following module:
1.
Hi all,
Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.20.rc2. We are planning to execute following tests for this cycle:
OEQA-manual tests for following module:
1.
|
By
Jing Hui Tham
·
#58312
·
|
|
Re: QA notification for completed autobuilder build (yocto-3.1.20.rc2)
We happened to hit another known autobuilder intermittent issue on the
qemuppc build:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14824
The worker happened to be heavily loaded at the time,
We happened to hit another known autobuilder intermittent issue on the
qemuppc build:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14824
The worker happened to be heavily loaded at the time,
|
By
Steve Sakoman
·
#58311
·
|
|
QA notification for completed autobuilder build (yocto-3.1.20.rc2)
A build flagged for QA (yocto-3.1.20.rc2) was completed on the autobuilder and is available at:
https://autobuilder.yocto.io/pub/releases/yocto-3.1.20.rc2
Build hash information:
bitbake:
A build flagged for QA (yocto-3.1.20.rc2) was completed on the autobuilder and is available at:
https://autobuilder.yocto.io/pub/releases/yocto-3.1.20.rc2
Build hash information:
bitbake:
|
By
Pokybuild User <pokybuild@...>
·
#58310
·
|
|
Re: [PATCH yocto-autobuilder-helper] scripts: run-docs-build: make the workdir pristine between builds
Hi Quentin,
Quentin Schulz <quentin.schulz@...> wrote:
Sorry for the delayed reply. It took a while before I found a little
time to look at the script code...
Indeed cleaning
Hi Quentin,
Quentin Schulz <quentin.schulz@...> wrote:
Sorry for the delayed reply. It took a while before I found a little
time to look at the script code...
Indeed cleaning
|
By
Luca Ceresoli
·
#58309
·
|
|
Re: QA notification for completed autobuilder build (yocto-.rc1)
Richard let me know that a missing release number will result in a
broken build for QA, so I will run a 3.1.20-rc2 build with this
corrected.
Again, sorry for the confusion.
Steve
On Mon, Oct 10,
Richard let me know that a missing release number will result in a
broken build for QA, so I will run a 3.1.20-rc2 build with this
corrected.
Again, sorry for the confusion.
Steve
On Mon, Oct 10,
|
By
Steve Sakoman
·
#58308
·
|