linux/poky.git/meta/classes, branch yocto-4.0.8

devshell: Do not add scripts/git-intercept to PATH

2023-02-24T16:41:46+00:00

The use of scripts/git-intercept was introduced in commit 3266c327df (install/devshell: Introduce git intercept script due to fakeroot issues) and later reverted in commit af27c81eaf (scripts: Make git intercept global). (From OE-Core rev: 70ee5f9d50bec6e708cd2006c11ef3d0bd7cab42) Signed-off-by: Peter Kjellerstedt Signed-off-by: Luca Ceresoli (cherry picked from commit f6c260c8e2a33e282a35afc99de4ef8cc1791b08) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

image.bbclass: print all QA functions exceptions

2023-02-24T16:41:46+00:00

For the QA checks in `image.bbclass`, all exceptions other than `oe.utils.ImageQAFailed` always print the following generic message: "Image QA function func_name failed" This can be very misleading, as it may hide python syntax errors and other kind of issues that are hard to detect without more explicit error messages. This change makes sure that the error message of all exceptions are displayed. Before this change: "Image QA function func_name failed" After this change: "Image QA function func_name failed: f-string: empty expression not allowed (, line 13)" (From OE-Core rev: 6c53d8d8c88fb06b19fbf5bdd754960b21531074) Signed-off-by: Mauro Queiros Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie (cherry picked from commit 3d85b30d8704d38b86f5b006748cebc74bd2a4fa) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

update-alternatives: fix typos

2023-02-24T16:41:46+00:00

(From OE-Core rev: 6b6f3cfe8995663b31482e70285863266dfd9d80) Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie (cherry picked from commit d3ca05b072c152b76a86edaaddebabdef312ea95) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

recipe_sanity: fix old override syntax

2023-02-15T21:46:56+00:00

(From OE-Core rev: 381fcdba555d0b56fcd4525d82bec851b3da95ec) Signed-off-by: Ulrich Ölmann Signed-off-by: Richard Purdie (cherry picked from commit 18eeea6fcd8ade49390a978134f51646da2f7764) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

libc-locale: Fix on target locale generation

2023-02-15T21:46:56+00:00

If on target locale generation is used, it fails at first boot showing errors about a missing directory. Ensure the directory exists. (From OE-Core rev: 258115c2a7d78f0416f952122c9448a805dab08f) Signed-off-by: Richard Purdie (cherry picked from commit f2844c9f1bbb729562063d96a3d1cc9d44dafa0a) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

testimage: Fix error message to reflect new syntax

2023-02-15T21:46:56+00:00

(From OE-Core rev: 03eced200a69ee64cb0efdca164e0d287314beac) Signed-off-by: Alejandro Enedino Hernandez Samaniego Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie (cherry picked from commit ec73d19d78e8f30ff9b817490c23bcdf8ea47c86) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

meta: remove True option to getVar and getVarFlag calls (again)

2023-02-15T21:46:56+00:00

* True is default since 2016 and most layers were already updated not to pass this parameter where not necessary, e.g. oe-core was updated couple times, first in: https://git.openembedded.org/openembedded-core/commit/?id=7c552996597faaee2fbee185b250c0ee30ea3b5f Updated with the same regexp as later oe-core update: https://git.openembedded.org/openembedded-core/commit/?id=9f551d588693328e4d99d33be94f26684eafcaba with small modification to replace not only d.getVar, but also data.getVar as in e.g.: e.data.getVar('ERR_REPORT_USERNAME', True) and for getVarFlag: sed -e 's|$d\.getVarFlag \?$( \?$[^,()]*, \?[^,()]*$, \?True)|\1(\2)|g' \ -i $(git grep -E 'getVarFlag ?$ ?([^,()]*), ?([^,()]*), ?True$' \ | cut -d':' -f1 \ | sort -u) (From OE-Core rev: de7bf6689a19dc614ce4b39c84ffd825bee1b962) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie (cherry picked from commit 26c74fd10614582e177437608908eb43688ab510) Signed-off-by: Steve Sakoman (cherry picked from commit 24a86d0c55ee89ae0dc77975e1d0ee02898d2289) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

scons.bbclass: Make MAXLINELENGTH overridable

2023-02-15T21:46:56+00:00

older scons do not support MAXLINELENGTH and some packages still may be using older scons, these recipes can clear SCONS_MAXLINELENGTH in them and get going. Set SCONS_MAXLINELENGTH = "" in such recipes. (From OE-Core rev: b4eaa248077305b75c551acb94223dbc524fc7a3) Signed-off-by: Khem Raj Cc: Martin Jansa Signed-off-by: Richard Purdie (cherry picked from commit 34de57d12c0a752f66c962d29e5335c1035db066) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

scons: Pass MAXLINELENGTH to scons invocation

2023-02-15T21:46:56+00:00

This helps in overcoming a problem when using scons with ccache enabled. When commands get longer, then it resorts to using response files to do the operations e.g. @/tmp/tmp96j6icra.lnk when this response file is inboked by compiler it works ok, however, this does not when ccache is used to invoke the complilation. We see errors e.g. ccache @/tmp/tmppsyij_0v.lnk ccache: error: execute_noreturn of @/tmp/tmppsyij_0v.lnk failed: No such file or directory Using MAXLINELENGTH setting ensures that we can use ARG_MAX to extend the length of commandline and hence avoid using response files. This issue is also reported in mongodb [1] [1] https://jira.mongodb.org/browse/SERVER-38389 (From OE-Core rev: b0e7777a911e236bda76e90258098057ed355953) Signed-off-by: Khem Raj Signed-off-by: Alexandre Belloni (cherry picked from commit 29558f6218f4676b459f2c78f82d245339d51c8c) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie

classes/fs-uuid: Fix command output decoding issue

2023-02-15T21:46:56+00:00

The default return value from subprocess.check_output is an encoded byte. The applied fix will decode the value to a string. (From OE-Core rev: ffa1de16fa82fbe7dfbed4c5ae0fc4e6d51e7ff3) Signed-off-by: Pawel Zalewski Signed-off-by: Alexandre Belloni (cherry picked from commit 046769fa952a511865c416b80d10af6287147fb7) Signed-off-by: Steve Sakoman Signed-off-by: Richard Purdie