@wiegraffolles:
Build preparation (ln -sf `which python2` $srcdir/python in PKGBUILD) seems to failed.
Try again. It's not reproduced on my system.
If you don't have a strong insistence, try to use unofficial user repository:
https://wiki.archlinux.org/index.php/Mozc#Unofficial_user_repository
Note: Please show me full build log using http://pastebin.com/ from the next time.
Search Criteria
Package Details: mozc 2.30.5618.102-1
Package Actions
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: | 81 |
Popularity: | 0.98 |
First Submitted: | 2010-08-09 04:27 (UTC) |
Last Updated: | 2024-10-10 12:38 (UTC) |
Dependencies (8)
- qt6-base (qt6-base-headlessAUR, qt6-base-gitAUR)
- bazel (bazel-gitAUR, bazel024-binAUR, bazel3AUR, bazel3-binAUR, bazel5AUR, bazelisk-gitAUR, bazeliskAUR, bazelisk-binAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- qt6-base (qt6-base-headlessAUR, qt6-base-gitAUR) (make)
- emacs-mozcAUR (emacs-mozc-with-jp-dictAUR) (optional) – Emacs integration
- fcitx5-mozc-utAUR (optional) – Fcitx5 integration
- ibus-mozcAUR (ibus-mozc-with-jp-dictAUR) (optional) – IBus integration
Required by (5)
Sources (8)
- git+https://github.com/abseil/abseil-cpp.git#commit=4447c7562e3bc702ade25105912dce503f0c4010
- git+https://github.com/chromium/gyp.git#commit=9ecf45e37677743503342ee4c6a76eaee80e4a7f
- git+https://github.com/google/breakpad.git#commit=216cea7bca53fa441a3ee0d0f5fd339a3a894224
- git+https://github.com/google/googletest.git#commit=b514bdc898e2951020cbdca1304b75f5950d1f59
- git+https://github.com/google/mozc.git#commit=1d74ac4a0f569aaa99838df861997f3e882add3c
- git+https://github.com/hiroyuki-komatsu/japanese-usage-dictionary.git#commit=e5b3425575734c323e1d947009dd74709437b684
- git+https://github.com/microsoft/wil.git#commit=fc5dbf55989fe20351c71d038a8d12de4b397a6d
- git+https://github.com/protocolbuffers/protobuf.git#commit=7cc670c1809e704ebeba90fb430d50e009f36727
Latest Comments
« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 16 Next › Last »
ponsfoot commented on 2015-02-09 10:51 (UTC)
wiegraffolles commented on 2015-02-09 09:55 (UTC)
I get this error when trying to build the latest update:
INFO: Running: ninja -j 8 -C out_linux/Release mozc_server mozc_tool ibus_mozc mozc_renderer
ninja: Entering directory `out_linux/Release'
[8/841] ACTION Generating gen/gui/character_pad/data/cp932_map.h.
FAILED: cd ../../gui; python ../build_tools/redirect.py ../out_linux/Release/gen/gui/character_pad/data/cp932_map.h character_pad/data/gen_cp932_map.py ../data/unicode/CP932.TXT
File "../build_tools/redirect.py", line 61
print '=========='
^
SyntaxError: Missing parentheses in call to 'print'
[8/841] ACTION Generating Resource file from config_dialog.qrc
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
File "build_mozc.py", line 1454, in <module>
main()
File "build_mozc.py", line 1450, in main
procedure[1](cmd_opts, cmd_args, original_directory_name)
File "build_mozc.py", line 1070, in BuildMain
BuildOnLinux(options, targets, original_directory_name)
File "build_mozc.py", line 1026, in BuildOnLinux
RunOrDie([make_command] + build_args + target_names)
File "/tmp/makepkg/mozc/src/mozc/build_tools/util.py", line 99, in RunOrDie
'==========']))
build_tools.util.RunOrDieError:
==========
ERROR: ninja -j 8 -C out_linux/Release mozc_server mozc_tool ibus_mozc mozc_renderer
==========
==> ERROR: A failure occurred in build().
Aborting...
:: mozc cleaning skipped
:: failed to build ibus-mozc,mozc package(s)
Any ideas on how to fix it?
m13253 commented on 2015-01-25 14:20 (UTC)
It seems that the latest Mozc source requiers gyp available as a command:
Traceback (most recent call last):
File "build_mozc.py", line 1478, in <module>
main()
File "build_mozc.py", line 1474, in main
procedure[1](cmd_opts, cmd_args, original_directory_name)
File "build_mozc.py", line 958, in GypMain
RunOrDie(gyp_command + gyp_options)
File "/tmp/yaourt-tmp-brilliant/aur-mozc/src/mozc/build_tools/util.py", line 99, in RunOrDie
Maybe we should depend on gyp / gyp-svn, or set $PATH to enable gyp instantly?
ponsfoot commented on 2014-11-03 06:06 (UTC)
ninja is unnecessary as makedepends anymore.
taro-k commented on 2014-10-13 06:48 (UTC)
@ponsfoot Thanks lot for your immediate reply and understanding. Also I am happy about you understood this is general security thing on AUR (and beyond, as you stated.) I am looking forward to the next release.
ponsfoot commented on 2014-10-13 05:26 (UTC)
@taro-k:
I can see how you feel (but, in your opinion, all binary repos and many other distros which provides source tar balls themselves like debian, fedora etc. have same concern).
Actually, getting source from upstream directly is easier than current style for maintenance.
You think 1 min for download is just 'only' (and you should downloaded depot_tools using git, too), I will accommodate a request from you (on the next release) if there is no opposition from other people.
mozc-svn is suitable for your concern.
taro-k commented on 2014-10-13 03:25 (UTC)
@ponsfoot thx. IMO, not trivial amount of users have concern about security/privacy especially for this kind of program. The direct download from upstream must make this point clear at least. If you don't like to do that, I will submit another package based on your great work. For such users, some additional makedepends don't matter. Also I just downloaded by svn but it took only 1 min. with narrow band not in developed country.
ponsfoot commented on 2014-10-13 02:08 (UTC)
@taro-k:
The upstream doesn't provide source tar balls for each version's any more.
If you want to get latest version of Mozc from upstream, you have to clone from svn repo. I think it's not efficient for end users as AUR package which requires longer download time and svn as makedepends.
taro-k commented on 2014-10-13 01:32 (UTC)
Hi, thx lot for your contribution. The "source" seems to be the private storage, not official/upstream source tree. I feel it's better the source is downloaded from upstream directly like many of other AUR packages.
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).