Persistent build error about missing libclang_rt.builtins.a

[tronje]

Hi, I'm getting the same error as in #947, and #962 does not fix it for me. I'm using the current master state of meta-browser. Here's the error again:

ERROR: chromium-x11-146.0.7680.177-r0 do_compile: Execution of '/workdir/build/tmp/work/corei7-64-poky-linux/chromium-x11/146.0.7680.177/temp/run.do_compile.1031968' failed with exit code 1
ERROR: Logfile of failure stored in: /workdir/build/tmp/work/corei7-64-poky-linux/chromium-x11/146.0.7680.177/temp/log.do_compile.1031968
Log data follows:
| DEBUG: Executing shell function do_compile
| ninja: error: '../../../../recipe-sysroot-native/usr/lib/clang/latest/lib/x86_64-unknown-linux-gnu/libclang_rt.builtins.a', needed by 'yocto_native_for_rust_host_build_tools/obj/build/rust/allocator/liballoc_error_handler_impl.a', missing and no known rule to make it
| WARNING: /workdir/build/tmp/work/corei7-64-poky-linux/chromium-x11/146.0.7680.177/temp/run.do_compile.1031968:148 exit 1 from 'ninja -v -j 20 chrome chrome_sandbox chromedriver.unstripped'
| WARNING: Backtrace (BB generated script):
| 	#1: do_compile, /workdir/build/tmp/work/corei7-64-poky-linux/chromium-x11/146.0.7680.177/temp/run.do_compile.1031968, line 148
| 	#2: main, /workdir/build/tmp/work/corei7-64-poky-linux/chromium-x11/146.0.7680.177/temp/run.do_compile.1031968, line 152
ERROR: Task (/workdir/layers/openembedded-core/../meta-browser/meta-chromium/recipes-browser/chromium/chromium-x11_146.0.7680.177.bb:do_compile) failed with exit code '1'

Any help? I'm quite puzzled by this.

I've tried with various versions of the other common layers (meta-yocto, openembedded-core, meta-openembedded, etc.), including their latest master states. I've also tried with and without meta-clang. meta-clang generally puzzles me a bit, because it doesn't actually provide a recipe for clang anymore.

Thanks very much for all your work!

[MaxIhlenfeldt]

Can you try the latest master (just updated) together with https://github.com/user-attachments/files/26764737/0008-Use-the-correct-path-to-libclang_rt.builtins.a.patch (from #973 (comment))?

[tronje]

Can you try the latest master (just updated) together with https://github.com/user-attachments/files/26764737/0008-Use-the-correct-path-to-libclang_rt.builtins.a.patch (from #973 (comment))?

It works! Sorry for taking so long to respond, but it took 4 hours to compile Chromium on my machine, and I wanted to be sure it succeeds.

Thanks very much!

[BigPapa314]

Hmm I have the same problem:

ERROR: chromium-ozone-wayland-147.0.7727.55-r0 do_compile: Execution of '/build/tmp/work/cortexa76-poky-linux/chromium-ozone-wayland/147.0.7727.55/temp/run.do_compile.94353' failed with exit code 1
ERROR: Logfile of failure stored in: /build/tmp/work/cortexa76-poky-linux/chromium-ozone-wayland/147.0.7727.55/temp/log.do_compile.94353
Log data follows:
| DEBUG: Executing shell function do_compile
| ninja: error: '../../../../recipe-sysroot-native/usr/lib/clang/latest/lib/linux/libclang_rt.builtins-aarch64.a', needed by 'obj/build/rust/allocator/liballoc_error_handler_impl.a', missing and no known rule to make it
| WARNING: exit code 1 from a shell command.
ERROR: Task (/build/../sources/meta-browser/meta-chromium/recipes-browser/chromium/chromium-ozone-wayland_147.0.7727.55.bb:do_compile) failed with exit code '1'

Used Sources:

0001-Drop-GN-compiler-settings-conflicting-with-OE.patch         0007-Fix-constexpr-variable-must-be-initialized-by-a-cons.patch  0013-Reduce-minimum-browser-window-width-to-480px.patch
0001-Fix-building-gpu_host_impl.cc-on-Linux.patch                0008-Use-the-correct-path-to-libclang_rt.builtins.a.patch        chromium-145-zip_ffi_glue-use-edition2024.patch
0002-v8-qemu-wrapper.patch                                       0009-Adjust-the-Rust-build-to-our-needs.patch                    chromium-147.0.7727.55
0003-wrapper-extra-flags.patch                                   0010-Don-t-require-profiler_builtins.rlib.patch                  fix-SYS_SECCOMP-redefinition.patch
0004-Delete-compiler-options-not-available-in-release-ver.patch  0011-fix-check_version-Only-compare-node.js-major-version.patch  use-adler2.patch
0005-avoid-link-latomic-failure-on-CentOS-8-host.patch           0012-chromium-fix-v4l2-compiler-error-on-arm.patch

[jcalvinowens]

Huh, so I was half right (testing raspberrypi3 now):

debian trixie building wrynose: FAIL
debian trixie building whinlatter: OK
gentoo building wrynose: FAIL
gentoo building whinlatter: FAIL

I will try to figure out what makes the second case different...

[BigPapa314]

I've got the following locations of the archive:

recipe-sysroot-native/usr/lib/clang/latest/lib/linux/libclang_rt.builtins-x86_64.a
recipe-sysroot-native/usr/lib/clang/latest/lib/aarch64-poky-linux-gnu/libclang_rt.builtins.a
recipe-sysroot-native/usr/lib/clang/latest/lib/x86_64-unknown-linux-gnu/libclang_rt.builtins.a

[BigPapa314]

I'm using wrynose and try to cross compile for arm64.

[BigPapa314]

Maybe we have to switch on host_cpu and not current_cpu for native tool selection?

[jcalvinowens]

Augh, I mixed up which branch I was testing on the second Debian machine... all four cases actually fail for me (with MACHINE=raspberrypi3). The distro difference was a red herring.

The difference for me is simply setting TARGET_VENDOR in my distro config. If I undo that in my layer:

-TARGET_VENDOR = "-${DISTRO}"
-HOST_VENDOR = "-${DISTRO}"
+#TARGET_VENDOR = "-${DISTRO}"
+#HOST_VENDOR = "-${DISTRO}"

...then it defaults to "oe", and chromium-ozone-wayland builds successfully as-is on both wrynose and whinlatter, without the 0008 patch.

(I didn't actually wait for the build to finish, just long enough to be sure it didn't get hung up on this failure.)

Digging into that more, I think the root issue is actually that the sed which replaces -oe- with -unknown- needs to instead replace "${TARGET_VENDOR}-" with "-unknown-". That fixes the problem without changing TARGET_VENDOR or adding the 0008 patch back on both whinlatter and wrynose.

Does #976 fix the problem for everyone else?