Date   

M+ & H bugs with Milestone Movements WW26

Stephen Jolley
 

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 bitbake debug output

randy.macleod@...

saul.wold@...

4.99

4.1 M3

 

13766

Using TCLIBC=musl results in SDKs producing incompatible binaries

randy.macleod@...

sakib.sajal@...

4.1 M1

4.1 M2

 

13854

xserver-nodm.service failed with xf86OpenConsole: Switching VT failed

randy.macleod@...

pavel@...

4.99

4.1 M3

 

13931

evaluate simplification of headers_install requirements

randy.macleod@...

bruce.ashfield@...

Future

4.1 M2

 

14121

Implement sphinx switchers.js for bitbake

randy.macleod@...

nicolas.dechesne@...

4.1 M1

4.1 M3

 

14303

Result of build is not stored in testresult.json with resulttool

randy.macleod@...

unassigned@...

4.1 M1

4.1 M3

 

14693

cmake-native do_configure fails when rebuilding without sstate on NIS hosts

randy.macleod@...

randy.macleod@...

4.1 M1

4.1 M2

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Enhancements/Bugs closed WW26!

Stephen Jolley
 

All,

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

Who

Count

michael.opdenacker@...

2

ross.burton@...

1

pavel@...

1

richard.purdie@...

1

randy.macleod@...

1

akuster808@...

1

Grand Total

7

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Current high bug count owners for Yocto Project 4.1

Stephen Jolley
 

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 release candidates for YP 4.1 needs to be released.

Who

Count

michael.opdenacker@...

37

ross.burton@...

25

david.reyna@...

23

bruce.ashfield@...

21

randy.macleod@...

16

richard.purdie@...

10

saul.wold@...

10

JPEWhacker@...

9

sakib.sajal@...

9

tim.orling@...

8

Aryaman.Gupta@...

6

mhalstead@...

4

jon.mason@...

4

akuster808@...

3

tvgamblin@...

2

pavel@...

2

pgowda.cve@...

2

Qi.Chen@...

2

hongxu.jia@...

2

Ahmed.Hossam@...

1

thomas.perrot@...

1

raj.khem@...

1

behanw@...

1

nicolas.dechesne@...

1

martin.beeger@...

1

mostthingsweb@...

1

luca.ceresoli@...

1

Martin.Jansa@...

1

sundeep.kokkonda@...

1

shachar@...

1

ola.x.nilsson@...

1

alexandre.belloni@...

1

throos@...

1

alejandro@...

1

piotr.lobacz@...

1

open.source@...

1

aehs29@...

1

Grand Total

213

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


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 418 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.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@...

 


[PATCH yocto-autobuilder-helper] scripts/archive_buildstats.py: archive buildstats to tar.zst

Aryaman Gupta <aryaman.gupta@...>
 

Convert each time-stamped buildstats directory to a compressed tarball
using the hostname as a prefix (to the file name only) so that one can
identify the source machine. Move these tarballs to the directory:
testresults/<build_name>/buildstats/

The archiving is performed during the "collect results" step.

Signed-off-by: Aryaman Gupta <aryaman.gupta@...>
Signed-off-by: Randy MacLeod <Randy.MacLeod@...>
---
scripts/archive_buildstats.py | 32 ++++++++++++++++++++++++++++++++
scripts/run-config | 1 +
2 files changed, 33 insertions(+)
create mode 100755 scripts/archive_buildstats.py

