Chromium 120.0.6099.224 fails to build with mickledore branch

[rjanani-p]

Hi ,
I am facing build issue for mickledore branch for Chromium 120.0.6099.224 version , I have added the chromium package to the build (IMAGE_INSTALL:append = " chromium-x11") in local.conf .
I am attaching the build log for reference. I would like to know what steps I need to take to build works,

It is failing at do_copy_target_rustlibs task,

0: chromium-x11-120.0.6099.224-r0 do_copy_target_rustlibs - 0s (pid 4010289)
ERROR: chromium-x11-120.0.6099.224-r0 do_copy_target_rustlibs: ExecutionError('build/tmp-glibc/work/core2-64-wrs-linux/chromium-x11/120.0.6099.224-r0/temp/run.do_copy_target_rustlibs.4010289', 1, None, None)
ERROR: Logfile of failure stored in: build/lts23base_build/tmp-glibc/work/core2-64-wrs-linux/chromium-x11/120.0.6099.224-r0/temp/log.do_copy_target_rustlibs.4010289
Log data follows:
| DEBUG: Executing shell function do_copy_target_rustlibs
| cp: cannot stat 'build/lts23base_build/tmp-glibc/work/core2-64-wrs-linux/chromium-x11/120.0.6099.224-r0/recipe-sysroot/usr/lib/rustlib/x86_64*': No such file or directory
| WARNING: build/tmp-glibc/work/core2-64-wrs-linux/chromium-x11/120.0.6099.224-r0/temp/run.do_copy_target_rustlibs.4010289:150 exit 1 from 'cp -r $rustlib_src_dir "/build/lts23base_build/tmp-glibc/work/core2-64-wrs-linux/chromium-x11/120.0.6099.224-r0/recipe-sysroot-native/usr/lib/rustlib"'
| WARNING: Backtrace (BB generated script):
| #1: do_copy_target_rustlibs, /build/lts23base_build/tmp-glibc/work/core2-64-wrs-linux/chromium-x11/120.0.6099.224-r0/temp/run.do_copy_target_rustlibs.4010289, line 150
| #2: main,/build/lts23base_build/tmp-glibc/work/core2-64-wrs-linux/chromium-x11/120.0.6099.224-r0/temp/run.do_copy_target_rustlibs.4010289, line 153

[MaxIhlenfeldt]

Does build/lts23base_build/tmp-glibc/work/core2-64-wrs-linux/chromium-x11/120.0.6099.224-r0/recipe-sysroot/usr/lib/rustlib exist? If yes, what do its contents look like?

[rjanani-p]

rustlib is not present in following path
build/lts23base_build/tmp-glibc/work/core2-64-wrs-linux/chromium-x11/120.0.6099.224-r0/recipe-sysroot/usr/lib/rustlib, to get rust lib any steps I need to perform? could you please share your input.

[MaxIhlenfeldt]

I'll do a build using mickledore myself and will check, I think that's easier.

[rjanani-p]

sure, @MaxIhlenfeldt , thanks for the sharing the inputs.

[MaxIhlenfeldt]

Hm, my build is now happily compiling, that means the do_copy_target_rustlibs task finished successfully. Can you please share the build configuration bitbake prints when you start a build?

This is what I get:

Build Configuration:
BB_VERSION           = "2.4.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "debian-12"
TARGET_SYS           = "aarch64-oe-linux"
MACHINE              = "qemuarm64"
DISTRO               = "nodistro"
DISTRO_VERSION       = "nodistro.0"
TUNE_FEATURES        = "aarch64 armv8a crc cortexa57"
TARGET_FPU           = ""
meta
meta-poky            = "HEAD:7235399a86b134e57d5eb783d7f1f57ca0439ae5"
meta-clang           = "HEAD:ca6c714d4a807f199db009bf4be293640623d7af"
meta-chromium        = "master:0fcfadca55fa36c48ef09ff85c82d5bcde39540b"
meta-oe              = "HEAD:8e1f0fa6bfac0e96fedc666fe9066f92c85afb27"

[rjanani-p]

I have tried build 2 times to cross check but getting same issue. Here I am attaching the Build Configuration for more inputs. Could you please suggest any modifications I need to do in build configuration.

BB_VERSION = "2.4.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "ubuntu-22.04"
DISTRO = "wrlinux"
DISTRO_VERSION = "10.23.30.6"
MACHINE = "qemuarm64"
DEFAULTTUNE = "cortexa57"
TARGET_SYS = "aarch64-wrs-linux"
TUNE_FEATURES = "aarch64 armv8a crc cortexa57"
TARGET_FPU = ""
XILINX_XSCT_VERSION = "2023.2"
XILINX_RELEASE_VERSION = "v2023.2"
lib32: TARGET_SYS = "aarch64-wrsmllib32-linux-gnueabi"
lib32: TUNE_FEATURES = "arm armv7ve vfp thumb callconvention-hard"
lib32: TARGET_FPU = "hard"
meta = "HEAD:a6750f0576f940dcc13ae7cf297d1a5d53517272"
meta-xfce
meta-oe
meta-poky = "HEAD:0189a80818acd0b1ae0a8cef616f53803442f828"
meta-clang = "HEAD:de872f7b72923cd2474b39d444500ce3af929720"
meta-chromium = "BASE:23843b037e853696e35d14773d28f8b9f83198c0"

[MaxIhlenfeldt]

How do you set up your sources? The commit hashes listed don't seem to map to commits in the repositories (e.g. kraj/meta-clang@de872f7 doesn't exist, and neither does 23843b0).

[rjanani-p]

We are maintaining mickledore branch internally that's the reason difference in commit id's and I have cross checked the meta-clang and remaining layers those are having the mickledore latest commit changes, could you please share your input how to resolve this issue.

[rwmacleod]

@rjanani-p please try to reproduce the issue without using WR Linux layers.

[rjanani-p]

@rwmacleod I have tried to reproduce the issue using poky mickledore branch (without using WR Linux layers) but I am unable to reproduce the issue. But why it is reproducing for WR linux branch not understanding. I am sharing the build configuration to reproduce the issue for reference.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "2.4.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "universal"
TARGET_SYS = "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO = "poky"
DISTRO_VERSION = "4.2.4"
TUNE_FEATURES = "m64 core2"
TARGET_FPU = ""
meta
meta-poky
meta-yocto-bsp = "mickledore:7235399a86b134e57d5eb783d7f1f57ca0439ae5"
meta-filesystems
meta-gnome
meta-initramfs
meta-multimedia
meta-networking
meta-oe
meta-perl
meta-python
meta-webserver
meta-xfce = "mickledore:8e1f0fa6bfac0e96fedc666fe9066f92c85afb27"
meta-clang.git = "mickledore:ca6c714d4a807f199db009bf4be293640623d7af"
meta-chromium = "master:0fcfadca55fa36c48ef09ff85c82d5bcde39540b"
meta-raspberrypi.git = "mickledore:9c81413d0b6f41f14f0f9c504d19e312c5b9958f"

could you please share your inputs

[rwmacleod]

@rjanani-p let's deal with the problem ourselves, it's nothing for@MaxIhlenfeldt to work on or worry about. For now, please resolve this issue as not reproducible or something like that.

[rjanani-p]

okay sure @rwmacleod , I will close the issue

[rjanani-p]

unable to reproducing the issue, hence closing the issue. Thank you.