Source: soapyhackrf Version: 0.2.1+git20160919-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/c++ -DHackRFSupport_EXPORTS > -I/<<BUILDDIR>>/soapyhackrf-0.2.1+git20160919 -I/usr/include/libhackrf -g > -O2 -fdebug-prefix-map=/<<BUILDDIR>>/soapyhackrf-0.2.1+git20160919=. -fPIE > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -fvisibility-inlines-hidden -std=c++11 -fPIC > -Wno-unused-parameter -Wall -Wextra -fvisibility=hidden -std=gnu++11 -o > CMakeFiles/HackRFSupport.dir/HackRF_Registation.cpp.o -c > /<<BUILDDIR>>/soapyhackrf-0.2.1+git20160919/HackRF_Registation.cpp > In file included from > /<<BUILDDIR>>/soapyhackrf-0.2.1+git20160919/HackRF_Registation.cpp:22:0: > /<<BUILDDIR>>/soapyhackrf-0.2.1+git20160919/SoapyHackRF.hpp:371:2: error: > 'transceiver_mode_t' does not name a type > transceiver_mode_t _current_mode; > ^~~~~~~~~~~~~~~~~~ > CMakeFiles/HackRFSupport.dir/build.make:65: recipe for target > 'CMakeFiles/HackRFSupport.dir/HackRF_Registation.cpp.o' failed > make[3]: *** [CMakeFiles/HackRFSupport.dir/HackRF_Registation.cpp.o] Error 1 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/soapyhackrf_0.2.1+git20160919-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.