diff --git a/scripts/archive_buildstats.py b/scripts/archive_buildstats.py
new file mode 100755
index 0000000..30ea289
--- /dev/null
+++ b/scripts/archive_buildstats.py
@@ -0,0 +1,32 @@
+#!/usr/bin/env python3
+#
+# SPDX-License-Identifier: GPL-2.0-only
+#
+import os, subprocess, socket, sys
+
+def usagedir():
+ print("Usage: " + sys.argv[0] + " <src> <dest> <target>")
+
+def main():
+ if len(sys.argv) != 4:
+ usage()
+ sys.exit()
+
+ builddir = sys.argv[1]
+ dest = sys.argv[2]
+ target = sys.argv[3]
+ dest_bsdir = os.path.join(dest, target, "buildstats")
+ subprocess.run(["mkdir", "-p", dest_bsdir])
+
+ build_bsdir = os.path.join(builddir, "tmp/buildstats")
+ hostname = socket.gethostname()
+ os.chdir(build_bsdir)
+ for timestamp in os.listdir(build_bsdir):
+ if hostname:
+ output = hostname + "-" + timestamp + ".tar.zst"
+ else:
+ output = "nohostname-"+ timestamp + ".tar.zst"
+ subprocess.check_call("tar -I zstd -cf "+output+" "+timestamp+"/*", shell=True)
+ subprocess.run(["mv", output, dest_bsdir])
+
+main()
diff --git a/scripts/run-config b/scripts/run-config
index 838847a..953977e 100755
--- a/scripts/run-config
+++ b/scripts/run-config
@@ -334,6 +334,7 @@ elif args.phase == "finish" and args.stepname == "collect-results":
hp.printheader("Running results collection")
runcmd([scriptsdir + "/collect-results", args.builddir, args.results_dir, args.target])
runcmd([scriptsdir + "/summarize_top_output.py", args.results_dir, args.target])
+ runcmd([scriptsdir + "/archive_buildstats.py", args.builddir, args.results_dir, args.target])
sys.exit(0)

if jcfg:
--
2.35.1


[meta-security][PATCH v2] meta-integrity: kernel-modsign: prevents splitting out debug symbols

Jose Quaresma
 

Starting with [1] kernel modules symbols is being slipped in OE-core
and this breaks the kernel modules sign, so disable it.

[1] https://git.openembedded.org/openembedded-core/commit/?id=e09a8fa931fe617afc05bd5e00dca5dd3fe386e8

Signed-off-by: Jose Quaresma <jose.quaresma@...>
---
meta-integrity/classes/kernel-modsign.bbclass | 2 ++
1 file changed, 2 insertions(+)

diff --git a/meta-integrity/classes/kernel-modsign.bbclass b/meta-integrity/classes/kernel-modsign.bbclass
index 093c358..d3aa7fb 100644
--- a/meta-integrity/classes/kernel-modsign.bbclass
+++ b/meta-integrity/classes/kernel-modsign.bbclass
@@ -13,7 +13,9 @@ MODSIGN_PRIVKEY ?= "${MODSIGN_KEY_DIR}/privkey_modsign.pem"
MODSIGN_X509 ?= "${MODSIGN_KEY_DIR}/x509_modsign.crt"

# If this class is enabled, disable stripping signatures from modules
+# as well disable the debug symbols split
INHIBIT_PACKAGE_STRIP = "1"
+INHIBIT_PACKAGE_DEBUG_SPLIT = "1"

