Source: gammu Version: 1.37.4-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161021 qa-ftbfs Justification: FTBFS on amd64
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /usr/bin/cc -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -Wl,-z,relro > CMakeFiles/cmTC_ab4a5.dir/CheckSymbolExists.c.o -o cmTC_ab4a5 -rdynamic > CMakeFiles/cmTC_ab4a5.dir/CheckSymbolExists.c.o: In function `main': > ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined > reference to `pthread_create' > collect2: error: ld returned 1 exit status If the failure looks somehow time/timezone related: Note that this rebuild was performed without the 'tzdata' package installed in the chroot. tzdata used be (transitively) part of build-essential, but it no longer is. If this package requires it to build, it should be added to build-depends. For the release team's opinion on this, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185 If the failure looks LSB-related: similarly to tzdata, lsb-base is not installed in the build chroot. The full build log is available from: http://aws-logs.debian.net/2016/10/21/gammu_1.37.4-1_unstable.log 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! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
