Chromium fails to build with USE=libcxx due to an error related to clang revision -- the relevant part of the build log as follows: ERROR at //build/config/compiler/BUILD.gn:1407:22: Script returned non-zero exit code. clang_revision = exec_script("//tools/clang/scripts/update.py", ^---------- Current dir: /var/tmp/portage/www-client/chromium-113.0.5672.63/work/chromium-113.0.5672.63/out/Release/ Command: python3.11 /var/tmp/portage/www-client/chromium-113.0.5672.63/work/chromium-113.0.5672.63/tools/clang/scripts/update.py --print-revision --verify-version=17 Returned 1 and printed out: The expected clang version is llvmorg-17-init-4759-g547e3456-1 but the actual version is Did you run "gclient sync"? The installed version is clang is 16.0.3, 17.x is currently masked. As can be seen in the script output above, the actual version is shown as an empty string: https://github.com/chromium/chromium/blob/113.0.5672.63/tools/clang/scripts/update.py#L360 The stamp file seems to be "third_party/llvm-build/Release+Asserts/cr_build_revision" in the source tree: https://github.com/chromium/chromium/blob/113.0.5672.63/tools/clang/scripts/update.py#L54 And it's indeed contains only a newline: # hexdump -C /var/tmp/portage/www-client/chromium-113.0.5672.63/work/chromium-113.0.5672.63/third_party/llvm-build/Release+Asserts/cr_build_revision 00000000 0a |.| 00000001 With libcxx USE-flag disabled, the build continues past this point. libcxx is not critical to me, but it should be masked in case it's a broken configuration. Installed changes and use flags: sys-devel/llvm:16 abi_x86_64 llvm_targets_AMDGPU llvm_targets_X86 sys-devel/clang:16 abi_x86_64 extra llvm_targets_AMDGPU llvm_targets_X86 pie python_single_target_python3_11 static-analyzer sys-devel/clang-runtime:16 abi_x86_64 compiler-rt libcxx openmp sanitize sys-devel/gcc:12 cet cxx default-stack-clash-protection default-znow graphite hardened lto nptl openmp pie sanitize ssp vtv www-client/chromium:0 X cups custom-cflags libcxx pic proprietary-codecs system-harfbuzz system-icu vaapi Reproducible: Always
Thanks, duplicate of bug 905798. Can you post your analysis there? *** This bug has been marked as a duplicate of bug 905798 ***
Created attachment 861266 [details] build.log
(In reply to Sam James from comment #1) > Thanks, duplicate of bug 905798. Can you post your analysis there? Sorry, didn't find the mentioned bug. Of course, will forward there.
