linux/poky.git/meta/recipes-devtools, branch mickledore-next

python3-bcrypt-crates.inc: regenerate with updated bbclass

2023-04-06T13:28:59+00:00

* it's needed for compatibility with updated fetcher from: https://patchwork.yoctoproject.org/project/bitbake/patch/20230405122125.3358972-1-enrico.scholz@sigma-chemnitz.de/ * easiest way to regenerate these is: echo > meta/recipes-devtools/python/python3-bcrypt-crates.inc bitbake -c update_crates python3-bcrypt git commit (From OE-Core rev: ccef8f0b0d6e4e8b099953df3cf092b1545aca20) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

python3-cryptography-crates.inc: regenerate with updated bbclass

2023-04-06T13:28:59+00:00

* it's needed for compatibility with updated fetcher from: https://patchwork.yoctoproject.org/project/bitbake/patch/20230405122125.3358972-1-enrico.scholz@sigma-chemnitz.de/ * easiest way to regenerate these is: echo > meta/recipes-devtools/python/python3-cryptography-crates.inc bitbake -c update_crates python3-cryptography git commit (From OE-Core rev: bf6a3cd70d13f05f0e2af2b54635214690a68a78) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

qemu: rename deprecated --enable-trace-backend configure option

2023-04-05T16:26:53+00:00

qemu 6.2 deprecated the configure option '--enable-trace-backend' in favor of '--enable-trace-backends' [1] Rename accordingly. [1] https://wiki.qemu.org/ChangeLog/6.2#Build_Information (From OE-Core rev: 9e41fac1c2ee15aaff9926dac3c0233430adff12) Signed-off-by: Thomas De Schampheleire Signed-off-by: Richard Purdie

qemu: retain default trace backend if 'ust' is not enabled

2023-04-05T16:26:53+00:00

The qemu build system enables the 'log' trace backend by default, if no explicit choice was made with '--enable-trace-backend=CHOICE'. However, the qemu recipe uses the following PACKAGECONFIG line: PACKAGECONFIG[ust] = "--enable-trace-backend=ust,--enable-trace-backend=nop,lttng-ust," which means that the 'nop' trace backend will be explicitly selected if the 'ust' feature is not enabled. The 'nop' backend removes almost all trace points at compile time, and thus basically means 'disable tracing'. To retain the default trace backend if 'ust' is not enabled, the above PACKAGECONFIG line should either explicitly fall back to the 'log' backend, or not provide any value for the 'disabled' case. This commit chooses the latter to not make any assumption about the upstream default. (From OE-Core rev: c31396a30dcf17ab23ff4dd5943eef5fba20cba6) Signed-off-by: Thomas De Schampheleire Signed-off-by: Richard Purdie

qemu: make tracetool-generated output reproducible

2023-04-05T16:26:53+00:00

'#line' directives written by qemu's tracetool makes the 'debug' package not reproducible due to absolute paths. Apply a patch to use a relative path instead. (From OE-Core rev: 85e30c507b63fa9126887dc6435d1ee6e23bd887) Signed-off-by: Thomas De Schampheleire Signed-off-by: Richard Purdie

python3-pygobject: depend on gobject-introspection

2023-04-04T12:11:50+00:00

When g-i feature is disabled, the gobject-introspection package dependency is not pulled in but pygobject has a hard dependency on it. (From OE-Core rev: 7fae697c6889e17dd47415808a7173670b507047) Signed-off-by: Petr Kubizňák Signed-off-by: Richard Purdie

rust: update 1.67.1 -> 1.68.1

2023-04-04T12:11:50+00:00

Rebase patches; one of the vendored crossbeam versions has been removed upstream, and so crossbeam_atomic.patch is adjusted accordingly. Replace getrandom-open64.patch with a backport. (From OE-Core rev: f5accb4fae49342cbec21718ae7a427615bfcedd) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

rust: install llvm item only once

2023-04-04T12:11:50+00:00

Otherwise it triggers a rebuild of llvm-dependent rust pieces every time rust_runx is called, lengthening the builds without need. (From OE-Core rev: aca6b29b508175da9f213b1c6dba5d02a15b8287) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

rust: do not run separate build/install steps

2023-04-04T12:11:49+00:00

Upstream does not actually use or test it this way; if the goal is to install items, then install target should be executed directly. In particular, in latest rust release building stage 2 items has regressed altogether (incorrect dependencies between rust-analyze tool and the libs it needs) and no one noticed. (From OE-Core rev: 7d805f9a9f6b5048308a37a2757d08cca40b1ff3) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

python3: Fix failing sysconfig.py test on x86(64 bit) using lib64 as baselib by updating test_sysconfig for posix_user purelib

2023-04-03T10:39:59+00:00

Steps to trigger the failed test: Edit local.conf to add something as follows: BASELIB = "lib64" IMAGE_INSTALL:append = " python3-tests". bitbake core-image-sato runqemu qemux86-64 nographic slirp Reproducer: $python3 -m test test_sysconfig sysconfig.py use platlibdir for purelib. Update test_sysconfig.test_user_similar() for the posix_user scheme: "purelib" doesn't use sys.platlibdir. (From OE-Core rev: 755321362e994a6a37a0f554b1aea56823de924e) Signed-off-by: Wentao Zhang Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie