[yocto] Recipe fails at do_rm_work due to failed attempt to delete a named pipe (FIFO)

[David Antliff]

Hi,

I'm working with a PetaLinux 2021.2 project, which defines a recipe called 
"petalinux-initramfs-image".

# Simple petalinux initramfs image.
DESCRIPTION = "Small image capable of booting a device. The kernel includes \
the Minimal RAM-based Initial Root Filesystem (initramfs), which finds the \
first 'init' program more efficiently."

INITRAMFS_SCRIPTS ?= "initramfs-framework-base \
initramfs-module-e2fs \
initramfs-module-udhcpc \
initramfs-module-searche2fs \
"

INITRAMFS_SCRIPTS_append_k26 = " initramfs-module-exec"

INITRAMFS_PACKAGES ?= "${VIRTUAL-RUNTIME_base-utils} \
base-passwd \
e2fsprogs \
${ROOTFS_BOOTSTRAP_INSTALL} \
${MACHINE_ESSENTIAL_EXTRA_RDEPENDS} \
"

BAD_RECOMMENDATIONS += "initramfs-module-rootfs"

PACKAGE_INSTALL ?= "packagegroup-core-boot ${INITRAMFS_PACKAGES} 
${INITRAMFS_SCRIPTS}"

# Do not pollute the initrd image with rootfs features
IMAGE_FEATURES = ""

export IMAGE_BASENAME = "petalinux-initramfs-image"
IMAGE_LINGUAS = ""

LICENSE = "MIT"

IMAGE_FSTYPES = "${INITRAMFS_FSTYPES}"
inherit core-image

IMAGE_ROOTFS_SIZE = "8192"
IMAGE_ROOTFS_EXTRA_SPACE = "0"

rm_work_rootfs[noexec] = "1"
rm_work_rootfs[cleandirs] = ""
RM_WORK_EXCLUDE_ITEMS = "rootfs"


For reasons I don't understand, this recipe fails to build at the do_rm_work 
task. Looking at the bitbake -v log, I can see that this recipe is somehow 
causing the temp directory in the build directory to be deleted:

+ rm -rf recipe-sysroot-native

+ for dir in *

+ '[' rootfs = pseudo ']'

+ echo rootfs

+ grep -q -w rootfs

+ for dir in *

+ '[' temp = pseudo ']'

+ echo rootfs

+ grep -q -w temp

+ rm -rf temp

+ ret=0

+ trap '' 0

+ exit 0

ERROR: petalinux-initramfs-image-1.0-r0 do_rm_work: [Errno 2] No such file or 
directory: 
'/[removed]/build/tmp/work/zynqmp_generic-xilinx-linux/petalinux-initramfs-image/1.0-r0/temp/fifo.59670'

I think whatever is calling do_rm_work (in rm_work.bbclass) is creating a named 
pipe (FIFO) file in the build/...petalinux-initramfs-image/1.0-r0/temp 
directory, for whatever purpose, and then when this recipe (for whatever 
reason) causes the deletion of the temp directory and exits, this outer entity 
then expects to be able to clean up the FIFO file it created, fails to do so, 
and raises the fatal error.

I'm assuming that this is a problem with the recipe itself, but I (with my 
limited knowledge and experience in this area) cannot see anything obvious in 
there that would lead to the inadvertent deletion of the temp directory.

Note that if I add RM_WORK_EXCLUDE += "petalinux-initramfs-image" then the 
build does not fail and I see this instead:

NOTE: Executing Tasks
+ do_rm_work
+ for p in petalinux-initramfs-image

NOTE: petalinux-initramfs-image-1.0-r0 do_rm_work: rm_work: Skipping 
petalinux-initramfs-image since it is in RM_WORK_EXCLUDE
+ '[' petalinux-initramfs-image = petalinux-initramfs-image ']'
+ bbnote 'rm_work: Skipping petalinux-initramfs-image since it is in 
RM_WORK_EXCLUDE'
+ '[' -p 
/[removed]/build/tmp/work/zynqmp_generic-xilinx-linux/petalinux-initramfs-image/1.0-r0/temp/fifo.60213
 ']'
