Package Details: mozc-ut 2.30.5618.102.20241010-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: 24
Popularity: 0.80
First Submitted: 2020-11-04 02:00 (UTC)
Last Updated: 2024-10-10 12:38 (UTC)

Dependencies (8)

Required by (5)

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 Next › Last »

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.

Nocifer commented on 2024-07-06 08:42 (UTC)

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

NettoHikari commented on 2024-07-05 21:08 (UTC)

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?

Nocifer commented on 2024-05-17 08:56 (UTC)

@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

csslayer commented on 2024-05-17 01:04 (UTC) (edited on 2024-05-17 01:31 (UTC) by csslayer)

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

Nocifer commented on 2024-03-18 19:18 (UTC) (edited on 2024-03-18 19:18 (UTC) by Nocifer)

@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

zwastik commented on 2024-03-18 17:30 (UTC) 

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

1 2 3 4 5 6 Next › Last »