Date   

Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley
 

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:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project.  If anyone can help, please take ownership of the bug and send patches!  If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 343 unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out with these.  Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.  There are also roughly four different "priority" classes right now, “3.2”, “3.3, "3.99" and "Future", the more pressing/urgent issues being in "3.2" and then “3.3”.

 

Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).  The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Re: Prevent WIC image from being built?

Bruce Ashfield
 

On Mon, Dec 28, 2020 at 7:12 PM Howard <howard.egan@...> wrote:

Hi:

Was wondering if there was a way to exclude wic image from being built.
If you remove "wic" from the IMAGE_TYPES, it won't be built.

https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-IMAGE_TYPES

Bruce

Many thanks, and Happy New year.
Howard


--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II


Re: How to develop kernel modules on the target?

Bruce Ashfield
 

On Mon, Dec 28, 2020 at 2:06 PM p32 via lists.yoctoproject.org
<p32=tuta.io@...> wrote:

Hello,

The execution of "make scripts prepare" did actually solve the issue, thank you very much for your help!

However, the need to manually execute this command on the target platform made me look into the kernel-devsrc recipe (https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-kernel/linux/kernel-devsrc.bb?h=zeus) to see if it is possible to let the build host execute this step. Some comments imply that this is the case. Consider, for instance, the one in line 257:

Ensure we don't race against "make scripts" during cpio

Unfortunately, I was unable to figure out how to do this. Is there a way to let the recipe trigger this step automatically?
Nope. There is no way to do this on the build host. Not without
complex use of qemu-user to generate and package for the target
architecture. We cannot package the output of scripts in the target
package, since it matches the host architecture and this will trigger
a QA error.

If you happen to be x86 build host and x86 target (or ARM/ARM), you
can partially get away with just invoking the steps .. but this needs
to be in your own layer and is a hack, and not appropriate for core.

About 4 years ago, we were partially through doing this work, when the
person doing the qemu parts stopped working on the project. The
partial work is captured in bugzilla.

Cheers,

Bruce

Thanks!


--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II


Prevent WIC image from being built?

Howard
 

Hi:

Was wondering if there was a way to exclude wic image from being built.  

Many thanks, and Happy New year.
Howard


recommendations for (YP-based) linux-powered drones?

Robert P. J. Day
 

friend recently asked me for recommendations for entry-level,
linux-based drones whose software is generated by yocto project, so it
could be used as a learning experience. as in, the fun would be in
the creation and customization of the software, not just playing with
the drone.

i didn't have an immediate answer ... i recall that qualcomm has
linux-based drone components:

https://developer.qualcomm.com/hardware/qualcomm-flight-pro

and i'm aware of https://www.dronecode.org/, focused on OSS drone
projects.

any thoughts on linux-based drones where one would build the
software using yocto project?

rday


Re: How to develop kernel modules on the target?

p32@...
 

Hello,

The execution of "make scripts prepare" did actually solve the issue, thank you very much for your help!

