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

Bug#1066714: kinput2: FTBFS: XimpProto.c:390:11: error: implicit declaration of function ‘sprintf’ [-Werror=implicit-function-declaration]



Source: kinput2
Version: 3.1-14
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):
> gcc -c -g -O2 -fno-strict-aliasing -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2   -I../include -Iimlib  -I/usr/include       -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L 				-D_POSIX_SOURCE -D_XOPEN_SOURCE 				-D_BSD_SOURCE -D_SVID_SOURCE                                 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 				  				  -DFUNCPROTO=15 -DNARROWPROTO        XimpProto.c
> In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25,
>                  from /usr/include/X11/Xos.h:42,
>                  from XimpProto.c:21:
> /usr/include/features.h:195:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   195 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
>       |   ^~~~~~~
> XimpProto.c: In function ‘getAtoms’:
> XimpProto.c:390:11: error: implicit declaration of function ‘sprintf’ [-Werror=implicit-function-declaration]
>   390 |     (void)sprintf(buf, "_XIMP_%s", xpw->ximp.localename);
>       |           ^~~~~~~
> XimpProto.c:45:1: note: include ‘<stdio.h>’ or provide a declaration of ‘sprintf’
>    44 | #include "DebugPrint.h"
>   +++ |+#include <stdio.h>
>    45 | 
> XimpProto.c:390:11: warning: incompatible implicit declaration of built-in function ‘sprintf’ [-Wbuiltin-declaration-mismatch]
>   390 |     (void)sprintf(buf, "_XIMP_%s", xpw->ximp.localename);
>       |           ^~~~~~~
> XimpProto.c:390:11: note: include ‘<stdio.h>’ or provide a declaration of ‘sprintf’
> XimpProto.c: In function ‘newClient’:
> XimpProto.c:477:15: warning: incompatible implicit declaration of built-in function ‘sprintf’ [-Wbuiltin-declaration-mismatch]
>   477 |         (void)sprintf(buf, "_XIMP_STRING_%d", xpw->ximp.propid++);
>       |               ^~~~~~~
> XimpProto.c:477:15: note: include ‘<stdio.h>’ or provide a declaration of ‘sprintf’
> XimpProto.c: In function ‘endCallback’:
> XimpProto.c:1943:17: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
>  1943 |     int abort = (int)call_data;
>       |                 ^
> XimpProto.c: In function ‘preeditCaretCallback’:
> XimpProto.c:2717:17: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
>  2717 |     int caret = (int)call_data;
>       |                 ^
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile:1118: XimpProto.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/kinput2_3.1-14_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: