chromium: Upgrade to 145.0.7632.159

[zboszor]

Release Notes:
https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop.html

Build and patch changes:
------------------------

Removed patches: None

Modified patches:
* 0001-Drop-GN-compiler-settings-conflicting-with-OE.patch
* 0001-Fix-building-gpu_host_impl.cc-on-Linux.patch
* 0003-wrapper-extra-flags.patch
* 0009-Adjust-the-Rust-build-to-our-needs.patch
* 0013-Reduce-minimum-browser-window-width-to-480px.patch

New patches:
* chromium-145-zip_ffi_glue-use-edition2024.patch

  zip_ffi_glue needs Rust 2024 Edition due to the let chains used
  in Chromium 145

License changes:
----------------

Added licenses:
* third_party/android_deps/autorolled/committed/libs/org_jetbrains_kotlinx_atomicfu_jvm/LICENSE
* third_party/litert/LICENSE
* third_party/nlohmann_json/LICENSE

Removed licenses:
* third_party/android_deps/libs/org_jetbrains_kotlinx_atomicfu_jvm/LICENSE
* third_party/webrtc/rtc_base/third_party/sigslot/LICENSE

Updated licenses:
* third_party/ffmpeg/CREDITS.chromium
* third_party/screen-ai/THIRD_PARTY_LICENSES

Test-built:
-----------

* chromium-ozone-wayland
  * MACHINE=intel-corei7-64, qemuarm64, raspberrypi3

* chromium-x11
  * MACHINE=intel-corei7-64, qemuarm64, raspberrypi3

Test dependencies:
------------------

* URI: git://git.openembedded.org/openembedded-core
  - branch: master
  - revision: 531f87111d83430615f2e20dd41a3dd5fc25c7ab

* URI: git://git.openembedded.org/meta-openembedded
  - layers: meta-oe
  - branch: master
  - revision: 6b55bede28261c38fb1da1474ca5c991ac414c93

* URI: git://git.yoctoproject.org/meta-intel
  - branch: master
  - revision: a885c3a6fe5475de198899f4c40435b254fcbccc

* URI: https://github.com/agherzan/meta-raspberrypi
  - branch: master
  - revision: 9720dc611cf38ff2990bdf0f6afa106645ca1f93

Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>

Also contains #962

[zboszor]

With the new commit for gn, Chromium 145 can also be built for whinlatter.
Probably it would be best if oe-core cherry-picked the gn changes into whinlatter.

[zboszor]

Chromium 145 modified the substitution pattern in the wrapper script, which made it fail to start. Fixed now.

[zboszor]

Rebased over #965 and therefore the new state of #962

[MaxIhlenfeldt]

I'll defer my review on this until #962 has been merged.

[zboszor]

I'll defer my review on this until #962 has been merged.

Please also see the mail from oe-core where you were cc-ed. Long story short: They don't want to backport gn recipe changes to whinlatter because it contains new features.

But the old commit revision of gn does not work for Chromium 145, exactly due to missing features in the initial state of the recipe that went into oe-core/whinlatter.

I think meta-browser needs a whinlatter branch now, where the bbappend added here can be carried forward. It can be branched off after #962 is merged.