+ printf '%b\0' 'bbnote rm_work: Skipping petalinux-initramfs-image since it is 
in RM_WORK_EXCLUDE'
+ exit 0
+ bb_bash_exit_handler 'exit 0'
+ ret=0

+ set +x

There the named pipe file is mentioned, but I'm not sure why a test for its 
existence is here, interleaved with output from rm_work.bbclass. I don't see 
that in rm_work.bbclass anywhere - or is it a part of bbnote​?

Any idea what's going on with this recipe?

-- David.






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57501): https://lists.yoctoproject.org/g/yocto/message/57501
Mute This Topic: https://lists.yoctoproject.org/mt/92321952/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] M+ & H bugs with Milestone Movements WW2"All,

[Stephen Jolley]

All,

YP M+ or high bugs which moved to a new milestone in WW28 are listed below: 


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


High

  14065

Automated ptest regression testing

randy.macl...@windriver.com

ross.bur...@arm.com

4.1 M2

4.1 M3


Medium+

  14775

AB-INT: SDK preparation failure: SState: cannot test file://[...] 
TimeoutError('timed out')

richard.pur...@linuxfoundation.org

unassig...@yoctoproject.org

4.1 M2

4.1 M3

Thanks, 

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com  

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57500): https://lists.yoctoproject.org/g/yocto/message/57500
Mute This Topic: https://lists.yoctoproject.org/mt/92321685/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Enhancements/Bugs closed WW28!

[Stephen Jolley]

All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


alejan...@enedino.org

2


yogesh.ty...@intel.com

1


ptsne...@gmail.com

1


randy.macl...@windriver.com

1


ross.bur...@arm.com

1


Grand Total

6

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57499): https://lists.yoctoproject.org/g/yocto/message/57499
Mute This Topic: https://lists.yoctoproject.org/mt/92321660/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] 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 410
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,  "4.1", "4.2", "4.99" and "Future", the more pressing/urgent
issues being in "4.1" and then "4.2".

 

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...@gmail.com
 ) 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...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57497): https://lists.yoctoproject.org/g/yocto/message/57497
Mute This Topic: https://lists.yoctoproject.org/mt/92321582/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current high bug count owners for Yocto Project 4.1

[Stephen Jolley]

All,

Below is the list as of top 35 bug owners as of the end of WW28 of who have
open medium or higher bugs and enhancements against YP 4.1.   There are 77
possible work days left until the final release candidates for YP 4.1 needs
to be released.


Who

Count


michael.opdenac...@bootlin.com

36


ross.bur...@arm.com

27


david.re...@windriver.com

23


bruce.ashfi...@gmail.com

21


randy.macl...@windriver.com

16


richard.pur...@linuxfoundation.org

10


saul.w...@windriver.com

10


jpewhac...@gmail.com

9


sakib.sa...@windriver.com

9


aryaman.gu...@windriver.com

6


tim.orl...@konsulko.com

6


mhalst...@linuxfoundation.org

5


jon.ma...@arm.com

4


akuster...@gmail.com

3


tvgamb...@gmail.com

2


pa...@zhukoff.net

2


pgowda@gmail.com

2


qi.c...@windriver.com

2


hongxu@windriver.com

2


sundeep.kokko...@gmail.com

2


mostthings...@gmail.com

1


aeh...@gmail.com

1


beh...@converseincode.com

1


martin.bee...@online.de

1


ahmed.hos...@opensynergy.com

1


nicolas.deche...@linaro.org

1


raj.k...@gmail.com

1


martin.ja...@gmail.com

1


thomas.per...@bootlin.com

1


shac...@vdoo.com

1


ola.x.nils...@axis.com

1


alexandre.bell...@bootlin.com

1


luca.ceres...@bootlin.com

1


alejan...@enedino.org

