Source: netpipe
Version: 3.7.2-8.1
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):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> mpicc.lam -Wl,-z,relro -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 -DMPI -DMPI2 ./src/netpipe.c \
>            ./src/mpi2.c -o NPmpi2 -I./ 
> ./src/mpi2.c: In function ‘RecvData’:
> ./src/mpi2.c:110:7: error: implicit declaration of function ‘sched_yield’ 
> [-Werror=implicit-function-declaration]
>   110 |       sched_yield(); /* Since we made r_ptr volatile, we don't 
> necessarily
>       |       ^~~~~~~~~~~
> cc1: some warnings being treated as errors
> mpicc.lam: No such file or directory
> make[1]: *** [makefile:255: mpi2] Error 1


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