Bug#799322: pocl: FTBFS: (gcc5 related?) symbols mismatches + test failures
Le 17/09/2015 22:45, Rebecca N. Palmer a écrit : > Also, nearly all the tests failed: the build treats this as > non-fatal, but it should probably be investigated. Just for the record, failed tests are fatal but the failure is postponed in order to get more info from build logs: override_dh_auto_test: # Failure in testsuite is delayed until symbols handling # and all files are logged. $(RM) debian/stamp-failed-testsuite if ! dh_auto_test ; then \ [...] touch debian/stamp-failed-testsuite; \ fi override_dh_makeshlibs: dh_makeshlibs if test -f debian/stamp-failed-testsuite ; then \ grep '^ .*FAILED' < tests/testsuite.log ; \ exit 1 ; \ fi -- Vincent Danjean GPG key ID 0xD17897FA vdanj...@debian.org GPG key fingerprint: 621E 3509 654D D77C 43F5 CA4A F6AE F2AF D178 97FA Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main
Bug#799322: pocl: FTBFS: (gcc5 related?) symbols mismatches + test failures
Le 17/09/2015 22:45, Rebecca N. Palmer a écrit : > Package: src:pocl > Version: 0.10-10 > Severity: serious > Control: found -1 0.10-12 > Control: block 794935 with -1 > > The binNMU of pocl for the llvm-toolchain-3.5 transition > (https://buildd.debian.org/status/fetch.php?pkg=pocl=amd64=0.10-10%2Bb1=1442439767) > failed with symbols mismatches, at least some of which look gcc-5 related > (though I haven't checked whether they all are, and pocl does have a history > of symbols issues), e.g. > > - > (optional=templinst)_ZN4llvm12hash_combineINS_9hash_codeESsEES1_RKT_RKT0_@Base > 0.10 > [...] > +#MISSING: 0.10-10+b1# > (optional=templinst)_ZN4llvm12hash_combineINS_9hash_codeENS_9StringRefEEES1_RKT_RKT0_@Base > 0.10 > + > _ZN4llvm12hash_combineINS_9hash_codeENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcES1_RKT_RKT0_@Base > 0.10-10+b1 > > Also, nearly all the tests failed: the build treats this as non-fatal, but it > should probably be investigated. > > A local build of 0.10-12 from experimental had far fewer (but not no) test > failures, but still FTBFS with the symbols issue. pocl 0.10 is outdated. There is no interest into digging into it. I started to package the new version but did not have time to finish for now. Help welcome (I just pushed my initial work in collab-maint) pocl 0.10 can be removed from testing for now if this help transitions. And, for information, I plan to remove symbols tracking. This is a mess due to C++ mangling and all C++ libraries are only used internally. So, there is no interest at all into tracking the symbol list. Regards, Vincent -- Vincent Danjean GPG key ID 0xD17897FA vdanj...@debian.org GPG key fingerprint: 621E 3509 654D D77C 43F5 CA4A F6AE F2AF D178 97FA Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html APT repo: deb http://people.debian.org/~vdanjean/debian unstable main
Bug#799322: pocl: FTBFS: (gcc5 related?) symbols mismatches + test failures
Package: src:pocl Version: 0.10-10 Severity: serious Control: found -1 0.10-12 Control: block 794935 with -1 The binNMU of pocl for the llvm-toolchain-3.5 transition (https://buildd.debian.org/status/fetch.php?pkg=pocl=amd64=0.10-10%2Bb1=1442439767) failed with symbols mismatches, at least some of which look gcc-5 related (though I haven't checked whether they all are, and pocl does have a history of symbols issues), e.g. - (optional=templinst)_ZN4llvm12hash_combineINS_9hash_codeESsEES1_RKT_RKT0_@Base 0.10 [...] +#MISSING: 0.10-10+b1# (optional=templinst)_ZN4llvm12hash_combineINS_9hash_codeENS_9StringRefEEES1_RKT_RKT0_@Base 0.10 + _ZN4llvm12hash_combineINS_9hash_codeENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcES1_RKT_RKT0_@Base 0.10-10+b1 Also, nearly all the tests failed: the build treats this as non-fatal, but it should probably be investigated. A local build of 0.10-12 from experimental had far fewer (but not no) test failures, but still FTBFS with the symbols issue.
