Upstream made a release last month and this release will depend on a more recent abseil-cpp https://github.com/google/mozc/releases/tag/2.26.4660.102
-9999 is also in bad shape, as at least mozc-2.26.4220-system_abseil-cpp.patch fails to apply.
ping
Created attachment 825059 [details] Build for 2.26.4660.102 With this ebuild and this patch, I can get mozc building. Note that you must upgrade abseil-cpp to a 2021-11 version, which conflicts with mozc-2.26.4220's 2020 requirement. Things need to be cleaned up (there doesn't need to be version checking in the 4660 ebuild, because version is a given?), and the maintainer may prefer to split this patch to multiple files. I've only built it. I haven't tested it.
(In reply to Jack Daniels from comment #3) > I've only built it. I haven't tested it. I've been running it for a week or so, all seems to be working properly. I don't use it very extensively, though, and I'm unsure what all the individual patch files for the previous version were - configuration directory, server path (which applies only to Windows), include_dirs modifications, gtest/mock, and jsoncpp.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=669a3f32c87981d710784a2f0ee1c97f3ecc32de commit 669a3f32c87981d710784a2f0ee1c97f3ecc32de Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2022-12-25 19:59:50 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2022-12-25 20:01:54 +0000 app-i18n/mozc: drop unmaintained broken out-of-sync 9999 ebuild Bug: https://bugs.gentoo.org/843227 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> app-i18n/mozc/mozc-9999.ebuild | 380 ----------------------------------------- 1 file changed, 380 deletions(-)
