| ~~~^ ~~~ | | | | | lua_Integer {aka long int} | unsigned int | %0*lx lua-plugin-init.c: In function 'ime_utf8_to_utf16': lua-plugin-init.c:412:27: error: passing argument 2 of 'luaL_addlstring' from incompatible pointer type [-Wincompatible-pointer-types] 412 | luaL_addlstring(&buf, str, written * sizeof(gunichar2)); | ^~~ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_desktop_gnome_systemd-20240621-221521 UNMASKED: ~dev-libs/icu-75.1 ~dev-libs/icu-layoutex-75.1 Requested by sam >=sys-libs/ncurses-6.5 Requested by sam ~dev-lang/perl-5.40.0 ~virtual/perl-Archive-Tar-3.20.10_rc ~virtual/perl-CPAN-Meta-Requirements-2.143.0 ~virtual/perl-Compress-Raw-Bzip2-2.212.0 ~virtual/perl-DB_File-1.859.0 ~virtual/perl-Data-Dumper-2.189.0 ~virtual/perl-Devel-PPPort-3.720.0 ~virtual/perl-Exporter-5.780.0 ~virtual/perl-ExtUtils-CBuilder-0.280.240 ~virtual/perl-ExtUtils-Manifest-1.750.0 ~virtual/perl-File-Spec-3.900.0 ~virtual/perl-HTTP-Tiny-0.88.0 ~virtual/perl-IO-1.550.0 ~virtual/perl-IO-Compress-2.212.0 ~virtual/perl-IO-Socket-IP-0.420.0 ~virtual/perl-IO-Zlib-1.150.0 ~virtual/perl-Math-BigInt-2.3.2 ~virtual/perl-Math-BigInt-FastCalc-0.501.800 ~virtual/perl-Math-BigRat-2.3.2 ~virtual/perl-Module-CoreList-5.202.406.90 ~virtual/perl-Module-Metadata-1.0.38 ~virtual/perl-Pod-Simple-3.450.0 ~virtual/perl-Safe-2.460.0 ~virtual/perl-Socket-2.38.0 ~virtual/perl-Test-Harness-3.480.0 ~virtual/perl-Test-Simple-1.302.199 ~virtual/perl-Text-Tabs+Wrap-2024.1.0 ~virtual/perl-Time-HiRes-1.977.700 ~virtual/perl-Time-Local-1.350.0 ~virtual/perl-autodie-2.370.0 ~virtual/perl-bignum-0.670.0 ~virtual/perl-podlators-5.10.200_rc ~virtual/perl-threads-2.400.0 ~virtual/perl-threads-shared-1.690.0 ~virtual/perl-version-0.993.0 Requested by dilfridge and sam The attached etc.portage.tar.xz has all details. ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-14 * clang/llvm (if any): clang version 18.1.7 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/18/bin Configuration file: /etc/clang/x86_64-pc-linux-gnu-clang.cfg /usr/lib/llvm/18 18.1.7 Python 3.12.4 Available Ruby profiles: [1] ruby31 (with Rubygems) [2] ruby32 (with Rubygems) [3] ruby33 (with Rubygems) * Available Rust versions: [1] rust-bin-1.79.0 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 17.0.11_p9 [openjdk-bin-17] *) Eclipse Temurin JDK 21.0.3_p9 [openjdk-bin-21] 3) Eclipse Temurin JDK 8.412_p08 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-17 [3] openjdk-bin-21 system-vm The Glorious Glasgow Haskell Compilation System, version 9.2.8 php cli (if any): go version go1.22.4 linux/amd64 HEAD of ::gentoo commit 252642f432f041bae98b8348d38fbc859d0c3dc0 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Tue Jun 25 03:19:11 2024 +0000 2024-06-25 03:19:11 UTC emerge -qpvO app-i18n/ibus-libpinyin [ebuild N ] app-i18n/ibus-libpinyin-1.15.2-r1 USE="lua -boost -opencc" LUA_SINGLE_TARGET="lua5-1 -lua5-3" PYTHON_SINGLE_TARGET="python3_12 -python3_10 -python3_11"
Created attachment 896379 [details] emerge-info.txt
Created attachment 896380 [details] app-i18n:ibus-libpinyin-1.15.2-r1:20240625-041131.log
Created attachment 896381 [details] emerge-history.txt
Created attachment 896382 [details] environment
Created attachment 896383 [details] etc.clang.tar.xz
Created attachment 896384 [details] etc.portage.tar.xz
Created attachment 896385 [details] logs.tar.xz
Created attachment 896386 [details] qlist-info.txt.xz
Created attachment 896387 [details] temp.tar.xz
This compiles and works fine on my own machine (x86_64) when i use the same useflags (lua only). So I don't think this is a current real-world issue (yet). I am guessing the issue might be changes in the compiler as i am on the stable x86_64-pc-linux-gnu-13 (not -14 that the unstable test build was using that generated this).
I had a look upstream, and found this :- https://github.com/libpinyin/ibus-libpinyin/commit/cf33a2c289f7676a36954bdcf700a9d0086d6886 I believe this is probably the issue, and applying that change should fix it. If so, it can be fixed in two ways:- 1. Upgrade the package to the latest version or 2. Adhoc Patch this into the current version. Ideally '1' is the best solution, but the reason we aren't already running with the latest version is that it failed testing and had some very weird behavior (excessive latency etc) which made it unusable. Still that was several months ago, so I will take another look at this.
I did some testing with current latest (1.15.7) and it seemed fine, none of the latency issues that i mentioned above. As such we can just bump the version and this should resolve this bug.