kernel_do_configure:prepend() {
if [ -f "${MODSIGN_PRIVKEY}" -a -f "${MODSIGN_X509}" ]; then
--
2.36.1


[meta-security][PATCH] meta-integrity: kernel-modsign: prevents splitting out debug

Jose Quaresma
 

Starting with [1] kernel modulus symbols is being slipped in OE-core
and this breaks the kernel module sign, so disable it.

[1] https://git.openembedded.org/openembedded-core/commit/?id=e09a8fa931fe617afc05bd5e00dca5dd3fe386e8

Signed-off-by: Jose Quaresma <jose.quaresma@...>
---
meta-integrity/classes/kernel-modsign.bbclass | 2 ++
1 file changed, 2 insertions(+)

diff --git a/meta-integrity/classes/kernel-modsign.bbclass b/meta-integrity/classes/kernel-modsign.bbclass
index 093c358..d3aa7fb 100644
--- a/meta-integrity/classes/kernel-modsign.bbclass
+++ b/meta-integrity/classes/kernel-modsign.bbclass
@@ -13,7 +13,9 @@ MODSIGN_PRIVKEY ?= "${MODSIGN_KEY_DIR}/privkey_modsign.pem"
MODSIGN_X509 ?= "${MODSIGN_KEY_DIR}/x509_modsign.crt"

# If this class is enabled, disable stripping signatures from modules
+# as well disable the debug symbols split
INHIBIT_PACKAGE_STRIP = "1"
+INHIBIT_PACKAGE_DEBUG_SPLIT = "1"

kernel_do_configure:prepend() {
if [ -f "${MODSIGN_PRIVKEY}" -a -f "${MODSIGN_X509}" ]; then
--
2.36.1


Re: how to setup host environment for yocto

tomzy
 

Hi,
Hi
I'm new to yocto, I wonder the recommended way to setup an environment for yocto using vagrant or docker to isolate from the host, since I've encounter many different error about python version or something like that. Some layers providede by vendor uses a tool called repo for version control, I always cannot install on my machine, following the steps form that page doesn't help either. 

I recommend taking a look at the kas project.[1] It allows you to manage Yocto layers in your project in a very easy
and pleasant way. You can also take a look at the Yocto Summit presentation [2] which talks about various ways of
managing Yocto layers. Good luck with learning the Yocto Project.
[1] https://github.com/siemens/kas; https://kas.readthedocs.io/en/latest/userguide.html?highlight=kas-container#usage
[2] https://www.youtube.com/watch?v=PLl8jwZOpS0&list=PLD4M5FoHz-TwZkOR-GoWjq5XlLpZIFt5-&index=12

Thanks,
CD

Regards
Tomasz Żyjewski
Embedded Systems Engineer
GPG: 5C495EA3EBEECA59
https://3mdeb.com | @3mdeb_com


[yocto-autobuilder-helper] [PATCH] config.json: Enable memres bitbake

Richard Purdie
 

We could do with wider exposure of testing of this so enable on the
autobuilder by default.

Signed-off-by: Richard Purdie <richard.purdie@...>
---
config.json | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/config.json b/config.json
index d01319f..de32fb1 100644
--- a/config.json
+++ b/config.json
@@ -66,7 +66,8 @@
"BB_LOG_HOST_STAT_ON_INTERVAL = '1'",
"BB_LOG_HOST_STAT_CMDS_INTERVAL = 'oe-time-dd-test.sh -c 100 -t 15'",
"BB_LOG_HOST_STAT_ON_FAILURE = '1'",
- "BB_LOG_HOST_STAT_CMDS_FAILURE = 'oe-time-dd-test.sh -l'"
+ "BB_LOG_HOST_STAT_CMDS_FAILURE = 'oe-time-dd-test.sh -l'",
+ "BB_SERVER_TIMEOUT = '60'"
]
},
"templates" : {
--
2.34.1


how to setup host environment for yocto

黃玉珍
 


Hi,

I'm new to yocto, I wonder the recommended way to setup an environment for yocto using vagrant or docker to isolate from the host, since I've encounter many different error about python version or something like that. Some layers providede by vendor uses a tool called repo for version control, I always cannot install on my machine, following the steps form that page doesn't help either. 

Thanks,
CD


Re: source-less python

Ross Burton
 

On 23 Jun 2022, at 23:40, Aurum Nitrogen via lists.yoctoproject.org <aurumnitrogen=gmail.com@...> wrote:

Hi,
I was wondering if there has been talk about support for source-less python on an image. Installing py and pyc files doubles the size of python on the rootfs. I can imagine this being implemented as an image feature.
I know that in buildroot it is supported.
Was this discussed and decided against? Is this an open issue?

There’s an open issue: https://bugzilla.yoctoproject.org/show_bug.cgi?id=6434

The easiest implementation would be a rootfs-time postprocessing step where you compile every .py file, and then delete the .py. Is this what buildroot does?

This does break feeds, but the alternative (of changing how packaging is done) would be a lot more invasive.

Ross
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.


Minutes: Yocto Project Weekly Triage Meeting 6/23/2022

sakib.sajal@...
 

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage

Attendees: Stephen Jolley, Steve Sakoman, Saul Wold, Luca Ceresoli, Michael Opdenacker, Pavel Zhukov, Richard Purdie, Aryaman Gupta, Randy Macleod, Ross Burton, Tim Orling

ARs:

Notes:
N/A

Medium+ 4.1 Unassigned Enhancements/Bugs: 74 (Last week 75)

Medium+ 4.99 Unassigned Enhancements/Bugs: 45 (Last week 44)

AB Bugs: 47 (Last week 49)


Re: source-less python

Alexander Kanavin
 

I don't remember any such discussion. If you want this to happen, you
are welcome to develop the feature.

Alex

On Thu, 23 Jun 2022 at 16:39, Aurum Nitrogen <aurumnitrogen@...> wrote:

Hi,
I was wondering if there has been talk about support for source-less python on an image. Installing py and pyc files doubles the size of python on the rootfs. I can imagine this being implemented as an image feature.
I know that in buildroot it is supported.
Was this discussed and decided against? Is this an open issue?

Thanks,
John




source-less python

Aurum Nitrogen
 

Hi,
I was wondering if there has been talk about support for source-less python on an image. Installing py and pyc files doubles the size of python on the rootfs. I can imagine this being implemented as an image feature.
I know that in buildroot it is supported.
Was this discussed and decided against? Is this an open issue?

Thanks,
John


USB Installer for initial deployment

Matthias Schoepfer
 

Hi there,

I am looking for some kind of package or software, that creates an (USB thumb drive) installer for initial installation and deployment of a yocto image. So you can flash the image onto an USB thumb drive and boot from it (arch is x86-64 so this should be easy), and after asking if that is really what you want, will erase the local storage and partition the drive (root A/B, data, swap) and copies over the image from the yocto build. I know that there is some thing into this direction in the meta-intel layer, but that is not quite well documented nor do I think it will suit our needs (regarding partitioning for example).

So, before I write terrible bash scripts into an initramfs init (because this is my best idea so far), if someone could give me a hint were to look would be great.

Thanks and regards,

    Matthias


Re: [PATCH yocto-autobuilder-helper] scripts/archive_buildstats.py: copy all buildstats

Richard Purdie
 

On Wed, 2022-06-22 at 17:12 -0400, Randy MacLeod wrote:
As a first pass, collect all the tmp/buildstats logs
using 'cp -a', to enable review and graphing of all builds.
The goal is to understand the trends in the /proc/pressure/{cpu|io}
data that is now gathered as part of the buildstats system.

Signed-off-by: Aryaman Gupta <Aryaman.Gupta@...>
Signed-off-by: Randy MacLeod <Randy.MacLeod@...>
---
scripts/archive_buildstats.py | 27 +++++++++++++++++++++++++++
scripts/run-config | 1 +
2 files changed, 28 insertions(+)
create mode 100755 scripts/archive_buildstats.py
The NAS couldn't cope with the number of small files these data trees
contained leading to timeouts. If you want to do something like this
you'll probably have to create tarball archives of the results.

Cheers,

Richard


[meta-security][PATCH] lkrg: update to 0.9.3

Armin Kuster
 

refresh patch

Signed-off-by: Armin Kuster <akuster808@...>
---
.../lkrg/files/makefile_cleanup.patch | 72 +++++++------------
...g-module_0.9.2.bb => lkrg-module_0.9.3.bb} | 7 +-
2 files changed, 30 insertions(+), 49 deletions(-)
rename recipes-kernel/lkrg/{lkrg-module_0.9.2.bb => lkrg-module_0.9.3.bb} (90%)

