Source: yiyantang
Version: 0.7.0-8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@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):
> x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include     
> -DG_LOG_DOMAIN=\"yyt\"     -I../intl -I../intl  -Wdate-time 
> -D_FORTIFY_SOURCE=2  -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> yiyantang_init.c
> xmalloc.c: In function ‘xstrdup’:
> xmalloc.c:136:16: error: implicit declaration of function ‘strlen’ 
> [-Werror=implicit-function-declaration]
>   136 |   p = xmalloc (strlen (str) + 1);
>       |                ^~~~~~
> xmalloc.c:48:1: note: include ‘<string.h>’ or provide a declaration of 
> ‘strlen’
>    47 | #include "error.h"
>   +++ |+#include <string.h>
>    48 | 
> xmalloc.c:136:16: warning: incompatible implicit declaration of built-in 
> function ‘strlen’ [-Wbuiltin-declaration-mismatch]
>   136 |   p = xmalloc (strlen (str) + 1);
>       |                ^~~~~~
> xmalloc.c:136:16: note: include ‘<string.h>’ or provide a declaration of 
> ‘strlen’
> xmalloc.c:137:3: error: implicit declaration of function ‘strcpy’ 
> [-Werror=implicit-function-declaration]
>   137 |   strcpy (p, str);
>       |   ^~~~~~
> xmalloc.c:137:3: note: include ‘<string.h>’ or provide a declaration of 
> ‘strcpy’
> xmalloc.c:137:3: warning: incompatible implicit declaration of built-in 
> function ‘strcpy’ [-Wbuiltin-declaration-mismatch]
> xmalloc.c:137:3: note: include ‘<string.h>’ or provide a declaration of 
> ‘strcpy’
> loop.c: In function ‘loop’:
> loop.c:91:25: error: implicit declaration of function ‘exit’ 
> [-Werror=implicit-function-declaration]
>    91 |                         exit (ret);
>       |                         ^~~~
> loop.c:42:1: note: include ‘<stdlib.h>’ or provide a declaration of ‘exit’
>    41 | #include "zhconv.h"
>   +++ |+#include <stdlib.h>
>    42 | 
> loop.c:91:25: warning: incompatible implicit declaration of built-in function 
> ‘exit’ [-Wbuiltin-declaration-mismatch]
>    91 |                         exit (ret);
>       |                         ^~~~
> loop.c:91:25: note: include ‘<stdlib.h>’ or provide a declaration of ‘exit’
> loop.c:117:33: warning: ignoring return value of ‘write’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   117 |                                 write (ptym, ibuf, ret);
>       |                                 ^~~~~~~~~~~~~~~~~~~~~~~
> loop.c:162:41: warning: ignoring return value of ‘write’ declared with 
> attribute ‘warn_unused_result’ [-Wunused-result]
>   162 |                                         write (STDOUT_FILENO, tbuf2, 
> ret);
>       |                                         
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
> make[3]: *** [Makefile:201: xmalloc.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/yiyantang_0.7.0-8_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240313;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240313&fusertaguser=lu...@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 via email to