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

Bug#1066368: filter: FTBFS: actions.c:255:21: error: implicit declaration of function ‘wait’ [-Werror=implicit-function-declaration]



Source: filter
Version: 2.6.3+ds1-3
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):
> cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2  -c -o actions.o actions.c
> actions.c:200:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
>   200 | mail_message(address, fptr,resendflag)
>       | ^~~~~~~~~~~~
> actions.c: In function ‘mail_message’:
> actions.c:255:21: error: implicit declaration of function ‘wait’ [-Werror=implicit-function-declaration]
>   255 |                     wait(&statusp);
>       |                     ^~~~
> actions.c:292:14: error: implicit declaration of function ‘lock’; did you mean ‘lockf’? [-Werror=implicit-function-declaration]
>   292 |         if (!lock()) {
>       |              ^~~~
>       |              lockf
> actions.c:336:9: error: implicit declaration of function ‘unlock’; did you mean ‘unlink’? [-Werror=implicit-function-declaration]
>   336 |         unlock();               /* blamo or not?  Let it decide! */
>       |         ^~~~~~
>       |         unlink
> actions.c: In function ‘save_message’:
> actions.c:393:27: error: implicit declaration of function ‘save_to_folder’ [-Werror=implicit-function-declaration]
>   393 |                     ret = save_to_folder(foldername,tmpfptr);
>       |                           ^~~~~~~~~~~~~~
> actions.c: In function ‘mail_message’:
> actions.c:269:21: warning: ignoring return value of ‘setuid’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
>   269 |                     setuid(user_uid);
>       |                     ^~~~~~~~~~~~~~~~
> actions.c:270:21: warning: ignoring return value of ‘setgid’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
>   270 |                     setgid(user_gid);
>       |                     ^~~~~~~~~~~~~~~~
> actions.c: In function ‘execute’:
> actions.c:544:17: warning: ignoring return value of ‘setgid’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
>   544 |                 setgid(user_gid);
>       |                 ^~~~~~~~~~~~~~~~
> actions.c:545:17: warning: ignoring return value of ‘setuid’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
>   545 |                 setuid(user_uid);
>       |                 ^~~~~~~~~~~~~~~~
> actions.c:549:17: warning: ignoring return value of ‘dup’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
>   549 |                 dup(tmpfd);
>       |                 ^~~~~~~~~~
> cc1: some warnings being treated as errors
> make[1]: *** [<builtin>: actions.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/03/13/filter_2.6.3+ds1-3_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: