Source: purelibc
Version: 1.0.6-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

During a rebuild of all packages in sid, your package failed to build
on armhf.


Relevant part (hopefully):
> /usr/bin/cc -D_GNU_SOURCE -Dpurelibc_EXPORTS -I/<<PKGBUILDDIR>> -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -Wall -pedantic -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
> -D_FORTIFY_SOURCE=2 -ggdb -Wall -Wextra -pedantic -std=gnu11 
> -Wno-incompatible-pointer-types -Wno-unused-parameter -fPIC -MD -MT 
> CMakeFiles/purelibc.dir/syscalls.c.o -MF 
> CMakeFiles/purelibc.dir/syscalls.c.o.d -o 
> CMakeFiles/purelibc.dir/syscalls.c.o -c /<<PKGBUILDDIR>>/syscalls.c
> /tmp/ccPREIBJ.s: Assembler messages:
> /tmp/ccPREIBJ.s:380: Error: symbol `readdir64' is already defined
> /tmp/ccPREIBJ.s:984: Error: symbol `scandir64' is already defined
> /tmp/ccPREIBJ.s:1045: Error: symbol `scandirat64' is already defined
> make[3]: *** [CMakeFiles/purelibc.dir/build.make:79: 
> CMakeFiles/purelibc.dir/dir.c.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/purelibc_1.0.6-1_unstable-armhf.log

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