diff --git a/recipes-kernel/lkrg/files/makefile_cleanup.patch b/recipes-kernel/lkrg/files/makefile_cleanup.patch
index 799b1a6..f29afbe 100644
--- a/recipes-kernel/lkrg/files/makefile_cleanup.patch
+++ b/recipes-kernel/lkrg/files/makefile_cleanup.patch
@@ -1,73 +1,53 @@
-Upstream-Status: Pending
-
-This needs more work. Its my starting point.
-
+Upstream-Status: Inappropriate [embedded specific]
+
Signed-off-by: Armin Kuster <akuster808@...>

+
Index: git/Makefile
===================================================================
--- git.orig/Makefile
+++ git/Makefile
-@@ -4,28 +4,10 @@
- # Author:
- # - Adam 'pi3' Zabrocki (http://pi3.com.pl)
- ##
--
--P_OUTPUT = output
+@@ -7,15 +7,8 @@
+
+ P_OUTPUT = output
P_PWD ?= $(shell pwd)
-P_KVER ?= $(shell uname -r)
--P_BOOTUP_SCRIPT ?= scripts/bootup/lkrg-bootup.sh
--TARGET := p_lkrg
+ P_BOOTUP_SCRIPT ?= scripts/bootup/lkrg-bootup.sh
+ TARGET := p_lkrg
-ifneq ($(KERNELRELEASE),)
- KERNEL := /lib/modules/$(KERNELRELEASE)/build
-else
- ## KERNELRELEASE not set.
- KERNEL := /lib/modules/$(P_KVER)/build
-endif
--
--#
--# Uncomment for debug compilation
--#
--# ccflags-m := -ggdb -DP_LKRG_DEBUG_BUILD -finstrument-functions
--# ccflags-y := ${ccflags-m}
--# p_lkrg-objs += src/modules/print_log/p_lkrg_debug_log.o

