linux/poky.git/meta, branch 5.0_M3

openssh: Add a workaround for ICE on powerpc64le

2024-03-08T08:06:16+00:00

Fixes [YOCTO #15415] The new openssh version has an ICE on powerpc64le similar to the one on mips/mips64[1]. By adding flag "--without-hardening" to "./configure", compiler option "-fzero-call-used-regs" will be removed when compiling. This prevents certain functions from triggering the following ICE: unimplemented: argument 'used' is not supported for '-fzero-call-used-regs' on this target References [1] https://git.openembedded.org/openembedded-core/commit/?id=5b290566519a87c563945a033cb49863317ad63d (From OE-Core rev: bc793fa9d1fe24c102d91e97b7002b6e637cbfa5) Signed-off-by: William Lyu Signed-off-by: Richard Purdie

kernel-fitImage: only include valid compatible line

2024-03-08T08:06:16+00:00

Without this commit the configuration node includes the compatible line 'compatible = [00];' if EXTERNAL_KERNEL_DEVICETREE is not defined, i.e. if PREFERRED_PROVIDER_virtual/dtb is not used. This prevents u-boot from using this configuration and it prints the message "Could not find configuration node". An additional check also ensures that the written compatible line never contains an empty compatible. The functionality to add the compatible line was added in commit f4c82fb6da89 ("kernel-fitImage: add machine compatible to config section"). (From OE-Core rev: f8f3a52b2f924789552e6a3f889162ff07e0887f) Signed-off-by: Christian Taedcke Signed-off-by: Richard Purdie

go.bbclass: set GOPROXY

2024-03-08T08:06:16+00:00

The GOPROXY is already correctly defined on the native sys root and this can be checked using the bitbake devshell: | $ go env GOPROXY | https://proxy.golang.org,direct The go_do_compile task calls the compiler directly so the GOPROXY env is not seen because it's not defined in the shell. Defining it explicitly solves this problem and was to avoid setting it in the recipes itself. (From OE-Core rev: e0919a3f7bc26b1ea9fb57740de4a9a3b9253f26) Signed-off-by: Jose Quaresma Signed-off-by: Richard Purdie

systemd: Check for directory before chmod'ing it

2024-03-08T08:06:16+00:00

da9db878a15 systemd: fix dead link /var/log/README add -Dcreate-log-dirs=false which means journal dir will not be generated regardless of VOLATILE_LOG_DIR value if a distro decided to set VOLATILE_LOG_DIR=no this code path will be executes and the directory being operated upon wont exist ending in do_install errors chown: cannot access '/mnt/b/yoe/master/build/tmp/work/riscv64-yoe-linux/systemd/255.4/image/var/log/journal': No such file or directory (From OE-Core rev: e017f405bf6ae6c269a8c9c981878fd1ad8666b6) Signed-off-by: Khem Raj Cc: Changqing Li Signed-off-by: Richard Purdie

bmaptool: Add bmap-tools runtime alias for compatibility

2024-03-08T08:06:16+00:00

The rename of bmap-tools to bmaptool creates an incompatibility that will break package feeds. Restore package feed compatibility by adding a bmap-tools runtime alias. Acked-by: Otavio Salvador (From OE-Core rev: fba4ac04524c5c3fa04a51b6e0679276327115ad) Signed-off-by: Tom Hochstein Signed-off-by: Richard Purdie

go: filter out build specific path from the linker flags

2024-03-07T17:27:51+00:00

patch 0007-exec.go-do-not-write-linker-flags-into-buildids.patch removes linker flags from buildids for not breaking reproducibility, but it seems that this will make go not rebuild when linker flag changes, Refer [1]. So remove this oe-specific patch, and change to filter out build specific path from the linker flags [1] https://github.com/golang/go/issues/63760 (From OE-Core rev: 6873c6cb000b24c1badd0fb8b5cd2d0a31a63096) Signed-off-by: Changqing Li Signed-off-by: Richard Purdie

systemd: remove systemd-bus-proxy settings

2024-03-07T17:27:51+00:00

systemd-bus-proxy was removed since v230. >From the NEWS file: """ * systemd-bus-proxyd has been removed, as kdbus is unlikely to still be merged into the kernel in its current form. """ (From OE-Core rev: e99003b244507d8586b1f878765aa4a546a767ef) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

systemd: use RDEPENDS for systemd-vconsole-setup

2024-03-07T17:27:51+00:00

With NO_RECOMMENDATIONS set to "1", systemd-vonsole-setup.service will fail because it invokes /usr/bin/loadkeys, which is from kbd. The RRECOMMENDATION should be changed to RDEPENDS, because it's not a recommenation, instead it's necessary. (From OE-Core rev: 6126d2dfab3f6bafe23d4dce805110784d23acb1) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie

systemd: fix dead link /var/log/README

2024-03-07T17:27:51+00:00

There are 2 issues here: First, in package systemd, there is a file /usr/lib/tmpfile.d/legacy.conf, which will create a symlink to /usr/share/doc/systemd/README.logs during boot time. But for oe, /usr/share/doc/systemd/README.logs is packaged in systemd-doc, which will make /var/log/README is dead link. Second, the symlink /var/log/README in legacy.conf use relative path: "L /var/log/README - - - - ../../usr/share/doc/systemd/README.logs" But for oe, when VOLATILE_LOG_DIR is true, /var/log is a link to /var/volatile/log, so /var/log/README need link to ../../../usr/share/doc/systemd/README.logs, while VOLATILE_LOG_DIR is false, /var/log is a dir, so /var/log/README need link to ../../usr/share/doc/systemd/README.logs. So current symlink in legacy.conf will also make it a dead link when VOLATILE_LOG_DIR is true. Turn off CREATE_LOG_DIRS to avoid these issues. (From OE-Core rev: 18d46e11d85da1f6feaba5a135931e43060024d6) Signed-off-by: Changqing Li Signed-off-by: Richard Purdie

rxvt-unicode: Fix installing of terminfo

2024-03-07T17:27:51+00:00

For cross compile, TIC will be native tic in recipe-sysroot-native, and the terminfo path will be native path, the rxvt-unicode terminfo will be wrongly installed to native path. install terminfo to correct path in do_install (From OE-Core rev: daff3b4bf9d7b77a8170d9bc6f0b9c81b0a077d7) Signed-off-by: Changqing Li Signed-off-by: Richard Purdie