Source: jam Version: 2.6.1-2 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): > cc -o ./jam0 -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 builtins.c command.c compile.c > execas400.c execunix.c execvms.c expand.c filent.c fileos2.c fileunix.c > filevms.c glob.c hash.c headers.c jam.c jambase.c jamgram.c lists.c make.c > make1.c newstr.c option.c parse.c pathunix.c pathvms.c regexp.c rules.c > scan.c search.c timestamp.c variable.c -Wl,-z,relro > execunix.c: In function ‘execcmd’: > execunix.c:289:20: error: implicit declaration of function ‘vfork’ > [-Werror=implicit-function-declaration] > 289 | if ((pid = vfork()) == 0) > | ^~~~~ > execunix.c:293:13: error: implicit declaration of function ‘execvp’ > [-Werror=implicit-function-declaration] > 293 | execvp( argv[0], (char **)argv ); > | ^~~~~~ > execunix.c:294:13: error: implicit declaration of function ‘_exit’ > [-Werror=implicit-function-declaration] > 294 | _exit(127); > | ^~~~~ > execunix.c:294:13: warning: incompatible implicit declaration of built-in > function ‘_exit’ [-Wbuiltin-declaration-mismatch] > execunix.c: In function ‘execwait’: > execunix.c:334:22: error: implicit declaration of function ‘wait’ > [-Werror=implicit-function-declaration] > 334 | while( ( w = wait( &status ) ) == -1 && errno == EINTR ) > | ^~~~ > cc1: some warnings being treated as errors > fileunix.c: In function ‘file_archscan’: > fileunix.c:204:13: error: implicit declaration of function ‘read’; did you > mean ‘fread’? [-Werror=implicit-function-declaration] > 204 | if( read( fd, buf, SARMAG ) != SARMAG || > | ^~~~ > | fread > fileunix.c:207:13: error: implicit declaration of function ‘close’; did you > mean ‘pclose’? [-Werror=implicit-function-declaration] > 207 | close( fd ); > | ^~~~~ > | pclose > fileunix.c:259:17: error: implicit declaration of function ‘lseek’; did you > mean ‘fseek’? [-Werror=implicit-function-declaration] > 259 | lseek(fd, offset + SARHDR, 0); > | ^~~~~ > | fseek > cc1: some warnings being treated as errors > jam.c:169:1: warning: return type defaults to ‘int’ [-Wimplicit-int] > 169 | main( int argc, char **argv, char **arg_environ ) > | ^~~~ > make1.c: In function ‘make1d’: > make1.c:392:22: error: implicit declaration of function ‘unlink’ > [-Werror=implicit-function-declaration] > 392 | if( !unlink( targets->string ) ) > | ^~~~~~ > cc1: some warnings being treated as errors > parse.c: In function ‘parse_make’: > parse.c:102:27: error: implicit declaration of function ‘yylineno’; did you > mean ‘yylineo’? [-Werror=implicit-function-declaration] > 102 | p->yylineno = yylineno(); > | ^~~~~~~~ > | yylineo > cc1: some warnings being treated as errors > make[2]: *** [Makefile:115: jam0] Error 1 The full build log is available from: http://qa-logs.debian.net/2024/03/13/jam_2.6.1-2_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.
