Bug 920335 – www-client/chromium-121.0.6167.8 fails to compile: ../../third_party/llvm-build/Release+Asserts/lib/clang/18/lib/x86_64-unknown-linux-gnu/libclang_rt.builtins.a', needed by 'obj/third_party/protobuf/libprotoc_lib.a', missing and no known rule to make it

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description François Valenduc 2023-12-19 18:23:12 UTC]

Almost everything is in the subject, I tried to compile chromium-121.0.6167.8, which I found in this overlay: https://github.com/Kangie/gentoo

It immediately fails with this error: 

Done. Made 19336 targets from 3569 files in 14320ms
>>> Source configured.
>>> Compiling source in /var/tmp/portage/www-client/chromium-121.0.6167.8/work/chromium-121.0.6167.8 ...
 * Checking whether python3_11 is suitable ...
 *   dev-lang/python:3.11[xml(+)] ...
 [ ok ]
 *   python_check_deps ...
 *     dev-python/setuptools[python_targets_python3_11(-)] ...
 [ ok ]
 [ ok ]
 * Using python3.11 to build (via EPYTHON)
ninja -v -j17 -l18 -C out/Release chrome chromedriver chrome_sandbox
ninja: Entering directory `out/Release'
ninja: error: '../../third_party/llvm-build/Release+Asserts/lib/clang/18/lib/x86_64-unknown-linux-gnu/libclang_rt.builtins.a', needed by 'obj/third_party/protobuf/libprotoc_lib.a', missing and no known rule to make it
 * ERROR: www-client/chromium-121.0.6167.8::scaleway failed (compile phase):
 *   ninja -v -j17 -l18 -C out/Release chrome chromedriver chrome_sandbox failed

Is it really trying to use clang-18 which is for sure far from being stable ?

Reproducible: Always

[Comment 1 Sam James 2023-12-20 07:32:50 UTC]

Please include the build.log and emerge --info.

Anyway, I think this is kind-of expected. I know Kangie is still working on it which is why it's in a different branch (https://github.com/Kangie/gentoo/tree/chromium-121/beta/www-client/chromium).

This repository isn't in repositories.xml and I don't think it's intended as an overlay, it's just Kangie's development repo, so not really sure how to assign this. I'll call it INVALID but Kangie can reopen it if he wants.

[Comment 2 Sam James 2023-12-20 07:33:12 UTC]

(But if you're interested in helping with Chromium ebuilds, that's very welcome, just say that & perhaps lurk in #gentoo-chromium on IRC.)

[Comment 3 Matt Jolly 2023-12-20 07:48:30 UTC]

Hi François,

You have stumbled across my development fork of the Gentoo repo where I stage changes before they're submitted to ::gentoo

Chromium 121 requires rust as a build prerequisite. When that is selected, even when it knows to use the system toolchains, it will select the bundled clang toolchain - which google bumps every fortnight. It is absolutely trying to use clang 18 - that's what google build with upstream and ship with the chromium tarball.

Unfortunately I only got as far as wiring up system Rust before I decided to take a break last week, using the right clang version is next on my list!

I'm sorry you came across a broken / work in progress ebuild, but if you're interested in  chromium on Gentoo or want to learn more about  packaging we are always looking for help and I'm happy to provide some guidance. Please reach out on IRC as Sam mentioned.

[Comment 4 François Valenduc 2023-12-20 07:54:28 UTC]

Thanks for your information. I don't think I know chromium and ebuilds enough to help on the development. So I will wait until your ebuild really works. I simply wanted to try chromium 121 since I am unable to build chromium 120 on all my gentoo systems for a very strange reason (see bug #919812). On some systems, it works, on other it fails with the error mentioned in this bug.