Update chromium to 140.0.7339.136 and meta-chromium whinlatter support #923
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Chromium 138+ uses its bundled libc++ and compiler-rt. To ensure the build system uses these and does not fall back to system-provided runtime libraries, explicitly pass the target triple and disable system stdlib++. This avoids linker errors caused by missing crtbeginS.o, crtendS.o, and libgcc when using Clang with a minimal sysroot. Release Notes: https://chromereleases.googleblog.com/2025/07/stable-channel-update-for-desktop_15.html Build and patch changes: Added patches: 0011-fix-check_version-Only-compare-node.js-major-version.patch Updated patches: 0009-Adjust-the-Rust-build-to-our-needs.patch Removed patches: 0011-Disable-crabbyavif-to-fix-build-errors.patch 0012-Revert-Allow-and-use-std-hardware_destructive_interf.patch 0013-Revert-Set-Rust-symbol-visibility-to-hidden-when-C-s.patch 0014-pdfium-Fix-missing-PDFiumAPIStringBufferAdapter-temp.patch 0015-Revert-Connect-the-Rust-log-crate-to-the-base-loggin.patch License changes: Added licenses: third_party/compiler-rt/src/LICENSE.TXT third_party/libtess2/LICENSE third_party/llvm-libc/src/LICENSE.TXT third_party/net/third_party/mozilla_security_manager/LICENSE Removed licenses: third_party/accessibility-audit/LICENSE third_party/io_grpc_grpc_api/LICENSE third_party/libavifinfo/LICENSE Updated licenses: third_party/android_deps/libs/com_google_android_gms_play_services_auth/LICENSE → third_party/android_deps/autorolled/committed/libs/com_google_android_gms_play_services_auth/LICENSE third_party/android_deps/libs/com_google_android_gms_play_services_auth_api_phone/LICENSE → third_party/android_deps/autorolled/committed/libs/com_google_android_gms_play_services_auth_api_phone/LICENSE third_party/android_deps/libs/com_google_android_gms_play_services_auth_base/LICENSE → third_party/android_deps/autorolled/committed/libs/com_google_android_gms_play_services_auth_base/LICENSE third_party/android_deps/libs/com_google_android_gms_play_services_auth_blockstore/LICENSE → third_party/android_deps/autorolled/committed/libs/com_google_android_gms_play_services_auth_blockstore/LICENSE third_party/android_deps/libs/com_google_android_gms_play_services_fido/LICENSE → third_party/android_deps/autorolled/committed/libs/com_google_android_gms_play_services_fido/LICENSE third_party/android_deps/libs/com_google_android_libraries_identity_googleid_googleid/LICENSE → third_party/android_deps/autorolled/committed/libs/com_google_android_libraries_identity_googleid_googleid/LICENSE third_party/expat/src/expat/COPYING third_party/libjpeg_turbo/LICENSE Test-built chromium-ozone-wayland master, clang, MACHINE=qemux86-64 chromium-x11 master, clang, MACHINE=qemux86-64, qemuarm, qemuarm64 Repo hashes (from meta-chromium-test) meta-oe: commit: "a8dfd10600035a799abae03178fc7054582ea43d" poky: commit: "243d54fd466f5f852cc0fdcce57997918ce35f32" meta-clang: commit: "7a2f83360920b10214e2659e17a4b9cba2d0435b"
There are breaking changes in whinlatter in oe-core. Part of the changes was that meta-clang was merged into oe-core. There's no need to depend on meta-clang anymore. Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>
RUNTIME and TC_CXX_RUNTIME are both set explicitly to "llvm" in chromium.inc. Therefore the :runtime-llvm override is not needed because it's always on. But it's also a problem in whinlatter now, because the DEPENDS = "compiler-rt" is not applied properly, making do_copy_clang_library() fail. Remove :runtime-llvm override. Use TOOLCHAIN_NATIVE instead of TOOLCHAIN:class-native. Drop 0008-Use-the-correct-path-to-libclang_rt.builtins.a.patch and fix do_copy_clang_library() in a way that's compatible with clang in oe-core. Depend on lld-native. Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>
Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>
jcalvinowens
added a commit
to jcalvinowens/meta-browser
that referenced
this pull request
Sep 23, 2025
|
This was working for me on both master and master-next until the recent Rust upgrade [1]: Full command here: https://pastebin.com/raw/pz2cKdML [1] https://git.openembedded.org/openembedded-core/commit/?id=86d09ec9cd |
|
Can you try adding the patch from It looks like it has landed in the new stable chromium 141.0.7390.43. |
Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>
jcalvinowens
added a commit
to jcalvinowens/meta-browser
that referenced
this pull request
Sep 28, 2025
|
That did it. This PR works for now with these upstream SHAs: |
gn[-native] is shipped by oe-core since this commit:
commit e8dbf41f1f40ae3a5f9641429cad974f716f1f3e
Author: Khem Raj <raj.khem@gmail.com>
Date: Mon Sep 29 08:36:47 2025 -0700
gn: Add recipe
gn is a commonly used build tool to generate ninja files, used
in a lot of recipes e.g. chromium, qtwebengine, perfetto, hafnium etc.
these recipes come from different layers e.g. meta-qt6/meta-arm/meta-oe
since not all layers depend on meta-oe ( meta-arm does not ), its not
a possible option.
Given the usecases, putting it in core will benefit the ecosystem
and reduce some duplication. This recipe is taken from meta-arm
Disable maybe-initialized is a gcc specific option as error
Disable format warnings as errors, it adds -Wno-format explictly in
its build system
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>
kraj
approved these changes
Oct 2, 2025
otavio
approved these changes
Oct 2, 2025
jcalvinowens
added a commit
to jcalvinowens/meta-browser
that referenced
this pull request
Oct 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Builds on #920