--obj-m += $(TARGET).o
--$(TARGET)-objs += src/modules/ksyms/p_resolve_ksym.o \
-+obj-m := p_lkrg.o
-+p_lkrg-y := src/modules/ksyms/p_resolve_ksym.o \
- src/modules/hashing/p_lkrg_fast_hash.o \
- src/modules/comm_channel/p_comm_channel.o \
- src/modules/integrity_timer/p_integrity_timer.o \
-@@ -92,23 +74,14 @@ $(TARGET)-objs += src/modules/ksyms/p_re
+ #
+ # Use DEBUG=on for debug build.
+@@ -94,14 +87,13 @@ $(TARGET)-objs += src/modules/ksyms/p_re
src/p_lkrg_main.o


-all:
-# $(MAKE) -C $(KERNEL) M=$(P_PWD) modules CONFIG_DEBUG_SECTION_MISMATCH=y
- $(MAKE) -C $(KERNEL) M=$(P_PWD) modules
-- mkdir -p $(P_OUTPUT)
-- cp $(P_PWD)/$(TARGET).ko $(P_OUTPUT)
--
--install:
-- $(MAKE) -C $(KERNEL) M=$(P_PWD) modules_install
-- depmod -a
-- $(P_PWD)/$(P_BOOTUP_SCRIPT) install
-
--uninstall:
-- $(P_PWD)/$(P_BOOTUP_SCRIPT) uninstall
+modules:
+ $(MAKE) -C $(KERNEL_SRC) M=$(P_PWD) modules
-+
-+modules_install:
+ mkdir -p $(P_OUTPUT)
+ cp $(P_PWD)/$(TARGET).ko $(P_OUTPUT)
+
+-install:
+- $(MAKE) -C $(KERNEL) M=$(P_PWD) modules_install
++moduled_install:
+ $(MAKE) -C $(KERNEL_SRC) M=$(P_PWD) modules_install
+ depmod -a
+ $(P_PWD)/$(P_BOOTUP_SCRIPT) install
+
+@@ -109,7 +101,7 @@ uninstall:
+ $(P_PWD)/$(P_BOOTUP_SCRIPT) uninstall

clean:
- $(MAKE) -C $(KERNEL) M=$(P_PWD) clean
-- $(RM) Module.markers modules.order
-- $(RM) $(P_PWD)/src/modules/kmod/client/kmod/Module.markers
-- $(RM) $(P_PWD)/src/modules/kmod/client/kmod/modules.order
-- $(RM) -rf $(P_OUTPUT)
-+ rm -f *.o *~ core .depend .*.cmd *.ko *.mod.c
-+ rm -f Module.markers Module.symvers modules.order
-+ rm -rf .tmp_versions Modules.symvers
++ $(MAKE) -C $(KERNEL_SRC) M=$(P_PWD) clean
+ $(RM) Module.markers modules.order
+ $(RM) $(P_PWD)/src/modules/kmod/client/kmod/Module.markers
+ $(RM) $(P_PWD)/src/modules/kmod/client/kmod/modules.order
diff --git a/recipes-kernel/lkrg/lkrg-module_0.9.2.bb b/recipes-kernel/lkrg/lkrg-module_0.9.3.bb
similarity index 90%
rename from recipes-kernel/lkrg/lkrg-module_0.9.2.bb
rename to recipes-kernel/lkrg/lkrg-module_0.9.3.bb
index 85f7d44..2553974 100644
--- a/recipes-kernel/lkrg/lkrg-module_0.9.2.bb
+++ b/recipes-kernel/lkrg/lkrg-module_0.9.3.bb
@@ -9,10 +9,11 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=5105ead24b08a32954f34cbaa7112432"

