Package Details: mozc-ut 2.31.5712.102.20250117-1

Git Clone URL: https://aur.archlinux.org/mozc-ut.git (read-only, click to copy)
Package Base: mozc-ut
Description: The Open Source edition of Google Japanese Input bundled with the UT dictionary
Upstream URL: https://github.com/google/mozc
Licenses: Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND CC0-1.0 AND CC-BY-SA-3.0 AND CC-BY-SA-4.0 AND GPL-2.0-only AND GPL-2.0-or-later AND MIT AND NAIST-2003 AND Unicode-3.0 AND LicenseRef-Okinawa-Dictionary
Conflicts: mozc
Provides: mozc
Submitter: naoina
Maintainer: Nocifer
Last Packager: Nocifer
Votes: 26
Popularity: 0.87
First Submitted: 2020-11-04 02:00 (UTC)
Last Updated: 2025-01-17 11:43 (UTC)

Dependencies (8)

Required by (4)

Sources (18)

Pinned Comments

Nocifer commented on 2022-05-29 21:54 (UTC) (edited on 2023-08-22 09:33 (UTC) by Nocifer)

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

Latest Comments

1 2 3 4 5 6 7 Next › Last »

Nocifer commented on 2025-01-24 22:26 (UTC)

@raum_dellamorte Everything builds fine on my end as of a few minutes ago, and anyway Mozc doesn't/shouldn't use either Appimage or fuse for its build process.

Something is wrongly configured on your end, but I can't figure out what by reading this error log. I'm guessing that something you have installed is interfering with the build process and forcing it to call fusermount, which then fails for some unknown reason.

Are you trying to build via an AUR helper or manually? Or perhaps inside a container or VM or some such? Or perhaps you use some kind of tmpfs partition?

As an aside, if you had to create the polkitd user manually then something is very wrong with how you've installed/configured things, as that user and the accompanying polkitd group should have been created for you automatically by systemd. Perhaps this is a hint for some underlying issue that's also preventing you to build Mozc.

Lastly: try to build the package in a clean chroot. If nothing else, this will allow you to at least install and use it even if for the time being you can't find the error.

raum_dellamorte commented on 2025-01-24 11:00 (UTC)

I keep getting "fusermount: mount failed: Operation not permitted"

I installed fuse2 and can run AppImages, I did sudo rm -Rf ~/.cache/bazel. A comment suggested gcc13 was needed so I also tried installing that and making the related changes to PKGBUILD to use gcc13. Always the fusermount error. I couldn't get Flatpak to work until I manually added 'polkitd' as a system user, could it be something like that?

==> Starting build()...
Extracting Bazel installation...
Starting local Bazel server (8.0.1) and connecting to it...
DEBUG: /home/raum/.cache/bazel/_bazel_raum/9e7bc8e49e64b583f6fe2bd8adb482da/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 (193 packages loaded, 11787 targets configured).
ERROR: /home/raum/dl/mozc-ut/src/mozc/src/data_manager/oss/BUILD.bazel:54:13: Executing genrule //data_manager/oss:mozc_dataset_for_oss@version failed: (Exit 127): bash failed: error executing Genrule command (from target //data_manager/oss:mozc_dataset_for_oss@version) /bin/bash -c ... (remaining 1 argument skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
fusermount: mount failed: Operation not permitted
open dir error: No such file or directory

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
ERROR: /home/raum/dl/mozc-ut/src/mozc/src/data_manager/oss/BUILD.bazel:54:13: Executing genrule //data_manager/oss:mozc_dataset_for_oss@pos_matcher failed: (Exit 127): bash failed: error executing Genrule command (from target //data_manager/oss:mozc_dataset_for_oss@pos_matcher) /bin/bash -c ... (remaining 1 argument skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
fusermount: mount failed: Operation not permitted
open dir error: No such file or directory

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
ERROR: /home/raum/dl/mozc-ut/src/mozc/src/data_manager/oss/BUILD.bazel:54:13: Executing genrule //data_manager/oss:mozc_dataset_for_oss@user_pos failed: (Exit 127): bash failed: error executing Genrule command (from target //data_manager/oss:mozc_dataset_for_oss@user_pos) /bin/bash -c ... (remaining 1 argument skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
fusermount: mount failed: Operation not permitted
open dir error: No such file or directory

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 15.874s, Critical Path: 2.08s
INFO: 588 processes: 495 internal, 93 linux-sandbox.
ERROR: Build did NOT complete successfully
==> ERROR: A failure occurred in build().
    Aborting...

Nocifer commented on 2025-01-04 15:59 (UTC)

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.

tokisuno commented on 2025-01-04 12:21 (UTC)

@Nocifer should i be building with gcc then?

Nocifer commented on 2025-01-04 10:59 (UTC)

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

tokisuno commented on 2025-01-03 18:44 (UTC) (edited on 2025-01-03 18:46 (UTC) by tokisuno) 

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.

PepperJo commented on 2024-09-05 00:58 (UTC)

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

PepperJo commented on 2024-09-02 14:38 (UTC)

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)

silikeite commented on 2024-08-26 12:56 (UTC)

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

silikeite commented on 2024-08-26 12:55 (UTC)

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

1 2 3 4 5 6 7 Next › Last »