Package Details: fcitx5-mozc-ut 2.30.5432.102-1

Git Clone URL: https://aur.archlinux.org/fcitx5-mozc-ut.git (read-only, click to copy)
Package Base: fcitx5-mozc-ut
Description: Mozc module for Fcitx5
Upstream URL: https://github.com/fcitx/mozc
Licenses: Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND GPL-2.0-or-later AND MIT AND NAIST-2003 AND Unicode-3.0 AND LicenseRef-Okinawa-Dictionary
Conflicts: fcitx5-mozc
Provides: fcitx5-mozc
Submitter: Nocifer
Maintainer: Nocifer
Last Packager: Nocifer
Votes: 29
Popularity: 0.82
First Submitted: 2020-12-08 09:21 (UTC)
Last Updated: 2024-04-07 11:49 (UTC)

Required by (2)

Sources (1)

Pinned Comments

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

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

Latest Comments

1 2 3 4 Next › Last »

silikeite commented on 2024-04-19 07:29 (UTC)

I wonder if the dependency on mozc should instead be specifically for mozc-ut. This isn't a problem when building the AUR package manually or installing using yay, but works around an as-of-now still unfixed issue from paru since February where it insists on installing specifically aur/mozc and causing an internal conflict. [I recently tried switching from yay to paru due to issues in the flutter package which is how I found out this issue.]

I understand that adjusting the PKGBUILD to work around issues with package helpers may be a bad practice but thought to bring it up.

https://github.com/Morganamilo/paru/issues/1129

Nocifer commented on 2024-04-12 10:03 (UTC)

Hmm, to be honest your error sounds more like a bug than anything else, but I can't reproduce it so I can't even try to debug it.

One thing you could do is change this line in the PKGBUILD:

bazel build server:mozc_server gui/tool:mozc_tool --config oss_linux --compilation_mode opt

into this:

bazel build --verbose_failures server:mozc_server gui/tool:mozc_tool --config oss_linux --compilation_mode opt

which may provide some further hints about what exactly goes wrong in your build.

For clarification's sake, this change should go in mozc-ut's PKGBUILD, as that's where this error originates from. As your log shows, the failure of this package is a byproduct of the failure of mozc-ut on which it depends.

soemintun commented on 2024-04-11 00:36 (UTC)

Sorry for late reply. It's my first time trying to build. I couldn't make it in a clean chroot too. I got the same without using helper.

Nocifer commented on 2024-04-09 09:39 (UTC)

@soemintun The package builds fine for me, both normally and in a clean chroot. I'd suggest trying to build it without yay/paru, in a clean chroot, to rule out any possible misconfiguration/incompatibility specific to your system.

Also, is this your first time building this package or an attempt at updating it?

soemintun commented on 2024-04-09 00:22 (UTC) (edited on 2024-04-09 00:25 (UTC) by soemintun)

Build failed. I already tried deleting .cache/bazel & yay -Scc. I got same error in yay & paru while building UT dictionary

Compiling the UT dictionary...

==> Sources are ready.
==> Making package: mozc-ut 2.30.5432.102.20240407-1 (Tue 09 Apr 2024 08:38:45 AM JST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Starting build()...
Starting local Bazel server and connecting to it...
INFO: Analyzed 2 targets (161 packages loaded, 8434 targets configured).
ERROR: /home/soe/.cache/bazel/_bazel_soe/83c77da4e9edfa5cb6c35b7883d703f7/external/com_google_absl/absl/strings/BUILD.bazel:1265:11: Compiling absl/strings/internal/str_format/float_conversion.cc failed: (Exit 1): gcc failed: error executing CppCompile command (from target @@com_google_absl//absl/strings:str_format_internal) /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 39 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
external/com_google_absl/absl/strings/internal/str_format/float_conversion.cc:1287:26: internal compiler error: Segmentation fault
 1287 |                    Buffer* out,
      |                          ^
0x1ad33c8 internal_error(char const*, ...)
        ???:0
Please submit a full bug report, with preprocessed source (by using -freport-bug).
Please include the complete backtrace with any bug report.
See <https://bugs.archlinux.org/> for instructions.
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 5.200s, Critical Path: 2.46s
INFO: 103 processes: 33 internal, 70 linux-sandbox.
ERROR: Build did NOT complete successfully
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: mozc-ut-exit status 4
==> Making package: fcitx5-mozc-ut 2.30.5432.102-1 (Tue 09 Apr 2024 08:38:53 AM JST)
==> Checking runtime dependencies...
==> Missing dependencies:
  -> mozc>=2.30.5432.102
==> Checking buildtime dependencies...
==> ERROR: Could not resolve all dependencies.
 -> error making: fcitx5-mozc-ut-exit status 8
 -> Failed to install the following packages. Manual intervention is required:
mozc-ut - exit status 4
fcitx5-mozc-ut - exit status 8

AlphaCentauri commented on 2024-03-28 15:38 (UTC) (edited on 2024-03-28 15:39 (UTC) by AlphaCentauri)

Apologies, that was indeed the issue. Fresh install, knew I forgot a step. Thank you, I deleted the previous comment.

Nocifer commented on 2024-03-28 12:39 (UTC)

Have you installed the base-devel package?

Nocifer commented on 2024-03-09 13:09 (UTC)

Sorry for the fsck up, I don't even know how I managed to do that. Package permissions have (hopefully) been fixed.

Nocifer commented on 2024-01-22 19:16 (UTC)

@eagleflo Luckily today was update day anyway (upstream finally pushed a new build tag after two months of nada) so Bazel 7.0 compatibility has also been taken care of.

1 2 3 4 Next › Last »