Package Details: mozc-ut 2.30.5490.102.20240609-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.67
First Submitted: 2020-11-04 02:00 (UTC)
Last Updated: 2024-06-09 09:10 (UTC)

Dependencies (10)

Required by (5)

Sources (11)

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

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

Nocifer commented on 2024-03-09 13:09 (UTC)

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

Mixaz commented on 2024-03-09 04:17 (UTC)

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.

npreining commented on 2024-01-24 11:43 (UTC)

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

Nocifer commented on 2024-01-24 11:39 (UTC)

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

npreining commented on 2024-01-23 23:14 (UTC)

@Nocifer thanks, indeed, I have some Android env vars I have forgotten about. After doing

unset ANDROID_HOME ANDROID_NDK ANDROID_NDK_HOME ANDROID_NDK_ROOT ANDROID_SDK_ROOT

the build did work.

Thanks and sorry for the noise

Nocifer commented on 2024-01-23 14:31 (UTC) (edited on 2024-01-23 14:31 (UTC) by Nocifer)

@npreining I guess you have something Android-related installed? If so, then this must be some new Bazel 7.0 quirk. Does adding unset ANDROID_HOME in the PKGBUILD (e.g. under the similar unset ANDROID_NDK_HOME in line 96) fix it for you?