Then the PRs for Chromium 145 and 146 (#963 and #964 , respectively) for master would not need this bbappend. The single commits from each PR may be cherry-picked into whinlatter.

FWIW, the build of 146 for whinlatter (x86_64, glibc) is in progress ATM, but it seems it will finish correctly. It's way past the point where it built that bytemuck module (for which a patch was added) so Rust 1.90 in whinlatter is still good to build the latest version.

[zboszor]

Rebased over current master with #962 merged.

[thorstenl312]

Hello,

I am running into the following do_compile failure when building v144/v145. I believe the problem has to do with do_copy_clang_library()

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: /build/build/arago-tmp-default/work/aarch64-oe-linux/chromium-ozone-wayland/142.0.7444.175/temp/run.do_compile.628953:146 exit 1 from 'ninja -v -j 64 chrome chrome_sandbox chromedriver.unstripped'
WARNING: Backtrace (BB generated script): 
	#1: do_compile, /build/build/arago-tmp-default/work/aarch64-oe-linux/chromium-ozone-wayland/142.0.7444.175/temp/run.do_compile.628953, line 146
	#2: main, /build/build/arago-tmp-default/work/aarch64-oe-linux/chromium-ozone-wayland/142.0.7444.175/temp/run.do_compile.628953, line 150

Here are my variables:

BUILD_ARCH="x86_64"
BUILD_SYS="x86_64-linux"
RUST_BUILD_SYS="x86_64-unknown-linux-gnu"
RUST_TARGET_SYS="aarch64-oe-linux-gnu"
TARGET_ARCH="aarch64"
TARGET_SYS="aarch64-oe-linux"

[zboszor]

What's your MACHINE setting? MACHINE=qemuarm64 on x86-64 build host should give the same, and this is what I tried with.

Also, please show the output of:

ls -l recipe-sysroot-native/usr/lib/clang/latest/lib

EDIT: Something in your build system must be switching back to an older commit.
The version you are building is 142.0.7444.175

[thorstenl312]

What's your MACHINE setting? MACHINE=qemuarm64 on x86-64 build host should give the same, and this is what I tried with.

MACHINE=am62pxx-evm

Also, please show the output of:

ls -l recipe-sysroot-native/usr/lib/clang/latest/lib

ls -l recipe-sysroot/usr/lib/clang/latest/lib/
total 8
drwxr-xr-x 2 a0506634 a0506634 4096 Mar 24 09:02 aarch64-unknown-linux-gnu
drwxr-xr-x 2 a0506634 a0506634 4096 Mar 24 09:02 linux

I fixed the version being wrong and now am running into a mismatch version for NodeJS

FAILED: [code=1] gen/third_party/node/check_version_result.txt 
python3 ../../third_party/node/check_version.py --expected_version_file ../../third_party/node/update_node_binaries --out_file gen/third_party/node/check_version_result.txt
Traceback (most recent call last):
  File "/build/build/arago-tmp-default/work/aarch64-oe-linux/chromium-ozone-wayland/144.0.7559.132/sources/chromium-144.0.7559.132/out/Release/../../third_party/node/check_version.py", line 31, in <module>
    main(sys.argv[1:])
    ~~~~^^^^^^^^^^^^^^
  File "/build/build/arago-tmp-default/work/aarch64-oe-linux/chromium-ozone-wayland/144.0.7559.132/sources/chromium-144.0.7559.132/out/Release/../../third_party/node/check_version.py", line 20, in main
    node.RunNode([
    ~~~~~~~~~~~~^^
        os.path.join(_HERE_PATH, 'check_version.js'),
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        '--expected_version_file', args.expected_version_file,
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ])
    ^^
  File "/build/build/arago-tmp-default/work/aarch64-oe-linux/chromium-ozone-wayland/144.0.7559.132/sources/chromium-144.0.7559.132/third_party/node/node.py", line 38, in RunNode
    raise RuntimeError('Command \'%s\' failed\n%s' % (' '.join(cmd), err))
RuntimeError: Command '/build/build/arago-tmp-default/work/aarch64-oe-linux/chromium-ozone-wayland/144.0.7559.132/sources/chromium-144.0.7559.132/third_party/node/linux/node-linux-x64/bin/node /build/build/arago-tmp-default/work/aarch64-oe-linux/chromium-ozone-wayland/144.0.7559.132/sources/chromium-144.0.7559.132/out/Release/../../third_party/node/check_version.js --expected_version_file ../../third_party/node/update_node_binaries' failed
node:internal/process/promises:394
    triggerUncaughtException(err, true /* fromPromise */);
    ^

AssertionError [ERR_ASSERTION]: Failed NodeJS version check: Expected major version '24', but found '22'. Expected full version was 'v24.11.1', actual version is 'v22.22.1'. Did you run 'gclient sync'? If the problem persists try running 'gclient sync -f' instead, or deleting third_party/node/{linux,win,mac} folders and trying again.

'24' !== '22'

    at main (file:///build/build/arago-tmp-default/work/aarch64-oe-linux/chromium-ozone-wayland/144.0.7559.132/sources/chromium-144.0.7559.132/third_party/node/check_version.js:42:10) {
  generatedMessage: false,
  code: 'ERR_ASSERTION',
  actual: '24',
  expected: '22',
  operator: 'strictEqual',
  diff: 'simple'
}

Node.js v22.22.1

[zboszor]

For the NodeJS version mismatch, I have a secret internal do_configure:prepend piece I carry since Chromium 136.
No one complained about this issue before publicly, so I considered it specific to my builds.

I will insert a commit into this PR before the version upgrade.

[thorstenl312]

Built successfully, thanks!

[MaxIhlenfeldt]

I think meta-browser needs a whinlatter branch now, where the bbappend added here can be carried forward. It can be branched off after #962 is merged.

Then the PRs for Chromium 145 and 146 (#963 and #964 , respectively) for master would not need this bbappend. The single commits from each PR may be cherry-picked into whinlatter.

sgtm, I've created the branch. Feel free to send cherry-pick PRs.

[MaxIhlenfeldt]

lgtm, thanks!