Arch Linux User Repository

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

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

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

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

@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)?

@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

@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))))"

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)':

@Muflone

Quite right. I think that's fine too.
So, once Google had reached a milestone, incremented the version number, and incorporated it into fcitx5-Mozc, I created a merge request.
This version also works without issues on my local environment.
I hope it gets reflected eventually.

Naturally, it is possible to update the merge request based on the latest Fcitx5-Mozc commit. Do you think that is necessary?

Arch Linux ships stable packages, except very few exceptions.

so pulling the latest commit in not needed

@Muflone

Thank you for your confirmation.

Regarding the Fcitx5-Mozc package,
the current version of the Fcitx5-Mozc package on Arch Linux is 2.31.5810.102.gb091429.
The latest Mozc version is Mozc-2.32.5981.102+24.11.oss.

https://github.com/fcitx/mozc/commit/29e2b953deacc1b6aa35c28ffedb692399ee4c05
I created the merge request when the Fcitx5-Mozc version number increased. Naturally, it is possible to update the merge request based on the latest Fcitx5-Mozc commit. Do you think that is necessary?
As I cannot receive comments from anyone on GitLab, I am at a loss as to what to do.
I'll take my time and wait for about a month.