1


open.sou...@oleksandr-kravchuk.com

1


Grand Total

212

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57498): https://lists.yoctoproject.org/g/yocto/message/57498
Mute This Topic: https://lists.yoctoproject.org/mt/92321585/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] missing cgroups when trying to re-mount rootfs from initramfs busybox image

[Embedded 1]

I have busybox with an initramfs. When I try to re-mount the rootfs I
see this. This is with Yocto. Do I need to include systemd in my
initramfs image?

sh-5.0# exec switch_root /root /sbin/init
switch_root: failed to mount moving /run to /root/run: Invalid argument
switch_root: forcing unmount of /run
[  339.929584] systemd[1]: System time before build time, advancing clock.
[  339.974784] systemd[1]: Module 'autofs4' is built in
[  339.980811] systemd[1]: Failed to mount tmpfs at /sys/fs/cgroup: No such file
 or directory
[  339.989411] systemd[1]: Failed to mount cgroup at /sys/fs/cgroup/systemd: No
such file or directory
[!!] Failed to mount API filesystems.
[  340.024657] systemd[1]: Freezing execution.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57496): https://lists.yoctoproject.org/g/yocto/message/57496
Mute This Topic: https://lists.yoctoproject.org/mt/92319892/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Installing gfortran into native sysroot for libgfortran

[Philip Balister]

In my notes:

cat /dev/null > conf/locked-signs.inc

Philip

On 7/11/22 12:49, Gregory Anders wrote:

On Friday, July 08, 2022 11:40 AM MDT, Philip Balister  
wrote:
  

On 7/8/22 09:12, Khem Raj wrote:



On Fri, Jul 8, 2022 at 2:25 AM Gregory Anders mailto:g...@gpanders.com>> wrote:

 On Thu, 07 Jul 2022 16:26 +0100, Richard Purdie wrote:
  >On Thu, 2022-07-07 at 06:39 -0700, Gregory Anders wrote:
  >> Problem solved: the issue was actually that I was using a network
  >> sstate cache,
  >> and the cached output of gcc-cross did not contain gfortran.
  >> Disabling the
  >> sstate cache for gcc-cross causes gfortran to be included in the
  >> sysroot and
  >> now all is working as expected.
  >
  >You shouldn't have to disable the sstate cache but glad you got it
  >working. Which release series is that with?

 I am using Xilinx's Petalinux tool, which uses honister under the
 hood. Xilinx maintains an sstate cache for Petalinux, which is quite
 convenient for cutting down build times, but apparently setting the
 FORTRAN variable does not invalidate the sstate cache entry for the
 gcc-cross recipe (which it should, as it affects the build outputs).


Perhaps it’s using locked sstate which might be the reason


It is. It was great fun to find the path to disable it when I also had
this issue :)

Philip


(Apologies for the double post to the list.)

Philip, would you mind sharing what you did to disable it?

Thanks,

Greg






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57495): https://lists.yoctoproject.org/g/yocto/message/57495
Mute This Topic: https://lists.yoctoproject.org/mt/92216663/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Installing gfortran into native sysroot for libgfortran

[Gregory Anders]

On Friday, July 08, 2022 11:40 AM MDT, Philip Balister  
wrote:

> On 7/8/22 09:12, Khem Raj wrote:
> >
> >
> > On Fri, Jul 8, 2022 at 2:25 AM Gregory Anders  > > wrote:
> >
> > On Thu, 07 Jul 2022 16:26 +0100, Richard Purdie wrote:
> >  >On Thu, 2022-07-07 at 06:39 -0700, Gregory Anders wrote:
> >  >> Problem solved: the issue was actually that I was using a network
> >  >> sstate cache,
> >  >> and the cached output of gcc-cross did not contain gfortran.
> >  >> Disabling the
> >  >> sstate cache for gcc-cross causes gfortran to be included in the
> >  >> sysroot and
> >  >> now all is working as expected.
> >  >
> >  >You shouldn't have to disable the sstate cache but glad you got it
> >  >working. Which release series is that with?
> >
> > I am using Xilinx's Petalinux tool, which uses honister under the
> > hood. Xilinx maintains an sstate cache for Petalinux, which is quite
> > convenient for cutting down build times, but apparently setting the
> > FORTRAN variable does not invalidate the sstate cache entry for the
> > gcc-cross recipe (which it should, as it affects the build outputs).
> >
> >
> > Perhaps it’s using locked sstate which might be the reason
>
> It is. It was great fun to find the path to disable it when I also had
> this issue :)
>
> Philip

