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

Bug#1066238: dvbackup: FTBFS: dvconnect.c:264:33: error: implicit declaration of function ‘memcpy’ [-Werror=implicit-function-declaration]



Source: dvbackup
Version: 1:0.0.4-9
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 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fPIE -pie -Wl,-z,relro -Wl,-z,now -D_FORTIFY_SOURCE=2 -DHAVE_LIBPOPT -o dvconnect dvconnect.c -lpopt -lpthread
> dvconnect.c: In function ‘handle_packet’:
> dvconnect.c:264:33: error: implicit declaration of function ‘memcpy’ [-Werror=implicit-function-declaration]
>   264 |                                 memcpy(p_out, data + 12, 480);
>       |                                 ^~~~~~
> dvconnect.c:22:1: note: include ‘<string.h>’ or provide a declaration of ‘memcpy’
>    21 | #include <malloc.h>
>   +++ |+#include <string.h>
>    22 | 
> dvconnect.c:264:33: warning: incompatible implicit declaration of built-in function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
>   264 |                                 memcpy(p_out, data + 12, 480);
>       |                                 ^~~~~~
> dvconnect.c:264:33: note: include ‘<string.h>’ or provide a declaration of ‘memcpy’
> dvconnect.c: In function ‘capture_raw’:
> dvconnect.c:326:26: error: implicit declaration of function ‘strcmp’ [-Werror=implicit-function-declaration]
>   326 |         if (!filename || strcmp(filename, "-") == 0) {
>       |                          ^~~~~~
> dvconnect.c:326:26: note: include ‘<string.h>’ or provide a declaration of ‘strcmp’
> dvconnect.c:401:25: error: implicit declaration of function ‘memset’ [-Werror=implicit-function-declaration]
>   401 |                         memset(curr, 0, v.buf_size);
>       |                         ^~~~~~
> dvconnect.c:401:25: note: include ‘<string.h>’ or provide a declaration of ‘memset’
> dvconnect.c:401:25: warning: incompatible implicit declaration of built-in function ‘memset’ [-Wbuiltin-declaration-mismatch]
> dvconnect.c:401:25: note: include ‘<string.h>’ or provide a declaration of ‘memset’
> dvconnect.c:426:41: warning: incompatible implicit declaration of built-in function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
>   426 |                                         memcpy(outbuf + outbuf_used, curr+ofs,
>       |                                         ^~~~~~
> dvconnect.c:426:41: note: include ‘<string.h>’ or provide a declaration of ‘memcpy’
> dvconnect.c:431:41: warning: incompatible implicit declaration of built-in function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
>   431 |                                         memcpy(outbuf + outbuf_used,
>       |                                         ^~~~~~
> dvconnect.c:431:41: note: include ‘<string.h>’ or provide a declaration of ‘memcpy’
> dvconnect.c: In function ‘fill_buffer’:
> dvconnect.c:584:33: warning: incompatible implicit declaration of built-in function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
>   584 |                                 memcpy(f_node->data, underrun_data_frame,
>       |                                 ^~~~~~
> dvconnect.c:584:33: note: include ‘<string.h>’ or provide a declaration of ‘memcpy’
> dvconnect.c:633:25: warning: incompatible implicit declaration of built-in function ‘memcpy’ [-Wbuiltin-declaration-mismatch]
>   633 |                         memcpy(p, frame + vdata, 480);
>       |                         ^~~~~~
> dvconnect.c:633:25: note: include ‘<string.h>’ or provide a declaration of ‘memcpy’
> dvconnect.c: In function ‘send_raw’:
> dvconnect.c:782:9: warning: incompatible implicit declaration of built-in function ‘memset’ [-Wbuiltin-declaration-mismatch]
>   782 |         memset(packet_sizes, 0, sizeof(packet_sizes));
>       |         ^~~~~~
> dvconnect.c:782:9: note: include ‘<string.h>’ or provide a declaration of ‘memset’
> dvconnect.c: In function ‘rt_raisepri’:
> dvconnect.c:848:17: warning: incompatible implicit declaration of built-in function ‘memset’ [-Wbuiltin-declaration-mismatch]
>   848 |                 memset (&scp, '\0', sizeof (scp));
>       |                 ^~~~~~
> dvconnect.c:848:17: note: include ‘<string.h>’ or provide a declaration of ‘memset’
> dvconnect.c: In function ‘sig_int_recv_handler’:
> dvconnect.c:305:9: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
>   305 |         write(2, t, sizeof(t));
>       |         ^~~~~~~~~~~~~~~~~~~~~~
> dvconnect.c: In function ‘sig_int_send_handler’:
> dvconnect.c:499:9: warning: ignoring return value of ‘write’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
>   499 |         write(2, t, sizeof(t));
>       |         ^~~~~~~~~~~~~~~~~~~~~~
> cc1: some warnings being treated as errors
> make[2]: *** [Makefile:16: dvconnect] Error 1


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