Package Details: fcitx5-mozc-with-jp-dict 2.30.5432.102-6

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 with UT dictionary
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 LGPL-3.0-only AND MIT AND NAIST-2003
Conflicts: fcitx, fcitx-mozc, fcitx-mozc-with-jp-dict, fcitx-qt5, fcitx-qt6, fcitx5-mozc, ibus-mozc, ibus-mozc-with-jp-dict, mozc-with-jp-dict-common
Provides: fcitx5-mozc
Replaces: fcitx5-mozc, mozc-with-jp-dict-common
Submitter: phoepsilonix
Maintainer: phoepsilonix
Last Packager: phoepsilonix
Votes: 5
Popularity: 1.53
First Submitted: 2023-03-14 08:19 (UTC)
Last Updated: 2024-04-16 02:03 (UTC)

Required by (0)

Sources (6)

Latest Comments

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.

phoepsilonix commented on 2023-08-29 12:59 (UTC)

@Fandekasp fix

Fandekasp commented on 2023-05-30 07:13 (UTC)

==> Validating source files with sha512sums... mozc ... Skipped x-ken-all-202110.zip ... Passed jigyosyo-202110.zip ... Passed mozcdict-ext ... Skipped mecab-naist-jdic-0.6.3b-20111013.tar.gz ... Passed core_lex.zip ... Passed notcore_lex.zip ... Passed mozcdic-ut-alt-cannadic.txt.tar.bz2 ... Passed mozcdic-ut-edict2.txt.tar.bz2 ... FAILED mozcdic-ut-jawiki.txt.tar.bz2 ... FAILED mozcdic-ut-personal-names.txt.tar.bz2 ... FAILED mozcdic-ut-place-names.txt.tar.bz2 ... FAILED mozcdic-ut-skk-jisyo.txt.tar.bz2 ... Passed ==> ERROR: One or more files did not pass the validity check!

also, emacs really shouldn't be a dependency...