linux/poky.git/meta/classes-recipe, branch walnascar

systemd.bbclass: Make systemd_postinst run as intended

2025-09-22T19:21:23+00:00

After the switch from using a systemctl written in Python to using the official version of systemctl from the systemd project, the systemd_postinst function has effectively not been executed during the rootfs creation. The reason is that systemctl provided by systemctl-native fails if run without arguments (as systemd_postinst does): Failed to connect to system scope bus via local transport: Operation not permitted (consider using --machine=@.host --user to connect to bus of other user) This is not seen in the logs since stderr is sent to /dev/null, and the only way to tell that there is a problem is because systemd services that are expected to be enabled aren't running. The reason this has gone unnoticed is because systemd_handle_machine_id in rootfs-postcommands.bbclass will call systemctl preset-all, which in most cases will create the missing links to enable the systemd services. This change effectively reverts commit a52e66762c0c51918b1ba3d4622759637b6e920a (systemd.bbclass: update command to check systemctl available) and instead only runs systemctl without arguments (to determine that it can communicate with systemd) when executed on target. (From OE-Core rev: 6cb4239b412dc782f66728e47753c1a82cccf759) Signed-off-by: Peter Kjellerstedt Signed-off-by: Steve Sakoman

rust-target-config: Add has-thread-local option

2025-09-09T16:30:07+00:00

The "has-elf-tls" option was removed by the commit 8e1614a906086fb46c5dd7b7f2dffab91194165c. However is should have been renamed to "has-thread-local", since it was renamed and not removed in rust by this commit. https://github.com/rust-lang/rust/commit/391332c5d9d5a5e97a0d36e011a87ad43045cfd3 (From OE-Core rev: 575a4316f661392eb73d1d97300511e2bca24ada) Signed-off-by: Per x Johansson Signed-off-by: Peter Kjellerstedt Signed-off-by: Steve Sakoman

testimage: get real os-release file

2025-06-20T16:21:27+00:00

/etc/os-release is a symlink to /usr/lib. Symlink is retrieved as a dead link which points to nowhere if also the original file is not accompanying it. Fetch the real file in addition to this link. Alternative could be to use "tar -h" (supported also by busybox tar), however that could lose some important information if links are relevant for failure analysis. (From OE-Core rev: ed43f9ccb3c08845259e24440912631afd780d12) (From OE-Core rev: 93efeca19f53132fce84d914b7ebf21070370127) Signed-off-by: Peter Marko Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman

systemd.bbclass: generate preset for templates

2025-06-13T16:01:26+00:00

There was a regression introduced by the change to use systemd-systemctl-native rather than a python fake implementation, which caused template units to not be properly enabled when set in the SYSTEMD_SERVICE variable. Through investigation, it seems that the best way to re-enable template instances is to handle them explicitly in the systemd.bbclass and enable them with `preset`, like most units are handled[1,2]. Per the systemd.preset manpage, the format for template units is different than for regular units[3]. We need to coalesce all the template instances onto a single line and emit them as an additional space-deliminated argument. Ran this against openbmc's phosphor-ipmi-net recipe and generated the following preset file: ``` $ cat packages-split/phosphor-ipmi-net/usr/lib/systemd/system-preset/98-phosphor-ipmi-net.preset enable phosphor-ipmi-net@.service eth0 enable phosphor-ipmi-net@.socket eth0 ``` [1]: https://lore.kernel.org/openembedded-core/Z2ch.1747051947055246176.oktf@lists.openembedded.org/ [2]: https://lore.kernel.org/openembedded-core/aDdoTVtCmElpURYD@heinlein/ [3]: https://www.freedesktop.org/software/systemd/man/latest/systemd.preset.html Fixes: 7a580800db39 ("systemd: Build the systemctl executable") (From OE-Core rev: f33d9b1f434e40a459614d8dc21ce45e11581008) (From OE-Core rev: ea207dce1f5f8579d8ddde487ac9852f50bfc792) Signed-off-by: Patrick Williams Signed-off-by: Richard Purdie Signed-off-by: Steve Sakoman

module.bbclass: add KBUILD_EXTRA_SYMBOLS to install

2025-05-19T15:57:20+00:00

