Arch Linux User Repository

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

@NettoHikari Your best bet would be asking here for help with your issues, like everyone else. I know I'd personally be really interested to hear about the numerous reasons that this package is failing to download and build all the time for you, so that I can try and fix them, or maybe even report them upstream.

Other than that, I could suggest trying one of the other two Mozc package families in the AUR, but they also use Bazel so I don't know how much help they would be to you. And the only precompiled package I'm aware of in the repos is fcitx5-mozc which has been outdated for close to two years now (last real update was in late 2022), so that's a no-go as well.

I'm honestly sick and tired of this package failing to install for numerous reasons all the time. Sometimes because some of the stuff can't be downloaded, sometimes, because of Bazel failing to compile stuff, etc.

Is there any repo with a precompiled version?

@csslayer Or even better, we can turn off Protobuf's unconditional use of the -Werror flag, which is what turns those nice -Wmaybe-uninitialized warnings into pesky -Werror=maybe-uninitialized errors and subsequently breaks the build :)

Source: https://github.com/protocolbuffers/protobuf/issues/14714

Issue with gcc 14 can be workaround by --cxxopt=-Wno-maybe-uninitialized , in case you want to use default gcc instead.

Correction: you need --cxxopt=-Wno-maybe-uninitialized --host_cxxopt=-Wno-maybe-uninitialized

@zwastik It's a pacman bug and a fix is already included in bazel 7.1.0-2.

Source: https://gitlab.archlinux.org/archlinux/packaging/packages/bazel/-/issues/1

Compiling the UT dictionary...

==> Sources are ready.
==> Making package: mozc-ut 2.29.5400.102.20240308-2 (Mon 18 Mar 2024 02:26:12 PM -03)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
file is invalid or corrupted (missing end of central directory record)
Opening zip "/usr/bin/bazel-real": Cannot find central directory
FATAL: Failed to open '/usr/bin/bazel-real' as a zip file: (error: 5): Input/output error
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: mozc-ut-exit status 4
==> Making package: fcitx5-mozc-ut 2.29.5400.102-4 (Mon 18 Mar 2024 02:26:13 PM -03)
==> Checking runtime dependencies...
==> Missing dependencies:
  -> mozc>=2.29.5400.102
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.
 -> error making: fcitx5-mozc-ut-exit status 8
 -> Failed to install the following packages. Manual intervention is required:
mozc-ut - exit status 4
fcitx5-mozc-ut - exit status 8

$ file /usr/bin/bazel-real
/usr/bin/bazel-real: ELF 64-bit LSB pie executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 4.4.0, BuildID[sha1]=57b7d70dd3d5b6cfaaa3ba0c950012d247d0843c, not stripped

Sorry for the fsck up, I don't even know how I managed to do that. Package permissions have (hopefully) been fixed.

The server is failing to start for me after the update. Permissions for files in /usr/lib/mozc/ have been changed to 644, reverting them to 755 fixed the issue.

@Nocifer thanks for adding the additional override, hopefully it helps others. And thanks for maintaining these packages, much appreciated!

@npreining Nah, it's not you, Bazel is already known to break when ANDROID_NDK_HOME is set and some other conditions are also met, hence the unset ANDROID_NDK_HOME fix. But I guess with Bazel 7.0 we'll have to take care of ANDROID_HOME as well.

As far as I can tell by skimming through Bazel's source code it's only these two variables that are taken into consideration, so I've updated the PKGBUILD accordingly.