Package Details: fcitx5-mozc-with-jp-dict 3.33.6089.2-2

Git Clone URL: https://aur.archlinux.org/mozc-with-jp-dict.git (read-only, click to copy)
Package Base: mozc-with-jp-dict
Description: Fcitx5 Module for Mozc(the Open Source Edition of Google Japanese Input) with SudachiDict and MeCab UniDic Neologd and MeCab IpaDic Neologd
Upstream URL: https://github.com/fcitx/mozc
Keywords: dictionary emacs fcitx5 ibus japanese mozc
Licenses: Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND MIT AND NAIST-2003 AND Unicode-3.0 AND LicenseRef-Okinawa-Dictionary
Conflicts: fcitx, fcitx-mozc, fcitx-qt5, fcitx-qt6, fcitx5-mozc, ibus-mozc
Provides: fcitx5-mozc
Submitter: phoepsilonix
Maintainer: phoepsilonix
Last Packager: phoepsilonix
Votes: 10
Popularity: 0.29
First Submitted: 2023-03-14 08:19 (UTC)
Last Updated: 2026-02-22 15:45 (UTC)

Required by (3)

Sources (19)

Pinned Comments

phoepsilonix commented on 2024-08-26 00:02 (UTC) (edited on 2026-01-05 09:24 (UTC) by phoepsilonix)

If you're encountering errors during the build process, try deleting your Bazel cache (located at ~/.cache/bazel by default).

sudo rm -rf ~/.cache/bazel/*

or

makepkg -osC
cd src/mozc/src
bazel clean --expunge
cd ../../..

I use the following site for build verification and build automation.
If you encounter any issues, please also check here. It may be helpful.
If you are looking for pre-built package files, please check the following GitHub site.
https://github.com/phoepsilonix/mozc-arch/releases

without SudachiDict etc

git clone https://aur.archlinux.org/mozc-with-jp-dict.git
cd mozc-with-jp-dict
makepkg -p PKGBUILD.normal

Latest Comments

1 2 3 4 Next › Last »

phoepsilonix commented on 2026-01-24 05:28 (UTC) (edited on 2026-01-25 06:48 (UTC) by phoepsilonix)

I believe I was able to handle it.

The Bazel version on Arch Linux has been updated(9.0.0), resulting in an inability to build. Consequently, makedepends has been changed to bazelisk.
https://gitlab.archlinux.org/archlinux/packaging/packages/fcitx5-mozc/-/merge_requests/11

phoepsilonix commented on 2026-01-24 05:13 (UTC)

@gehenna14
As the official Mozc source code is not yet compatible with Bazel 9.0.0, we shall switch to building with Bazelisk.
Please wait for a while.

gehenna14 commented on 2026-01-24 03:09 (UTC)

The build fails at the Starting pkgver() step with no error messages other than build failed since the latest commit

gehenna14 commented on 2025-12-22 08:42 (UTC)

@phoepsilonix

I installed your package paru-static and it seems to have fixed the issue with paru!

I had previously patched that bug myself in the PKGBUILD in order to compile that version of paru but I guess that isn't enough for it to work properly.

Thank you!

phoepsilonix commented on 2025-12-22 03:41 (UTC) (edited on 2025-12-22 03:55 (UTC) by phoepsilonix)

@gehenna14
I believe paru was in the process of implementing support for libalpm16. Which version of paru are you using?

pacman -7.0.0 : paru 2.1.0
pacman 7.1.0-(libalpm16): paru 2.2.0

As there has been an update to pacman, paru and yay may also require corresponding updates.
The paru-static package has been made compatible with libalpm16 for the time being, so please feel free to try it out if you wish.

gehenna14 commented on 2025-12-22 03:37 (UTC)

@phoepsilonix

It seems to only be an issue as paru ATM, just manually installed it with makepkg and it compiles properly.

I don't know why I didn't try that earlier, I presume it's interpreting the PKGBUILD wrong.

phoepsilonix commented on 2025-12-22 03:23 (UTC) (edited on 2025-12-22 03:26 (UTC) by phoepsilonix)

@gehenna14

Could you please clear your cache and try again?
Also, could you tell me what command you're running? and What is your shell(bash,zsh,csh etc)?

gehenna14 commented on 2025-12-22 02:36 (UTC) (edited on 2025-12-22 02:37 (UTC) by gehenna14)

@phoepsilonix I figured out that I had it set to java 25 instead of java 21... I set it to java 21, and javac and java are in PATH now and java_home gets set now. However it just gives a different error now

error: can't find package name in packagelist: Setting JAVA_HOME:  /usr/lib/jvm/java-21-openjdk

phoepsilonix commented on 2025-12-21 23:44 (UTC) (edited on 2025-12-22 01:35 (UTC) by phoepsilonix)

@gehenna14

If java and javac are in your PATH, you may not need JAVA_HOME.
Please check the following command.

which javac
javac --version
java --version

 ls -l /usr/lib/jvm/default-runtime/

If the PATH was not set,

archlinux-java fix

Switching the JVM(JDK)

archlinux-java set java-21-openjdk

archlinux-java set java-25-openjdk

If Java is in your PATH, you should be able to set it up with the following command.
It appears to function without issue even without setting JAVA_HOME.

export JAVA_HOME="$(dirname $(dirname $(realpath $(which javac))))"

gehenna14 commented on 2025-12-21 12:45 (UTC) (edited on 2025-12-21 12:46 (UTC) by gehenna14)

Got this today, could it be because I have jre-openjdk installed alongside jdk21-openjdk?

Should I remove the former? or can I just set JAVA_HOME?

I find this strange because i was obviously able to build it in the past

Sorry for the really stupid question.

==> Making package: mozc-with-jp-dict 2.32.5994.102-3 (Mon 22 Dec 2025 01:42:09)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Starting pkgver()...
==> Starting build()...
Extracting Bazel installation...
FATAL: Could not find system javabase. Ensure JAVA_HOME is set, or javac is on your PATH.
==> ERROR: A failure occurred in build().
    Aborting...
error: failed to build 'mozc-with-jp-dict-2.32.5994.102-3 (fcitx5-mozc-with-jp-dict)':

1 2 3 4 Next › Last »