Source: highwayhash Version: 0~git20181002.c5ee50b-3 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20190315 qa-ftbfs Justification: FTBFS in buster on amd64
Hi, During a rebuild of all packages in buster (in a buster chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<<PKGBUILDDIR>>' > g++ -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong > -Wformat -Werror=format-security -std=c++11 -Wall -O3 -fPIC -pthread > -Wl,-z,relro -Wl,-z,now -pthread -shared obj/sip_hash.o obj/sip_tree_hash.o > obj/scalar_sip_tree_hash.o obj/arch_specific.o obj/instruction_sets.o > obj/nanobenchmark.o obj/os_specific.o obj/hh_portable.o obj/hh_avx2.o > obj/hh_sse41.o obj/c_bindings.o -o lib/libhighwayhash.so.0 > -Wl,-soname,libhighwayhash.so.0 > mkdir -p /<<PKGBUILDDIR>>/debian/tmp//usr/lib/x86_64-linux-gnu/ > mkdir -p /<<PKGBUILDDIR>>/debian/tmp//usr/include//highwayhash > install -m0444 lib/libhighwayhash.a > /<<PKGBUILDDIR>>/debian/tmp//usr/lib/x86_64-linux-gnu/ > install -m0555 lib/libhighwayhash.so > /<<PKGBUILDDIR>>/debian/tmp//usr/lib/x86_64-linux-gnu/ > install -m0444 highwayhash/*.h > /<<PKGBUILDDIR>>/debian/tmp//usr/include//highwayhash/ > make[2]: Leaving directory '/<<PKGBUILDDIR>>' > mkdir -p debian/libhighwayhash0/usr/lib/x86_64-linux-gnu > rename 's/.so/.so.0/' debian/tmp/usr/lib/x86_64-linux-gnu/*.so > install -m0755 debian/tmp/usr/lib/x86_64-linux-gnu/*.so.0 \ > debian/libhighwayhash0/usr/lib/x86_64-linux-gnu/ > mkdir -p debian/libhighwayhash-dev/usr/lib/x86_64-linux-gnu > install -m0755 debian/tmp/usr/lib/x86_64-linux-gnu/*.a \ > debian/libhighwayhash-dev/usr/lib/x86_64-linux-gnu/ > set -e; cd debian/libhighwayhash-dev/usr/lib/x86_64-linux-gnu/; \ > ln -s libhighwayhash.so.0 libhighwayhash.so > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > dh_install > dh_installdocs > dh_installchangelogs > dh_installman > dh_lintian > dh_perl > dh_link > dh_strip_nondeterminism > dh_compress > dh_fixperms > dh_missing > dh_strip > dh_makeshlibs > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libhighwayhash0/DEBIAN/symbols doesn't match > completely debian/libhighwayhash0.symbols > --- debian/libhighwayhash0.symbols > (libhighwayhash0_0~git20181002.c5ee50b-3_amd64) > +++ dpkg-gensymbolsg8mdHJ 2019-03-16 04:54:58.805876282 +0000 > @@ -64,7 +64,7 @@ > > _ZNSt23mersenne_twister_engineImLm64ELm312ELm156ELm31ELm13043109905998158313ELm29ELm6148914691236517205ELm17ELm8202884508482404352ELm37ELm18444473444759240704ELm43ELm6364136223846793005EEclEv@Base > 0~20180209-g14dedec > > _ZNSt24uniform_int_distributionImEclISt20discard_block_engineISt26subtract_with_carry_engineImLm48ELm5ELm12EELm389ELm11EEEEmRT_RKNS0_10param_typeE@Base > 0~20170419-g1f4a24f > > _ZNSt6vectorISt4pairIjiESaIS1_EE17_M_realloc_insertIJS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base > 0~20180103-geeea446 > - > _ZNSt6vectorIjSaIjEE17_M_realloc_insertIJRKjEEEvN9__gnu_cxx17__normal_iteratorIPjS1_EEDpOT_@Base > 0~20180209-g14dedec > +#MISSING: 0~git20181002.c5ee50b-3# > _ZNSt6vectorIjSaIjEE17_M_realloc_insertIJRKjEEEvN9__gnu_cxx17__normal_iteratorIPjS1_EEDpOT_@Base > 0~20180209-g14dedec > _ZNSt6vectorImSaImEE17_M_default_appendEm@Base 0~20180209-g14dedec > > _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIjSaIjEEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base > 0~20170419-g1f4a24f > > _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIjSaIjEEESt10_Select1stIS5_ESt4lessImESaIS5_EE8_M_eraseEPSt13_Rb_tree_nodeIS5_E@Base > 0~20170419-g1f4a24f > dh_makeshlibs: failing due to earlier errors > make: *** [debian/rules:22: binary] Error 2 The full build log is available from: http://aws-logs.debian.net/2019/03/15/highwayhash_0~git20181002.c5ee50b-3_testing.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.
