Package Details: fcitx5-mozc-ut 2.30.5618.102-1

Git Clone URL: https://aur.archlinux.org/fcitx5-mozc-ut.git (read-only, click to copy)
Package Base: fcitx5-mozc-ut
Description: Mozc module for Fcitx5
Upstream URL: https://github.com/fcitx/mozc
Licenses: Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND GPL-2.0-or-later AND MIT AND NAIST-2003 AND Unicode-3.0 AND LicenseRef-Okinawa-Dictionary
Conflicts: fcitx5-mozc
Provides: fcitx5-mozc
Submitter: Nocifer
Maintainer: Nocifer
Last Packager: Nocifer
Votes: 34
Popularity: 2.29
First Submitted: 2020-12-08 09:21 (UTC)
Last Updated: 2024-10-10 12:39 (UTC)

Pinned Comments

Nocifer commented on 2022-05-29 21:55 (UTC) (edited on 2023-08-22 09:32 (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-07-05 06:37 (UTC)

@mber ccache and distcc are both explicitly disabled due to them having been identified a couple of years ago as the source of multiple compilation headaches. I don't know if that would still be the case nowadays, but you can always remove the line options=(!distcc !ccache) in the PKGBUILD and try it yourself.

Still, this probably wouldn't help you much in this case, as the slow rebuild times are mostly due to the last few releases including major updates by upstream to backend stuff like abseil-cpp and protobuf, which make up the bulk of the build and can really slow it down. You can verify if this is indeed the issue by rebuilding the package manually; just go to its cache folder (e.g. ~/.cache/yay/fcitx5-moz-ut) and run makepkg, it should complete in just a few seconds.

mber commented on 2024-07-04 11:46 (UTC)

Is there any way to get this to use ccache or something? The build times on a low spec machine are enormous every update.

Nocifer commented on 2024-06-25 13:53 (UTC)

The only thing that's been changed in the latest update is the Java version (from 11 to 21), and that should not be affecting prepare().

On my end the package builds successfully, both in a clean chroot during testing and in my default environment during the update process. Perhaps deleting the old src folder (if you keep it around between updates) could help.

cle5 commented on 2024-06-25 12:21 (UTC) (edited on 2024-06-26 22:55 (UTC) by cle5)

Does not build upgrading from previous version 

==> ERROR: A failure occurred in prepare().
    Aborting...
 -> error making: fcitx5-mozc-ut-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
fcitx5-mozc-ut - exit status 4

Works after deleting bazel cache! sorry lol (^_^;)

arkeet commented on 2024-06-24 21:56 (UTC) (edited on 2024-06-24 21:56 (UTC) by arkeet)

I get this build error:

Error: LinkageError occurred while loading main class com.google.devtools.build.lib.bazel.Bazel
        java.lang.UnsupportedClassVersionError: com/google/devtools/build/lib/bazel/Bazel has been compiled by a more recent version of the Java Runtime (class file version 65.0), this version of the Java Runtime only recognizes class file versions up to 55.0

I have bazel 7.2.0-1, which now uses Java 21 instead of 11. So I suppose it fails because this package sets JAVA_HOME='/usr/lib/jvm/java-11-openjdk/' when building. It works after downgrading to bazel 7.1.1-2.

Nocifer commented on 2024-06-17 18:30 (UTC)

@rinbega Oops. Thanks, and fixed.

rinbega commented on 2024-06-17 15:06 (UTC)

I'm missing tray icons unless I change dashes into underscores in the names of the icons in the PKGBUILD. The cause is e13338a, I guess.

river_wunsch commented on 2024-05-13 13:12 (UTC)

Thanks @asura for the solution.

Step-by-step guide for noobs like me:

  1. Install gcc13
  2. Edit PKGBUILD file before building the package:
    1. Add two lines to the build() function before bazel build ...: export CC='/usr/bin/gcc-13' export CXX='/usr/bin/g++-13'
    2. If you don't have mozc installed, also add the same two lines to the PKGBUILD file for mozc package.

asura commented on 2024-05-11 21:18 (UTC)

Could not build with gcc version 14.

Solved by installing 'gcc13' and adding 'CC=/usr/bin/gcc-13' and 'CXX=/usr/bin/g++-13' before the bazel build command in the PKGBUILD.

soemintun commented on 2024-04-21 04:35 (UTC)

Thanks for the advises. It took me awhile to get correct solution for my problem. My CPU might have an issue. I have Intel i9-14900KF (32) @ 5.700GHz. While compiling, Bazel was using all 32-cores to compile, but somehow build process was terminated before finish. I don't know why. But I added bazel build --jobs 12 to PKGBUILD file and deleted bazel cache. Then rebuild was successful.

1 2 3 4 5 Next › Last »