DEPENDS = "virtual/kernel elfutils"

-SRCREV = "43db5f19fca259feb1962f6db33382348cbc8320"
-
SRC_URI = "git://github.com/lkrg-org/lkrg.git;protocol=https;branch=main \
- file://makefile_cleanup.patch "
+ file://makefile_cleanup.patch \
+"
+
+SRCREV = "c578e9f786299b67ffd62057b4534b0bf4fb7ece"

S = "${WORKDIR}/git"

--
2.25.1


Re: LInker Errors: Cannot find crti.o/crtbeginS.o. No such file or directory. #honister #make #yocto

Khem Raj
 



On Thu, Jun 23, 2022 at 1:36 AM <douglas.cooper1@...> wrote:

Hello. Im trying to write a recipe for an autoconf based project. Ive managed to resolve most of the include and linker issues with the exception of the subject error. The files in question exist at <sysroot>/usr/lib64 and <sysroot>/usr/lib64/${TARGET_SYS}/10.3.1 and those paths appear to be on the file search path with sysroot set as expected. Any help would be appreciated.


It’s linker cmdline which is interesting here please post it and that will help to see further 





[PATCH yocto-autobuilder-helper] scripts/archive_buildstats.py: copy all buildstats

Randy MacLeod
 

As a first pass, collect all the tmp/buildstats logs
using 'cp -a', to enable review and graphing of all builds.
The goal is to understand the trends in the /proc/pressure/{cpu|io}
data that is now gathered as part of the buildstats system.

Signed-off-by: Aryaman Gupta <Aryaman.Gupta@...>
Signed-off-by: Randy MacLeod <Randy.MacLeod@...>
---
scripts/archive_buildstats.py | 27 +++++++++++++++++++++++++++
scripts/run-config | 1 +
2 files changed, 28 insertions(+)
create mode 100755 scripts/archive_buildstats.py

diff --git a/scripts/archive_buildstats.py b/scripts/archive_buildstats.py
new file mode 100755
index 0000000..bdbe9f4
--- /dev/null
+++ b/scripts/archive_buildstats.py
@@ -0,0 +1,27 @@
+#!/usr/bin/env python3
+#
+# SPDX-License-Identifier: GPL-2.0-only
+#
+
+import os, sys
+
+def usage():
+ print("Usage: " + sys.argv[0] + " <src> <dest> <target>")
+
+def main():
+ if len(sys.argv) != 4:
+ usage()
+ sys.exit()
+
+ builddir = sys.argv[1]
+ dest = sys.argv[2]
+ target = sys.argv[3]
+
+ bsdir = os.path.join(builddir, "tmp/buildstats")
+ directory = os.path.join(dest, target)
+
+ os.system('mkdir -p ' + directory)
+ # cp -a <path-to-worker-buildstats> <directory>
+ os.system('cp -a ' + builddir + ' ' + directory)
+
+main()
diff --git a/scripts/run-config b/scripts/run-config
index 838847a..953977e 100755
--- a/scripts/run-config
+++ b/scripts/run-config
@@ -334,6 +334,7 @@ elif args.phase == "finish" and args.stepname == "collect-results":
hp.printheader("Running results collection")
runcmd([scriptsdir + "/collect-results", args.builddir, args.results_dir, args.target])
runcmd([scriptsdir + "/summarize_top_output.py", args.results_dir, args.target])
+ runcmd([scriptsdir + "/archive_buildstats.py", args.builddir, args.results_dir, args.target])
sys.exit(0)

if jcfg:
--
2.32.0


LInker Errors: Cannot find crti.o/crtbeginS.o. No such file or directory. #honister #make #yocto

douglas.cooper1@...
 

Hello. Im trying to write a recipe for an autoconf based project. Ive managed to resolve most of the include and linker issues with the exception of the subject error. The files in question exist at <sysroot>/usr/lib64 and <sysroot>/usr/lib64/${TARGET_SYS}/10.3.1 and those paths appear to be on the file search path with sysroot set as expected. Any help would be appreciated.

1 - 20 of 57347