Summary: | app-i18n/ibus-libpinyin-1.15.2-r1 - [perl-5.40] [ncurses-6.5] [icu-75.1] lua-plugin-init.c: error: passing argument 2 of luaL_addlstring from incompatible pointer type [-Wincompatible-poi | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Graham <graham> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | cjk, graham |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 935270 | ||
Bug Blocks: | 870412 | ||
Attachments: |
emerge-info.txt
app-i18n:ibus-libpinyin-1.15.2-r1:20240625-041131.log emerge-history.txt environment etc.clang.tar.xz etc.portage.tar.xz logs.tar.xz qlist-info.txt.xz temp.tar.xz |
Description
Toralf Förster
![]() 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. |