Package Details: mozc 2.30.5448.102-1

Git Clone URL: https://aur.archlinux.org/mozc.git (read-only, click to copy)
Package Base: mozc
Description: The Open Source edition of Google Japanese Input
Upstream URL: https://github.com/google/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: mozc-ut
Submitter: ponsfoot
Maintainer: Nocifer
Last Packager: Nocifer
Votes: 78
Popularity: 0.70
First Submitted: 2010-08-09 04:27 (UTC)
Last Updated: 2024-04-26 20:47 (UTC)

Dependencies (7)

Sources (1)

Pinned Comments

Nocifer commented on 2022-05-29 21:53 (UTC) (edited on 2023-08-22 09:33 (UTC) by Nocifer)

If you're getting compilation errors, please delete your Bazel cache (~/.cache/bazel by default).

Latest Comments

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

ponsfoot commented on 2018-10-31 10:21 (UTC)

@MaxMilton: Okay. I'll move them. Please wait.

MaxMilton commented on 2018-10-30 19:35 (UTC)

Package fails to install due to SHA1 sum mismatch. Looks like instead of downloading the jigyosyo-201805.zip and x-ken-all-201805.zip files, it instead fetches the sourceforge download page. Please move your packages away from sourceforge -- GitHub etc. is be a much better option now-a-days.

ponsfoot commented on 2018-05-31 12:32 (UTC)

@MightyPork: Applied, Thank you for the patch.

MightyPork commented on 2018-05-27 10:26 (UTC) (edited on 2018-05-27 10:29 (UTC) by MightyPork)

This package does not build.

Fix by using custom.patch (fixes the build error and also enables hiragana by default, so you don't need to click in the tray menu)

https://gist.githubusercontent.com/MightyPork/6b93f56b404e526268ac133f1a783afd/raw/40b3b9569d4b0741d78c511b247b26d2b1e7a2ae/mozc.patch

and adding

patch -Np0 -i "${srcdir}/custom.patch"

at the top of prepare () {

then run updpkgsums and makepkg -f

ponsfoot commented on 2018-03-02 13:15 (UTC)

Hi,

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

Thx

polm23 commented on 2017-09-11 07:14 (UTC)

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 (UTC)

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 (UTC)

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

eschwartz commented on 2017-04-14 17:13 (UTC)

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: https://github.com/google/mozc/issues/417 [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 (UTC)

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

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