Package Details: fcitx5-mozc-with-jp-dict 2.31.5851.102-13

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: 7
Popularity: 0.37
First Submitted: 2023-03-14 08:19 (UTC)
Last Updated: 2025-08-16 20:09 (UTC)

Required by (2)

Sources (19)

Pinned Comments

phoepsilonix commented on 2024-08-26 00:02 (UTC) (edited on 2025-07-05 04:36 (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 ../../..

sudo pacman -Rs fcitx-qt6 fcitx
makepkg -p PKGBUILD

The development of Fcitx has transitioned to Fcitx5, and Fcitx-Mozc is no longer maintained. Please try the following command.

sudo pacman -Rs fcitx5-qt fcitx5
makepkg -p PKGBUILD.fcitx

If you are looking for pre-built package files, please check the following GitHub site.
https://github.com/phoepsilonix/mozc-arch/releases

Latest Comments

1 2 Next › Last »

fabiscafe commented on 2025-08-17 20:00 (UTC)

Sadly, I'm also unable to build it. 

==> 1. Build the rust program(dict-to-mozc), it may take some time...
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: latest update on 2025-08-07, rust version 1.89.0 (29483883e 2025-08-04)
info: component 'cargo' for target 'x86_64-unknown-linux-gnu' is up to date
info: component 'clippy' for target 'x86_64-unknown-linux-gnu' is up to date
info: component 'rustc' for target 'x86_64-unknown-linux-gnu' is up to date
info: component 'rustfmt' for target 'x86_64-unknown-linux-gnu' is up to date
info: downloading component 'llvm-tools'
info: latest update on 2025-08-07, rust version 1.89.0 (29483883e 2025-08-04)
info: component 'cargo' for target 'x86_64-unknown-linux-gnu' is up to date
info: component 'clippy' for target 'x86_64-unknown-linux-gnu' is up to date
info: component 'rustc' for target 'x86_64-unknown-linux-gnu' is up to date
info: component 'rustfmt' for target 'x86_64-unknown-linux-gnu' is up to date
info: downloading component 'llvm-tools'
info: downloading component 'rust-src'
info: installing component 'llvm-tools'
error: component download failed for llvm-tools-x86_64-unknown-linux-gnu: could not rename downloaded file from '/build/.rustup/downloads/bb0ced899fd1ac628f26e375adabc970b415c516ec82fb7cf9ac3c63cb4d0fee.partial' to '/build/.rustup/downloads/bb0ced899fd1ac628f26e375adabc970b415c516ec82fb7cf9ac3c63cb4d0fee': No such file or directory (os error 2)
Usage: grep [OPTION]... PATTERNS [FILE]...
Try 'grep --help' for more information.
info: installing component 'rust-src'
error: "--target" takes a target architecture as an argument.

Run `rustup target list` to see possible targets.
error: "--target" takes a target architecture as an argument.

Run `rustup target list` to see possible targets.

@phoepsilonix could you try to verify that it builds in a clean chroot?

git clone https://aur.archlinux.org/mozc-with-jp-dict.git
pkgctl build --repo extra mozc-with-jp-dict

should do that.

phoepsilonix commented on 2025-07-04 08:56 (UTC) (edited on 2025-07-04 09:23 (UTC) by phoepsilonix)

@jaro3

Tweaked. I think dict-to-mozc is now buildable for both gcc and clang. I think it can build on both ArchLinux and ManjaroLinux.

The “error: component download failed” is an error when communication with the rust server fails. In this case, try building again.

Also try deleting bazel's cache, as it may not be able to build due to bazel version upgrades.

If you still cannot build, please let us know the results of the following commands and the build environment. 

rustup target list --installed
rustup target list --installed | grep $(rustc -vV | sed -e 's|host: ||' -e 's|-gnu||p' -n) | grep -v musl && TARGET=$(rustup target list --installed | grep $(rustc -vV | sed -e 's|host: ||' -e 's|-gnu||p' -n)|grep -v musl|head -n1) || TARGET=$(rustup target list --installed | grep $(rustc -vV | sed -e 's|host: ||' -e 's|-gnu||p' -n)|grep musl|head -n1)
echo $TARGET

jaro3 commented on 2025-07-03 03:46 (UTC)

Build fails in clean chroot too:


info: downloading component 'llvm-tools'
info: downloading component 'rust-src'
error: component download failed for llvm-tools-x86_64-unknown-linux-gnu: could not rename downloaded file from '/build/.rustup/downloads/16e8d9b4187cc3936feddd9ceccde0157a4a1b2be98ca9c202cda304e0e81853.partial' to '/build/.rustup/downloads/16e8d9b4187cc3936feddd9ceccde0157a4a1b2be98ca9c202cda304e0e81853': No such file or directory (os error 2)
info: installing component 'llvm-tools'
info: installing component 'rust-src'
error: "--target" takes a target architecture as an argument.

Run `rustup target list` to see possible targets.
error: "--target" takes a target architecture as an argument.

Run `rustup target list` to see possible targets.
==> ERROR: A failure occurred in prepare().
    Aborting...

jaro3 commented on 2025-07-03 03:44 (UTC)

Build fails:


warning: mimalloc-rust-sys@1.7.9-source:       |                                       ^~~~~~~~~~~~~~~~~~
error: failed to run custom build command for `mimalloc-rust-sys v1.7.9-source`

Caused by:
  process didn't exit successfully: `/usr/src/tmp/mozc-with-jp-dict/src/dict-to-mozc/target/release/build/mimalloc-rust-sys-d715c5ad95029a71/build-script-build` (exit status: 1)

INFO: Reading 'startup' options from /usr/src/tmp/mozc-with-jp-dict/src/mozc/src/.bazelrc: --windows_enable_symlinks
Server crashed during startup. Now printing /root/.cache/bazel/_bazel_root/7cf5d81357f08e7007592eb7ec47290c/server/jvm.out
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
==> ERROR: A failure occurred in build().
    Aborting...

phoepsilonix commented on 2024-08-27 00:46 (UTC)

61.patch has been updated. Please delete 61.patch before building. This will ensure that the new 61.patch is re-downloaded.

phoepsilonix commented on 2024-08-26 00:02 (UTC) (edited on 2025-07-05 04:36 (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 ../../..

sudo pacman -Rs fcitx-qt6 fcitx
makepkg -p PKGBUILD

The development of Fcitx has transitioned to Fcitx5, and Fcitx-Mozc is no longer maintained. Please try the following command.

sudo pacman -Rs fcitx5-qt fcitx5
makepkg -p PKGBUILD.fcitx

If you are looking for pre-built package files, please check the following GitHub site.
https://github.com/phoepsilonix/mozc-arch/releases

phoepsilonix commented on 2024-01-25 04:31 (UTC) (edited on 2024-01-25 06:59 (UTC) by phoepsilonix)

@eagleflo

What are the CFLAGS and CXXFLAGS settings in makepkg.conf? In my environment, -U_FORTIFY_SOURCE is included, but I am able to build without any problem.
I am able to build with either gcc or clang.
-D_FORTIFY_SOURCE=1 and U_FORTIFY_SOURCE are set at the same time, which may be causing the error.

Should I ignore CFLAGS etc in makepkg.conf?

I have adjusted the _FORTIFY_SOURCE so that it is not set more than once. Adjusted to not use CFLAGS in makepkg.conf when using gcc.

eagleflo commented on 2024-01-24 18:12 (UTC)

This doesn't seem to build due to redefining _FORTIFY_SOURCE, somehow:

[...]
==> 6. Finally add UT dictionary to mozc source
Starting local Bazel server and connecting to it...
INFO: Analyzed 2 targets (172 packages loaded, 8262 targets configured).
ERROR: /home/aku/.cache/bazel/_bazel_aku/d29b003fe2642b307a65eadf17216668/external/com_google_protobuf/src/google/protobuf/stubs/BUILD.bazel:12:11: Compiling src/google/protobuf/stubs/common.cc failed: (Exit 1): gcc failed: error executing CppCompile command (from target @@com_google_protobuf//src/google/protobuf/stubs:lite) /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections ... (remaining 61 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
<command-line>: error: "_FORTIFY_SOURCE" redefined [-Werror]
<command-line>: note: this is the location of the previous definition
cc1plus: all warnings being treated as errors
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 7.011s, Critical Path: 3.52s
INFO: 32 processes: 18 internal, 14 linux-sandbox.
ERROR: Build did NOT complete successfully
==> ERROR: A failure occurred in build().

phoepsilonix commented on 2024-01-23 02:03 (UTC) (edited on 2024-01-24 15:00 (UTC) by phoepsilonix)

@hypnagogic

The Ruby script used to generate the dictionary was rewritten in Rust. An awk script to remove duplicate entries from the dictionary was also provided. The dependency on Ruby was completely removed. Instead, it relies on rustup.

hypnagogic commented on 2023-12-14 01:25 (UTC)

these specific ruby hard dependencies suck... I already have ruby and a ruby version manager installed. this package makes me install them again.

1 2 Next › Last »