Symbols are used during install as well, adding KBUILD_EXTRA_SYMBOLS enables successful installation. | DEBUG: Executing shell function do_install | NOTE: make -j 22 KERNEL_SRC=xxx/kernel-source -C xxx/drivers KDIR=xxx/kernel-source DEPMOD=echo MODLIB=xxx/image/lib/modules/6.6.75-yocto-standard-00189-g530c419bc9db INSTALL_FW_PATH=xxx/image/lib/firmware CC=aarch64-poky-linux-gcc -fuse-ld=bfd -fcanon-prefix-map LD=aarch64-poky-linux-ld.bfd OBJCOPY=aarch64-poky-linux-objcopy STRIP=aarch64-poky-linux-strip O=xxx/kernel-build-artifacts modules_install | make: Entering directory 'xxx/drivers' | make -C xxx/kernel-source M=xxx/drivers modules | make[1]: Entering directory 'xxx/kernel-source' | make[2]: Entering directory 'xxx/kernel-build-artifacts' | MODPOST xxx/drivers/Module.symvers | ERROR: modpost: "xxx" [xxx/xxx.ko] undefined! (From OE-Core rev: c6ded848334807962967d2c6c7589fcc9feceb0d) Signed-off-by: Alon Bar-Lev Signed-off-by: Mathieu Dubois-Briand Signed-off-by: Richard Purdie (cherry picked from commit 0ef80eeda967a9e04ff91c3583aabbc35c9868e8) Signed-off-by: Steve Sakoman

cargo.bbclass: show PACKAGECONFIG_CONFARGS in bbnote

2025-03-25T21:20:41+00:00

* PACKAGECONFIG_CONFARGS was added in: https://git.openembedded.org/openembedded-core/commit/?id=16745b20452de60ae2474433cc1a2fb1ed9f6a64 but it wasn't added in bbnote above which might lead to confusing errors like I got now: NOTE: cargo build -v --frozen --target aarch64-webos-linux-gnu --release --manifest-path=.../git//Cargo.toml error: unexpected argument '--cfg' found Usage: cargo build --verbose... --frozen --target [] --release --manifest-path and was wondering where --cfg came from. * it was from recipe where we already use: RUSTFLAGS:append = " ${PACKAGECONFIG_CONFARGS}" it will be difficult to use PACKAGECONFIG for RUSTFLAGS and prevent them to be used here for cargo as well, what about the recipes which need them to explicitly append them to CARGO_BUILD_FLAGS ? (From OE-Core rev: 38d953b2ffd4e0cee9e77f97988e44be105023c6) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

cargo: pass PACKAGECONFIG_CONFARGS to cargo build

2025-03-20T11:29:04+00:00

In order to allow rust packages to define PACKAGECONFIG options, append the contents of PACKAGECONFIG_CONFARGS to the build command. This patch was already submitted by Bartosz Golaszewski on older version but was never merged. It will be really usefull for Rust recipes. (From OE-Core rev: 16745b20452de60ae2474433cc1a2fb1ed9f6a64) Signed-off-by: Jean-Pierre Geslin Signed-off-by: Richard Purdie

autotools: require that a configure script exists

2025-03-18T11:25:36+00:00

There's no point inheriting autotools if you're not actually going to run a configure script, so make a missing configure script fatal. (From OE-Core rev: 6d327a39befae44a88a812bdf4acde800dcee57b) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

native: Drop export statements that aren't needed

2025-03-18T10:27:31+00:00

These are already exported by bitbake.conf, no need to export them again. (From OE-Core rev: 92e52f5afac4877366c1ee2e6c6f0d1f5df84410) Signed-off-by: Richard Purdie

native: follow BUILD_* definitions for OBJCOPY, OBJDUMP and READELF

2025-03-18T10:27:31+00:00

Set the host OBJCOPY, OBJDUMP, and READELF variables to be derived from their corresponding BUILD_* definitions. This makes the native class match the build-gcc.inc file 1 to 1, as these were the only missing. Currently these variables get their definitions from gcc.inc, which uses HOST_PREFIX, and that works because the native class sets HOST_PREFIX to BUILD_PREFIX, but this doesn't seem correct. (From OE-Core rev: 87a6ffe21b706e6aeeeb77891565cbd7730ca163) Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie