Arch Linux User Repository

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

No, as far as I know Mozc will build just fine with Clang. This is an oversight of mine: back when I added the flag I didn't know that it isn't supported by LLVM, and when after a while I was informed about it I just figured that it probably wouldn't be long before I removed it anyway (I never expected that this bug would stay open for ~6 months), and the default system compiler is GCC, so there shouldn't be any real issues. Case in point, you're the first user in almost 6 months that has stumbled upon this (or at least, the first user who has reported it).

So as I said, please bear with this minor inconvenience until the next update, and in the meantime just change the flag and do the build normally.

@Nocifer should i be building with gcc then?

@tokisuno That's because you're trying to build with Clang, which does not support the -Wno-maybe-uninitialized compiler flag. For the time being you can just do what the error prompt says and change the flag to -Wno-uninitialized.

Upstream Mozc has already merged a proper fix for the issue that this flag was used as a stopgap for, so with the next update the flag will be removed from the PKGBUILD altogether.

Starting local Bazel server and connecting to it...
DEBUG: /home/poto/.cache/bazel/_bazel_poto/d996a5e9575394de42d450ce4b82c0cc/external/rules_android_ndk~/rules.bzl:28:14: Either the ANDROID_NDK_HOME environment variable or the path attribute of android_ndk_repository must be set.
INFO: Analyzed 2 targets (180 packages loaded, 10720 targets configured).
ERROR: /home/poto/.cache/bazel/_bazel_poto/d996a5e9575394de42d450ce4b82c0cc/external/protobuf~/src/google/protobuf/stubs/BUILD.bazel:12:11: Compiling src/google/protobuf/stubs/common.cc [for tool] failed: (Exit 1): clang-18 failed: error executing CppCompile command (from target @@protobuf~//src/google/protobuf/stubs:lite) /usr/bin/clang-18 -U_FORTIFY_SOURCE -fstack-protector -Wall -Wthread-safety -Wself-assign -Wunused-but-set-parameter -Wno-free-nonheap-object -fcolor-diagnostics -fno-omit-frame-pointer -g0 -O2 ... (remaining 40 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
error: unknown warning option '-Wno-maybe-uninitialized'; did you mean '-Wno-uninitialized'? [-Werror,-Wunknown-warning-option]
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 16.981s, Critical Path: 7.37s
INFO: 17 processes: 10 internal, 7 linux-sandbox.
ERROR: Build did NOT complete successfully
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: mozc-ut-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
mozc-ut - exit status 4 

this is when i built after clearing cache.

Found the issue. Running aura as sudo is not necessary anymore and otherwise breaks the build: https://github.com/fosskers/aura/issues/907

I'm getting a compilation error:

==> Starting build()...
FATAL: mkdir('/.cache/bazel/_bazel_nobody'): (error: 13): Permission denied
==> ERROR: A failure occurred in build().
    Aborting...
aura :: Package failed to build, citing:

  makepkg failed.

Seems bazel is run as the nobody user and the nobody user does not have any home so it defaults to /. Any ideas? (I tried deleting the cache from other users just in case but that didn't solve the problem)

@NettoHikari I just rechecked and it seems they did fix the build issue somehow, you can use their repo if you want prebuilts.

@NettoHikari I had this and fcitx5-mozc-ut added to andontie-aur once, but it seems that it no longer gets built due to similar building issues; so I just build it locally nowadays (though I've never had issues building it myself).

Seems that there may be some problems with automating building this package (possibly the Bazel cache issue) so making a -bin of this would be a bit more difficult sadly.

@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?