However, the need to manually execute this command on the target platform made me look into the kernel-devsrc recipe (https://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-kernel/linux/kernel-devsrc.bb?h=zeus) to see if it is possible to let the build host execute this step. Some comments imply that this is the case. Consider, for instance, the one in line 257:
Ensure we don't race against "make scripts" during cpio
Unfortunately, I was unable to figure out how to do this. Is there a way to let the recipe trigger this step automatically?

Thanks!


Re: chpasswd not working in yocto-2019

Philip Balister
 

On 12/28/20 7:33 AM, Raghu Icecraft Software Trainings wrote:
Paul,
Thanks for the reply.
I am using Xilinx-SDK based : Linux version 4.19.0-rt1-xilinx-v2019.1

Can you please let me know how to verify the yocto version running on
target.
You might have better luck on the meta-xilinx mailing list. They should
know the details for their BSP.

More info on Xilnx layers and a pointer to subscribe info to the mailing
list is here:

https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841883/Yocto

Philip


Thanks,
Raghu

On Mon, Dec 28, 2020 at 5:31 PM Paul Barker <pbarker@...> wrote:

On Mon, 28 Dec 2020 at 09:44, Raghu Icecraft Software Trainings
<raghu.icecraft@...> wrote:

Hello,
I have upgraded my kernel poky to 2019.1 version, here i am unable to
find chpasswd utility because of which i am unable to set password to my
root-user.
Can you please let me know if the chpasswd utility has been changed or
modified please.

Yocto Project doesn't have a version "2019.1", see
https://wiki.yoctoproject.org/wiki/Releases.

I guess you're using a vendor supplied BSP or SDK with that version
number. Could you provide the Yocto Project version number and the
layers in use, or at least give some more info on where your "2019.1"
release is from.

Thanks,

--
Paul Barker
Konsulko Group




Re: How to develop kernel modules on the target?

Ovidiu Panait
 

On 28.12.2020 15:40, p32 via lists.yoctoproject.org wrote:

Hello everyone,

I am using the Yocto-based build system provided by NXP (primarily via the meta-freescale layer) to create Linux images for an i.MX 8M board and would like to develop small kernel modules without going through the build process of the entire image after each modification. Therefore, I would prefer to compile the kernel modules on the target architecture and have added the following items to the IMAGE_INSTALL variable via my local.conf:
 - packagegroup-core-buildessential
 - kernel-modules
 - kernel-dev
 - kernel-devsrc

I then tried to follow the the official build instructions (https://www.kernel.org/doc/html/latest/kbuild/modules.html) on the target but was unable to create a kernel module:
imx8mqevk:~# make -C /lib/modules/$(uname -r)/build M=$PWD
make: Entering directory '/lib/modules/5.4.47-2.2.0+g5ec03d06f54e/build'
  CC [M]  /root/hello.o
In file included from ./include/linux/types.h:6,
                 from ./include/linux/list.h:5,
                 from ./include/linux/module.h:9,
                 from /root/hello.c:1:
./include/uapi/linux/types.h:5:10: fatal error: asm/types.h: No such file or directory
    [...]
compilation terminated.

Hi,


You need to run "make scripts prepare" in /usr/src/kernel before trying to compile kernel modules on target.


Ovidiu

What am I missing here? Is there something else I have to do on the target before I can compile kernel modules on the target?

For the sake of completeness: The build is based on the Zeus release and the following repo manifest file:
https://source.codeaurora.org/external/imx/imx-manifest/tree/imx-5.4.47-2.2.0.xml?h=imx-linux-zeus

Thanks!



How to develop kernel modules on the target?

p32@...
 

Hello everyone,

I am using the Yocto-based build system provided by NXP (primarily via the meta-freescale layer) to create Linux images for an i.MX 8M board and would like to develop small kernel modules without going through the build process of the entire image after each modification. Therefore, I would prefer to compile the kernel modules on the target architecture and have added the following items to the IMAGE_INSTALL variable via my local.conf:
 - packagegroup-core-buildessential
 - kernel-modules
 - kernel-dev
 - kernel-devsrc

I then tried to follow the the official build instructions (https://www.kernel.org/doc/html/latest/kbuild/modules.html) on the target but was unable to create a kernel module:
imx8mqevk:~# make -C /lib/modules/$(uname -r)/build M=$PWD
make: Entering directory '/lib/modules/5.4.47-2.2.0+g5ec03d06f54e/build'
  CC [M]  /root/hello.o
In file included from ./include/linux/types.h:6,
                 from ./include/linux/list.h:5,
                 from ./include/linux/module.h:9,
                 from /root/hello.c:1:
./include/uapi/linux/types.h:5:10: fatal error: asm/types.h: No such file or directory
    [...]
compilation terminated.

What am I missing here? Is there something else I have to do on the target before I can compile kernel modules on the target?

For the sake of completeness: The build is based on the Zeus release and the following repo manifest file:
https://source.codeaurora.org/external/imx/imx-manifest/tree/imx-5.4.47-2.2.0.xml?h=imx-linux-zeus

Thanks!


Re: chpasswd not working in yocto-2019

Raghu Icecraft Software Trainings
 

Paul,
Thanks for the reply.
I am using Xilinx-SDK based : Linux version 4.19.0-rt1-xilinx-v2019.1

Can you please let me know how to verify the yocto version running on target.

Thanks,
Raghu 

On Mon, Dec 28, 2020 at 5:31 PM Paul Barker <pbarker@...> wrote:
On Mon, 28 Dec 2020 at 09:44, Raghu Icecraft Software Trainings
<raghu.icecraft@...> wrote:
>
> Hello,
> I have upgraded my kernel poky to 2019.1 version, here i am unable to find chpasswd utility because of which i am unable to set password to my root-user.
> Can you please let me know if the chpasswd utility has been changed or modified please.

Yocto Project doesn't have a version "2019.1", see
https://wiki.yoctoproject.org/wiki/Releases.

I guess you're using a vendor supplied BSP or SDK with that version
number. Could you provide the Yocto Project version number and the
layers in use, or at least give some more info on where your "2019.1"
release is from.

Thanks,

--
Paul Barker
Konsulko Group


Re: chpasswd not working in yocto-2019

 

On Mon, 28 Dec 2020 at 09:44, Raghu Icecraft Software Trainings
<raghu.icecraft@...> wrote:

Hello,
I have upgraded my kernel poky to 2019.1 version, here i am unable to find chpasswd utility because of which i am unable to set password to my root-user.
Can you please let me know if the chpasswd utility has been changed or modified please.
Yocto Project doesn't have a version "2019.1", see
https://wiki.yoctoproject.org/wiki/Releases.

I guess you're using a vendor supplied BSP or SDK with that version
number. Could you provide the Yocto Project version number and the
layers in use, or at least give some more info on where your "2019.1"
release is from.

Thanks,

--
Paul Barker
Konsulko Group


chpasswd not working in yocto-2019

Raghu Icecraft Software Trainings
 

Hello,
I have upgraded my kernel poky to 2019.1 version, here i am unable to find chpasswd utility because of which i am unable to set password to my root-user.
Can you please let me know if the chpasswd utility has been changed or modified please.


Re: Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'

Matthias Rampke
 

Bisect points at the commit that introduced the hard pseudo abort:

84e0642ed6aba422583871fc153bbd94380074de is the first bad commit
commit 84e0642ed6aba422583871fc153bbd94380074de
Author: Richard Purdie <richard.purdie@...>
Date:   Tue Sep 29 17:57:38 2020 +0100

    pseudo: Abort on mismatch patch

    Rather than doing what turns out to be a rather dangerous "fixup" if
    we see a file with a different path but the same inode as another file
    we've previously seen, throw and abort. Direct the user to a wiki page
    where we can maintain information about what this error means.

    (From OE-Core rev: 2db491d97da08d44ebd257f98489550a82a7935c)

    Signed-off-by: Richard Purdie <richard.purdie@...>

:040000 040000 265627b814038c0cc19248bbb885ab7536202e1c acfc4fbeb04a887f2ceeaa029a63a4dd82f7767d M      meta
bisect run success


/MR


On Sun, Dec 27, 2020 at 8:43 PM matthias.rampke via lists.yoctoproject.org <matthias.rampke=googlemail.com@...> wrote:
One more thing: I tried reverting the linux-libc-headers version change (57d5f4ad410d4e9d55bdd9734bf5ab8fa6667a53) and that fails in the same way, so it's not that.

I also realized that the yocto-3.2 tag does not include the 3.2.1 updates; however the same issue happens on 3.2.1 as well.

I will try to bisect this but it seems like it will take a long time since I need to wipe the tmp directory at every step.

/MR



Re: Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'

Matthias Rampke
 

One more thing: I tried reverting the linux-libc-headers version change (57d5f4ad410d4e9d55bdd9734bf5ab8fa6667a53) and that fails in the same way, so it's not that.

I also realized that the yocto-3.2 tag does not include the 3.2.1 updates; however the same issue happens on 3.2.1 as well.

I will try to bisect this but it seems like it will take a long time since I need to wipe the tmp directory at every step.

/MR


Re: Error during do_install for linux-libc-headers_5.8 recipe during 'bitbake core-image-minimal'

Matthias Rampke
 

Hi,

I hit the same issue, also while trying things out on WSL2 (not committed enough to build a dedicated workstation/VM). I found a few more things:

This seems to be a pseudo abort with:
path mismatch [2 links]: ino 409763 db '/run/shm/sem.mp-bzdlrxrj' req '/run/shm/tGpqeT'.
I tried to follow the instructions to collect as many logs as possible. Logs are attached as far as I could find them; the strace is too big and you can find it here.

This is a regression: poky-3.1 (which uses linux-libc-headers 5.4) works. It seems we are not the only ones with this issue, and others have already given up on Yocto-on-WSL2.

Hope this is useful,
Matthias


obvious(?) ruby error: adding erroneous second ".gemspec" suffix

Robert P. J. Day
 

i'm not fluent enough in ruby to want to submit a patch for this, so
i'll let someone higher up the food chain handle it.

trying to build a number of "native" ruby recipes from
meta-openstack, and getting precisely the same error for various
recipes:

| ERROR: Gemspec file not found: XXXXX-native.gemspec.gemspec

the clear bug here is that something is adding a ".gemspec" suffix to
a string that *already* has that suffix. that error is acknowledged
here ("Append '.gemspec' extension only when it is not present"):

https://github.com/voxik/rubygems/commit/6c3f0dc798966a6474f6d694da05a15d620760d6

so someone who is more comfortable with ruby is invited to deal with
that.

rday


is there a focused place to ask about ruby/gems WRT yocto building?

Robert P. J. Day
 

to prepare for trying to build a number of ruby gems for WR LTS19
(effectively zeus, as always), i thought i'd start simple and begin
with building for qemux86-64 with gatesgarth so i could plausibly
claim that i have a working basis for comparison, whereupon if that
worked for what i was after, i could work backwards.

i just now started a build for qemux86-64/gatesgarth with "bitbake
ruby", and i'll take it from there. knowing little about ruby, is
there a smaller community that would help with issues i run into, or
should i keep the discussion here?

i want to start by trying to build absolutely stock puppet and chef,
and if that turns out to need fixing, i will of course submit patches.
if anyone has already gone through this exercise, that would be just
ducky.

i should have the result of the first build in an hour or two --
given that i'm not trying to do anything out of the ordinary, i would
*hope* that a totally generic build would work out of the box, but
we'll see.

rday

p.s. the above recipes involve the layers meta-cloud-services and
sub-layer meta-openstack.


[meta-selinux][PATCH] audit: enable arm/aarch64 processor support by default

Yi Zhao
 

We encountered a runtime error for auditctl on lib32 image for aarch64:

root@qemuarm64:~# auditctl -a always,exit -F arch=b32 -S adjtimex -S settimeofday -k time_change
arch elf mapping not found

The root cause is the aarch64 processor support is not enabled for arm
build. Refer to Debian[1] and Fedora[2], actually we can enable
arm/aarch64 processor support unconditionally.

[1] https://salsa.debian.org/debian/audit/-/commit/8c6b2049bafb52712ca981e73d5b79d5bd97e08e
[2] https://src.fedoraproject.org/rpms/audit/blob/master/f/audit.spec

Signed-off-by: Yi Zhao <yi.zhao@...>
---
recipes-security/audit/audit_2.8.5.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-security/audit/audit_2.8.5.bb b/recipes-security/audit/audit_2.8.5.bb
index e3e5ddd..e2e0352 100644
--- a/recipes-security/audit/audit_2.8.5.bb
+++ b/recipes-security/audit/audit_2.8.5.bb
@@ -41,9 +41,9 @@ EXTRA_OECONF += "--without-prelude \
--without-python \
--without-golang \
--disable-zos-remote \
+ --with-arm=yes \
+ --with-aarch64=yes \
"
-EXTRA_OECONF_append_arm = " --with-arm=yes"
-EXTRA_OECONF_append_aarch64 = " --with-aarch64=yes"

EXTRA_OEMAKE += "PYLIBVER='python${PYTHON_BASEVERSION}' \
PYINC='${STAGING_INCDIR}/$(PYLIBVER)' \
--
2.25.1


Need to disable IPV6 completely from the yocto image for Raspberrypi

@prashant2314
 

Dear Team,

I'm using yocto dunfell version 3.1.3 .  in my image ipv6 configuration is coming, which I don't need. I need to disable it completely.

Please assist me the correct way to do the same.

Thanks.


Re: [ANNOUNCEMENT] Yocto Project 3.2.1 (gatesgarth-24.0.1) is Released

Peter Kjellerstedt
 

-----Original Message-----
From: Mittal, Anuj <anuj.mittal@...>
Sent: den 22 december 2020 17:55
To: Tummalapalli, Vineela <vineela.tummalapalli@...>; Peter
Kjellerstedt <peter.kjellerstedt@...>
Cc: yocto@...
Subject: Re: [yocto] [ANNOUNCEMENT] Yocto Project 3.2.1 (gatesgarth-
24.0.1) is Released

On Tue, 2020-12-15 at 23:07 +0000, Peter Kjellerstedt wrote:
Repository Name: meta-gplv2
Repository Location: https://git.yoctoproject.org/git/meta-gplv2
Branch: gatesgarth
Tag: yocto-3.2.1
The yocto-3.2.1 and gatesgarth-24.0.1 tags for meta-gplv2 have been
incorrectly
set on the dunfell branch rather than the gatesgarth branch. The Git
revision
and tar balls below are correct though. Since the tags are signed I
do now want
to modify them myself, so please correct them as soon as possible.
Vineela isn't working this week I think so she might not be able to
help but it looks like the commit tagged is on gatesgarth ...

https://git.yoctoproject.org/clean/cgit.cgi/meta-gplv2/log/?h=gatesgarth

$ git branch -a --contains yocto-3.2.1
* master
remotes/origin/HEAD -> origin/master
remotes/origin/gatesgarth
remotes/origin/master
remotes/origin/master-next

Thanks,

Anuj
You are absolutely correct. It seems the tags were incorrect for an hour
when first created, and apparently our local Git mirror does not handle
tags being updated so it still provides the original (incorrect) tags.
Thank you for pointing out what was a problem on our side. I will take
it up with our SCM team.

//Peter

5981 - 6000 of 57804