Arch Linux User Repository

If you're getting compilation errors, please delete your Bazel cache (~/.cache/bazel by default).

@mod20 I get the same build error even when building against the latest master. I've reported it upstream, so hopefully it'll get fixed soon.

I am getting the following error when compiling with latest GCC (13.1.1):

ERROR: /home/modanese/.cache/aurutils/sync/ibus-mozc/src/ibus-mozc-git/src/unix/ibus/BUILD.bazel:85:16: Compiling unix/ibus/ibus_wrapper.cc failed: (Exit 1): gcc failed: error executing command (from target //unix/ibus:ibus_wrapper) /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections ... (remaining 60 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
unix/ibus/ibus_wrapper.cc: In member function 'void mozc::ibus::IbusBusWrapper::RequestName(absl::lts_20230125::string_view)':
unix/ibus/ibus_wrapper.cc:417:13: error: 'uint32_t' does not name a type
  417 |   constexpr uint32_t flags = 0;
      |             ^~~~~~~~
unix/ibus/ibus_wrapper.cc:31:1: note: 'uint32_t' is defined in header '<cstdint>'; did you forget to '#include <cstdint>'?
   30 | #include "unix/ibus/ibus_wrapper.h"
  +++ |+#include <cstdint>
   31 | 
unix/ibus/ibus_wrapper.cc:418:44: error: 'flags' was not declared in this scope
  418 |   ibus_bus_request_name(bus_, name.data(), flags);
      |                                            ^~~~~

Tried deleting the bazel cache, but that didn't help.

Sorry about that, my cache folder still contained a mozc_renderer binary in renderer from the previous build and during testing the package managed to build successfully by reusing that, so I completely failed to notice the issue. Should be fixed now, thanks for reporting.

Current version fails because the latest update to PKGBUILD updates the destination folder of mozc_renderer to renderer/qt from renderer but the install -Dm755 bazel-bin/renderer/mozc_renderer command does not reflect it. Something like this can solve the issue until the update:

ln -s  ~/.cache/yay/ibus-mozc/src/ibus-mozc-git/src/bazel-bin/renderer/qt/mozc_renderer ~/.cache/yay/ibus-mozc/src/ibus-mozc-git/src/bazel-bin/renderer/mozc_renderer

@jukan This package does not install any configuration file, it only installs the Mozc binaries and a few extra files like licenses and icons, which you can verify by checking out the PKGBUILD.

If the default config file that (I suppose) is automatically created when launching Mozc via IBus contains errors, then you should probably report it upstream so the developers can provide a fix.

The default config for this package currently seems broken for me. The upstream docs omit quotes from the composition_mode field of the config.

https://github.com/google/mozc/blob/db37db71b53c9accc9ad66d12ad8196b25c771b3/docs/configurations.md

Removing the quotes made the input work for (after restarting IBus).

If you're getting compilation errors, please delete your Bazel cache (~/.cache/bazel by default).

Due to a mistake I made in the previous release, newer versions of this package may fail to gracefully update over a preexisting 2.26.4596.102 setup (installing fresh won't be an issue) with the following error (or something similar):

error: failed to prepare transaction (could not satisfy dependencies)
:: installing mozc (2.26.4610.102-1) breaks dependency 'mozc=2.26.4596.102' required by ibus-mozc

The TL;DR version of it is that you will need to do one of the following:

1) Uninstall this package and then reinstall it; or

2) Edit the file /var/lib/pacman/local/ibus-mozc-2.26.4596.102-1/desc and replace

%DEPENDS%
ibus>=1.4.1
mozc=2.26.4596.20211205

with

%DEPENDS%
ibus>=1.4.1
mozc>=2.26.4596.20211205

and then proceed to update as per usual.

(In other words, the mozc version dependency should be a lax >= instead of a strict =; which AFAIR is also standard PKGBUILD practice, but somehow I completely forgot about it.)

Hopefully this is now fixed, but I'll wait for your input (if any) before I can be certain. Sorry for the inconvenience.

Thanks a lot, that worked

Yeah, that's because this new version is a huge update, both in terms of how Mozc is built and how it is packaged, and it conflicts with its previous incarnation. I should have expected this really.

The best and easiest solution is to first uninstall the previous version and then install this new one.

I'll pin this for the time being.