(Apologies for the double post to the list.)

Philip, would you mind sharing what you did to disable it?

Thanks,

Greg


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57494): https://lists.yoctoproject.org/g/yocto/message/57494
Mute This Topic: https://lists.yoctoproject.org/mt/92216663/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] How to get license text

[William Huang]

Hi,
I was wondering if it is possible to get the license information for all of the 
deployed packages in the image? I know there's a license.manifest file in 
deploy/licenses, but I'm looking for a file that includes that manifest as well 
as the paragraph associated with the license. Closest I found was in the 
/usr/share/common-license folder which has the LICENSE or COPYING file for each 
package, but I am looking if there's a single file that contains this 
information instead.

Thanks

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57493): https://lists.yoctoproject.org/g/yocto/message/57493
Mute This Topic: https://lists.yoctoproject.org/mt/92314709/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Installing gfortran into native sysroot for libgfortran

[Gregory Anders]

On Friday, July 08, 2022 08:12 AM MDT, Khem Raj  wrote:

> On Fri, Jul 8, 2022 at 2:25 AM Gregory Anders  wrote:
>
> > On Thu, 07 Jul 2022 16:26 +0100, Richard Purdie wrote:
> > >On Thu, 2022-07-07 at 06:39 -0700, Gregory Anders wrote:
> > >> Problem solved: the issue was actually that I was using a network
> > >> sstate cache,
> > >> and the cached output of gcc-cross did not contain gfortran.
> > >> Disabling the
> > >> sstate cache for gcc-cross causes gfortran to be included in the
> > >> sysroot and
> > >> now all is working as expected.
> > >
> > >You shouldn't have to disable the sstate cache but glad you got it
> > >working. Which release series is that with?
> >
> > I am using Xilinx's Petalinux tool, which uses honister under the
> > hood. Xilinx maintains an sstate cache for Petalinux, which is quite
> > convenient for cutting down build times, but apparently setting the
> > FORTRAN variable does not invalidate the sstate cache entry for the
> > gcc-cross recipe (which it should, as it affects the build outputs).
>
>
> Perhaps it’s using locked sstate which might be the reason

I didn't know the sstate could be locked -- how would one unlock it? Could you
point me toward some relevant docs?

After some cursory searching the only thing I've found is the 'locked-sigs.inc'
file. And indeed, Petalinux does ship with a locked-sigs.inc file which
includes a signature for gcc-cross-arm. But adding gcc-cross-arm to
SIGGEN_UNLOCKED_RECIPES doesn't seem to have any effect.


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57492): https://lists.yoctoproject.org/g/yocto/message/57492
Mute This Topic: https://lists.yoctoproject.org/mt/92216663/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] ALTERNATIVE and RDEPENDS

[Konrad Weihmann]

Hi all,

is there a way to set the package metadata in a way that it would 
require one of the packages providing a tool via the ALTERNATIVE_ mechanism?


E.g. sed for instance could be provided by busybox (if enabled in 
config) or by the standalone sed recipe - within my recipe I would just 
want to make sure that any of the providing packages is available/used 
when assembling the image.


This basically affects all of the tools that are provided by coreutils 
and busybox too


I would be happy about any pointer...

Regards
Konrad

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#57491): https://lists.yoctoproject.org/g/yocto/message/57491
Mute This Topic: https://lists.yoctoproject.org/mt/92308142/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-