Package Base Details: mozc

Git Clone URL: (read-only)
Submitter: ponsfoot
Maintainer: ponsfoot
Last Packager: ponsfoot
Votes: 56
Popularity: 0.846820
First Submitted: 2010-08-09 04:27
Last Updated: 2018-11-30 11:34

Packages (3)

Pinned Comments

ponsfoot commented on 2013-05-28 07:43

(repository moved)
Unofficial user repository of Mozc is ready.
If you want to use the repo, add the following into your /etc/pacman.conf


SigLevel = Optional TrustAll

Server =

You can specify `pacman -S mozc-im' to choose all of Mozc packages.

See for more detail.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

ponsfoot commented on 2018-03-02 13:15


I intend to bump latest commit of mozc (which fixes ibus-mozc issue) with latest zipcode but cannot it due to trouble. Please give me some time. I might change file hosting service.


polm23 commented on 2017-09-11 07:14

Minor issue: This requires pkg-config, but it's not listed as a dependency. Noticed setting it up on a fresh machine.

linkmauve commented on 2017-04-20 13:43

Hi, on an up to date ArchLinux, using clang 4.0 from testing, I get this error when building this PKGBUILD:

clang-4.0: error: unknown argument: '-fvar-tracking-assignments'

If I remove it from the DEBUG_CFLAGS and the DEBUG_CXXFLAGS in /etc/makepkg.conf it does build. Since this argument is present in the default configuration, you should probably workaround it somehow.

ponsfoot commented on 2017-04-16 09:59

It should be fixed on 2.20.2673.102-2.
Thank you for the info.

eschwartz commented on 2017-04-14 17:13

Someone on IRC was having problems building this package with pacaur, and it turned out that the build system was calling `python` when it expected to get `python2`.[1] Doing some investigating in this PKGBUILD, I see you do actually try to work around this.

However... makepkg supports doing the download/extraction/prepare separate from the build, using the logic `makepkg --nobuild && makepkg --noextract`.[2] This is a perfectly valid use case, and PKGBUILDs are expected to work when used like that.

Setting environment variables -- in this case $PATH -- within the prepare() function and expecting them to still be available in the build() function breaks this logic and WILL NOT WORK.
Please fix your PKGBUILD to conform to proper makepkg standards. :)

[1] This is a definite upstream bug, and on my advice that IRC user opened the following bug report which if fixed should remove the need for such hacks:
[2] pacaur happens to trigger this issue, because it uses separate extraction and build steps for internal reasons. A number of PKGBUILDs that are flawed like this one is, have been discovered as a result.

ponsfoot commented on 2017-01-10 07:38

Please ask fcitx-mozc maintainer if emacs-mozc is not available in it.

mkasu commented on 2017-01-10 05:18

I'm interested in using emacs-mozc together with fcitx-mozc. Down below you said you'd integrate it into a "mozc-svn" package, but I couldn't find one with that name. Any advice?

ponsfoot commented on 2016-11-15 10:48

Please see nash's latest comment.
Is the HiDPI problem fixed on qt5 version? If so, I'll change to use qt5.

AKremlin commented on 2016-11-10 12:21

I understand the reason for keeping the dependency on qt4 until upstream bumps it (it's being held back because of lack of Windows support, but the Github master uses qt5 for linux and OSX). However, I would like to pkgbuild it using qt5, because I can't use the settings dialogue on my high-DPI display. How can I get it to build with qt5? I have qt5 installed on my system.

ponsfoot commented on 2016-10-29 08:30

Specifying version is based on Release History.
Latest version on it is still using qt4.