|
Re: LInker Errors: Cannot find crti.o/crtbeginS.o. No such file or directory.
#honister
#make
#yocto
#!/bin/sh
__BITBAKE_LAST_LINE=0
# Emit a useful diagnostic if something fails:
bb_sh_exit_handler() {
ret=$?
if [ "$ret" != 0 ]; then
echo "WARNING: exit code $ret from a shell
#!/bin/sh
__BITBAKE_LAST_LINE=0
# Emit a useful diagnostic if something fails:
bb_sh_exit_handler() {
ret=$?
if [ "$ret" != 0 ]; then
echo "WARNING: exit code $ret from a shell
|
By
douglas.cooper1@...
·
#57412
·
|
|
Re: Yocto Windows SDK with meta-qt6
Ansar, also please include the bblayers.conf file.
Sakib
Ansar, also please include the bblayers.conf file.
Sakib
|
By
sakib.sajal@...
·
#57411
·
|
|
Re: Regression in rust-cross-canadian-aarch64
Sundeep and/or Naveen please take a look.
Peter,
Please open a Yocto bug and document the steps to reproduce the error.
../Randy
--
# Randy MacLeod
# Wind River Linux
Sundeep and/or Naveen please take a look.
Peter,
Please open a Yocto bug and document the steps to reproduce the error.
../Randy
--
# Randy MacLeod
# Wind River Linux
|
By
Randy MacLeod
·
#57410
·
|
|
OpenEmbedded Happy Hour June 29 9pm/2100 UTC
All,
You are cordially invited to the next OpenEmbedded Happy Hour on June 29
for Europe/Americas time zones @ 2100/9pm UTC (5pm ET / 2pm
All,
You are cordially invited to the next OpenEmbedded Happy Hour on June 29
for Europe/Americas time zones @ 2100/9pm UTC (5pm ET / 2pm
|
By
Tim Orling
·
#57409
·
|
|
Yocto Project Status 28 June 2022 (WW26)
Current Dev Position: YP 4.1 M2
Next Deadline: 11th July 2022 YP 4.1 M2 Build
Next Team Meetings:
Bug Triage meeting Thursday June 30th 7:30 am PDT
Current Dev Position: YP 4.1 M2
Next Deadline: 11th July 2022 YP 4.1 M2 Build
Next Team Meetings:
Bug Triage meeting Thursday June 30th 7:30 am PDT
|
By
Stephen Jolley
·
#57408
·
|
|
Re: [OE-core] Announcing pkgexp
Understood, this definitely makes sense. Forget it!
Cheers
Michael
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
Understood, this definitely makes sense. Forget it!
Cheers
Michael
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
|
By
Michael Opdenacker
·
#57407
·
|
|
Re: [OE-core] Announcing pkgexp
The immediate problem with that is that for some packages, like libc, the reverse depends list can be huuuuge. If the page is redesigned to have scrollable regions then sure. That would likely
The immediate problem with that is that for some packages, like libc, the reverse depends list can be huuuuge. If the page is redesigned to have scrollable regions then sure. That would likely
|
By
Ross Burton
·
#57406
·
|
|
Re: [OE-core] Announcing pkgexp
Hi Ross
Hey, this looks very nice and very easy to use!
One minor complaint, though: the "What Depends on" button didn't immediately catch my eye.
Would it be possible to show such reverse
Hi Ross
Hey, this looks very nice and very easy to use!
One minor complaint, though: the "What Depends on" button didn't immediately catch my eye.
Would it be possible to show such reverse
|
By
Michael Opdenacker
·
#57405
·
|
|
Re: Yocto Windows SDK with meta-qt6
CC'd the mailing list
Can you check if it works without any additional layers? Also would it be possible to get your local.conf?
CC'd the mailing list
Can you check if it works without any additional layers? Also would it be possible to get your local.conf?
|
By
Joshua Watt
·
#57404
·
|
|
Announcing pkgexp
Hi,
I’ve just released the first release of pkgexp, a tool to explore the pkgdata that has been generated in a build. Quoting from the README:
pkgexp is a tool to visually explore the
Hi,
I’ve just released the first release of pkgexp, a tool to explore the pkgdata that has been generated in a build. Quoting from the README:
pkgexp is a tool to visually explore the
|
By
Ross Burton
·
#57403
·
|
|
Re: yocto support
If the change is private to you, then you can make a simple layer and
make all the needed modifications there. Is this not possible?
Alex
<arasilinux1086@...> wrote:
If the change is private to you, then you can make a simple layer and
make all the needed modifications there. Is this not possible?
Alex
<arasilinux1086@...> wrote:
|
By
Alexander Kanavin
·
#57402
·
|
|
yocto support
Dear All
Good Morning!
In my project, I am trying to create one custom image recipe in my yocto build system.
The reason of creating custom image is -> having few specific configurations for
Dear All
Good Morning!
In my project, I am trying to create one custom image recipe in my yocto build system.
The reason of creating custom image is -> having few specific configurations for
|
By
Senthamilarasi mathiyan
·
#57401
·
|
|
Re: Regression in rust-cross-canadian-aarch64
I've spent an age staring at this code this morning. I don't think
cross-canadian has ever worked properly. It might happen that some
combinations build but there are also some that don't and clearly
I've spent an age staring at this code this morning. I don't think
cross-canadian has ever worked properly. It might happen that some
combinations build but there are also some that don't and clearly
|
By
Richard Purdie
·
#57400
·
|
|
Re: Regression in rust-cross-canadian-aarch64
Thanks for suggestion! Yes, that will solve the problem for my setup. I was just wondering if you had any purpose with this if-else clause that should be kept or fixed?
I can send a patch for this to
Thanks for suggestion! Yes, that will solve the problem for my setup. I was just wondering if you had any purpose with this if-else clause that should be kept or fixed?
I can send a patch for this to
|
By
Peter Bergin
·
#57399
·
|
|
Re: Regression in rust-cross-canadian-aarch64
I'm wondering if we need something like:
diff --git a/meta/recipes-devtools/rust/rust-common.inc b/meta/recipes-devtools/rust/rust-common.inc
index 621cd4ad576..ef70c48d0f4 100644
---
I'm wondering if we need something like:
diff --git a/meta/recipes-devtools/rust/rust-common.inc b/meta/recipes-devtools/rust/rust-common.inc
index 621cd4ad576..ef70c48d0f4 100644
---
|
By
Richard Purdie
·
#57398
·
|
|
Re: Regression in rust-cross-canadian-aarch64
Hi again,
some progress on this issue.
The reason for this issue seems to be this commit:
commit 781eaa955dce5deab47371c25dae72b36c011900
Author: Richard Purdie
Hi again,
some progress on this issue.
The reason for this issue seems to be this commit:
commit 781eaa955dce5deab47371c25dae72b36c011900
Author: Richard Purdie
|
By
Peter Bergin
·
#57397
·
|
|
M+ & H bugs with Milestone Movements WW26
All,
YP M+ or high bugs which moved to a new milestone in WW26 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
10820
devtool: -d/--debug doesn't show
All,
YP M+ or high bugs which moved to a new milestone in WW26 are listed below:
Priority
Bug ID
Short Description
Changer
Owner
Was
Became
Medium+
10820
devtool: -d/--debug doesn't show
|
By
Stephen Jolley
·
#57396
·
|
|
Enhancements/Bugs closed WW26!
All,
The below were the owners of enhancements or bugs closed during the last
All,
The below were the owners of enhancements or bugs closed during the last
|
By
Stephen Jolley
·
#57395
·
|
|
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 WW26 of who have open medium or higher bugs and enhancements against YP 4.1. There are 86 possible work days left until the final
All,
Below is the list as of top 37 bug owners as of the end of WW26 of who have open medium or higher bugs and enhancements against YP 4.1. There are 86 possible work days left until the final
|
By
Stephen Jolley
·
#57394
·
|
|
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
·
#57393
·
|