Build error: bazel 9 support

[wengxt]

Description

fix.patch

Here's the patch fix the build for me.

Commit ID

76cb1ce

Build target

Linux

CI build status

passing

OS version

Archlinux

Build environment

• Python version (optional): 3.14.2
• Qt6 version (optional): 6.10.1

Build commands

bazel build -c opt --copt=-fPIC --config oss_linux server:mozc_server gui/tool:mozc_tool

Error logs

bazel build -c opt --copt=-fPIC --config oss_linux gui/tool:mozc_tool
Extracting Bazel installation...
Starting local Bazel server (9.0.0) and connecting to it...
WARNING: For repository 'com_google_absl', the root module requires module version [email protected], but got [email protected] in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'com_google_protobuf', the root module requires module version [email protected], but got [email protected] in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'bazel_skylib', the root module requires module version [email protected], but got [email protected] in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'rules_python', the root module requires module version [email protected], but got [email protected] in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: For repository 'build_bazel_apple_support', the root module requires module version [email protected], but got [email protected] in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
ERROR: Traceback (most recent call last):
File "/home/csslayer/.cache/bazel/_bazel_csslayer/e3a2184164be125565ea43de6b532d5e/external/rules_python+/python/private/py_library_rule.bzl", line 18, column 52, in
py_library = create_py_library_rule_builder().build()
File "/home/csslayer/.cache/bazel/_bazel_csslayer/e3a2184164be125565ea43de6b532d5e/external/rules_python+/python/private/rule_builders.bzl", line 517, column 44, in lambda
build = lambda *a, **k: _Rule_build(self, *a, **k),
File "/home/csslayer/.cache/bazel/_bazel_csslayer/e3a2184164be125565ea43de6b532d5e/external/rules_python+/python/private/rule_builders.bzl", line 546, column 28, in _Rule_build
kwargs = self.to_kwargs()
File "/home/csslayer/.cache/bazel/_bazel_csslayer/e3a2184164be125565ea43de6b532d5e/external/rules_python+/python/private/rule_builders.bzl", line 531, column 44, in lambda
to_kwargs = lambda: _Rule_to_kwargs(self),
File "/home/csslayer/.cache/bazel/_bazel_csslayer/e3a2184164be125565ea43de6b532d5e/external/rules_python+/python/private/rule_builders.bzl", line 589, column 42, in _Rule_to_kwargs
kwargs[_ATTRS] = self.attrs.build()
File "/home/csslayer/.cache/bazel/_bazel_csslayer/e3a2184164be125565ea43de6b532d5e/external/rules_python+/python/private/rule_builders.bzl", line 639, column 41, in lambda
build = lambda: _AttrsDict_build(self),
File "/home/csslayer/.cache/bazel/_bazel_csslayer/e3a2184164be125565ea43de6b532d5e/external/rules_python+/python/private/rule_builders.bzl", line 693, column 27, in _AttrsDict_build
attrs[k] = v.build() if _is_builder(v) else v
File "/home/csslayer/.cache/bazel/_bazel_csslayer/e3a2184164be125565ea43de6b532d5e/external/rules_python+/python/private/attr_builders.bzl", line 866, column 44, in lambda
build = lambda: _common_label_build(self, attr.label_list),
File "/home/csslayer/.cache/bazel/_bazel_csslayer/e3a2184164be125565ea43de6b532d5e/external/rules_python+/python/private/attr_builders.bzl", line 89, column 24, in _common_label_build
return attr_factory(**kwargs)
Error in label_list: at index 0 of providers, got element of type NoneType, want Provider
WARNING: Target pattern parsing failed.
ERROR: Skipping 'gui/tool:mozc_tool': error loading package 'gui/tool': at /home/csslayer/Develop/mozc/src/bazel/qt.bzl:44:6: at /home/csslayer/Develop/mozc/src/bazel/stubs.bzl:33:6: at /home/csslayer/.cache/bazel/_bazel_csslayer/e3a2184164be125565ea43de6b532d5e/external/rules_python+/python/defs.bzl:18:6: at /home/csslayer/.cache/bazel/_bazel_csslayer/e3a2184164be125565ea43de6b532d5e/external/rules_python+/python/py_library.bzl:17:6: at /home/csslayer/.cache/bazel/_bazel_csslayer/e3a2184164be125565ea43de6b532d5e/external/rules_python+/python/private/py_library_macro.bzl:16:6: initialization of module 'python/private/py_library_rule.bzl' failed
ERROR: error loading package 'gui/tool': at /home/csslayer/Develop/mozc/src/bazel/qt.bzl:44:6: at /home/csslayer/Develop/mozc/src/bazel/stubs.bzl:33:6: at /home/csslayer/.cache/bazel/_bazel_csslayer/e3a2184164be125565ea43de6b532d5e/external/rules_python+/python/defs.bzl:18:6: at /home/csslayer/.cache/bazel/_bazel_csslayer/e3a2184164be125565ea43de6b532d5e/external/rules_python+/python/py_library.bzl:17:6: at /home/csslayer/.cache/bazel/_bazel_csslayer/e3a2184164be125565ea43de6b532d5e/external/rules_python+/python/private/py_library_macro.bzl:16:6: initialization of module 'python/private/py_library_rule.bzl' failed
INFO: Elapsed time: 7.218s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
FAILED:
Fetching repository @@rules_swift+; starting
Fetching repository @@apple_support+; starting
Fetching repository @@protobuf+; starting

Additional context

No response

[yukawa]

Thank you for the report and patch.

We anticipate that the official switch to Bazel 9 in Mozc upstream will happen around March or April. Right now, we are verifying that the Windows and macOS binaries built with Bazel are production-ready, which is the final step before we can deprecate GYP.

Since our primary focus is replacing GYP, we want to avoid introducing build tool upgrades that might destabilize the environment during this critical verification phase. Once the GYP deprecation is finalized, we will be in a better position to update dependencies like Bazel.

[yukawa]

Just fyi, the implications of prebuilt proto compiler (protoc) are also something we would like to evaluate before migrating to Bazel 9 and Protobuf v34.x

• https://protobuf.dev/news/2026-01-16/

[yukawa]

Filed this so that people can keep track of the progress on Bazel 9 migration.

• Migrate to Bazel 9 #1437

As I explained above, Pull Requests are unlikely to be merged until GYP is fully deprecated, unless we decide to postpone GYP deprecation into the next release cycle.

[yukawa]

Perhaps we may need to wait for the next version of rules_android_ndk, which is supposed to include bazelbuild/rules_android_ndk@2966647, or locally cherry-pick it until the next version is released.