@fabiscafe
Mr fabiscafe, thank you for your report.
Various issues can arise concerning Rust and Bazel versions and installations. It's also possible that the Rust server might be experiencing temporary difficulties. Some users may even have multiple versions installed to switch between them.
I had intended to accommodate users with TARGETs other than x86_64 for future use, but the core cause this time was likely that it wasn't functioning correctly within the chroot environment.
Thanks to you, fabiscafe, I were able to fix this.
I would also like to express my gratitude once again to the other individuals who submitted reports.
Also, thank you for pointing out the Rust guidelines. I'll check them out later.
Thank you.
PS
I am taking my time waiting for a response to the next merge request. I would be delighted if you could also take things a little more slowly and wait a little longer.
https://gitlab.archlinux.org/archlinux/packaging/packages/fcitx5-mozc/-/merge_requests/8
Pinned Comments
phoepsilonix commented on 2024-08-26 00:02 (UTC) (edited on 2025-09-13 04:30 (UTC) by phoepsilonix)
If you're encountering errors during the build process, try deleting your Bazel cache (located at ~/.cache/bazel by default).
or
The development of Fcitx has transitioned to Fcitx5, and Fcitx-Mozc is no longer maintained. Please try the following command.
I use the following site for build verification and build automation.
If you encounter any issues, please also check here. It may be helpful.
If you are looking for pre-built package files, please check the following GitHub site.
https://github.com/phoepsilonix/mozc-arch/releases