[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1066226: fcitx-fbterm: FTBFS: fcitx-fbterm.c:116:5: error: implicit declaration of function ‘fcitx_client_enable_ic’; did you mean ‘fcitx_client_focus_in’? [-Werror=implicit-function-declaration]



Source: fcitx-fbterm
Version: 0.2.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie ftbfs-impfuncdef

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

This is most likely caused by a change in dpkg 1.22.6, that enabled
-Werror=implicit-function-declaration. For more information, see
https://wiki.debian.org/qa.debian.org/FTBFS#A2024-03-13_-Werror.3Dimplicit-function-declaration

Relevant part (hopefully):
> make[3]: Entering directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
> make[3]: Nothing to be done for 'CMakeFiles/fcitx-modules.target.dir/build'.
> make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
> [ 80%] Built target fcitx-modules.target
> /<<PKGBUILDDIR>>/src/keycode.c: In function ‘keycode_to_keysym’:
> /<<PKGBUILDDIR>>/src/keycode.c:83:16: warning: this statement may fall through [-Wimplicit-fallthrough=]
>    83 |             if (applic_keypad) break;
>       |                ^
> /<<PKGBUILDDIR>>/src/keycode.c:84:9: note: here
>    84 |         case K_BARENUMLOCK:
>       |         ^~~~
> /<<PKGBUILDDIR>>/src/fcitx-fbterm.c: In function ‘im_active’:
> /<<PKGBUILDDIR>>/src/fcitx-fbterm.c:116:5: error: implicit declaration of function ‘fcitx_client_enable_ic’; did you mean ‘fcitx_client_focus_in’? [-Werror=implicit-function-declaration]
>   116 |     fcitx_client_enable_ic(client);
>       |     ^~~~~~~~~~~~~~~~~~~~~~
>       |     fcitx_client_focus_in
> /<<PKGBUILDDIR>>/src/fcitx-fbterm.c: In function ‘im_deactive’:
> /<<PKGBUILDDIR>>/src/fcitx-fbterm.c:126:5: error: implicit declaration of function ‘fcitx_client_close_ic’; did you mean ‘fcitx_client_reset’? [-Werror=implicit-function-declaration]
>   126 |     fcitx_client_close_ic(client);
>       |     ^~~~~~~~~~~~~~~~~~~~~
>       |     fcitx_client_reset
> /<<PKGBUILDDIR>>/src/fcitx-fbterm.c: In function ‘main’:
> /<<PKGBUILDDIR>>/src/fcitx-fbterm.c:350:5: warning: ‘g_type_init’ is deprecated [-Wdeprecated-declarations]
>   350 |     g_type_init();
>       |     ^~~~~~~~~~~
> In file included from /usr/include/glib-2.0/gobject/gobject.h:26,
>                  from /usr/include/glib-2.0/gobject/gbinding.h:31,
>                  from /usr/include/glib-2.0/glib-object.h:24,
>                  from /usr/include/glib-2.0/gio/gioenums.h:30,
>                  from /usr/include/glib-2.0/gio/giotypes.h:30,
>                  from /usr/include/glib-2.0/gio/gio.h:28,
>                  from /<<PKGBUILDDIR>>/src/fcitx-fbterm.c:23:
> /usr/include/glib-2.0/gobject/gtype.h:735:23: note: declared here
>   735 | void                  g_type_init                    (void);
>       |                       ^~~~~~~~~~~
> cc1: some warnings being treated as errors
> make[3]: *** [src/CMakeFiles/fcitx-fbterm.dir/build.make:93: src/CMakeFiles/fcitx-fbterm.dir/fcitx-fbterm.c.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/fcitx-fbterm_0.2.0-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240313&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.


Reply to: